Dan,
As Mike suggests a .NET application requires the .NET Framework installed.
However this is a one time install (per version), once the Framework is
installed for one app, its installed for all apps. As more & more developers
create .NET apps, the framework is going to be installed on more & more
machines, thus increasing the chance that it will already be installed...
Luckily .NET was designed with side-by-side in mind, which means you can
have multiple versions of the Framework installed at one time. Each
respective app will use their respective version of the Framework. .NET was
also designed with a certain amount of compatibility across versions.
http://msdn.microsoft.com/library/de...ecutiontop.asp
..NET 2.0 will run most .NET 1.1 & 1.0 applications without any problems.
http://msdn2.microsoft.com/en-us/library/ms228009.aspx
In fact most .NET 1.0 & 1.1 apps will/should run under the .NET 2.0 64-bit
edition!
http://blogs.msdn.com/joshwil/archiv...06/415191.aspx
However due to meta file changes (Generics & such) .NET 1.0 & 1.1 cannot run
..NET 2.0 assemblies.
With appropriate lines you your app.config/web.config you can have .NET 1.0
run most .NET 1.1 applications. While .NET 1.1 will run most .NET 1.0
applications without change.
The general problem with running an app on different versions of the
framework are the "Breaking changes".
By .NET application I mean which version of the framework the program was
compiled against. VS 2002 compiles against .NET 1.0, VS 2003 is .NET 1.1,
while VS 2005 is .NET 2.0.
--
Hope this helps
Jay [MVP - Outlook]
..NET Application Architect, Enthusiast, & Evangelist
T.S. Bradley -
http://www.tsbradley.net
"Dan" <Da*@discussions.microsoft.com> wrote in message
news:6A**********************************@microsof t.com...
| Michel - thanks a lot for that information! Not sure what you mean by
| "distribution of the framework"... Is creating an executable or install
| package more cumbersome than VB6?
|
|
| Dan
|
|
|
| "m.posseth" wrote:
|
| > Hello Dan
| >
| > Well i am a VS6 and VS.Net coder ( i use both for my work ) VB.Net is
| > fully object oriented and is in a lot of ways totally different as VB6
,
| > you have to think more in OOP style while VB6 was more forgiving VB.Net
is
| > much more strict .
| >
| > However i believe that with the correct book specially targetted to
| > programmers switching from VB6 to VB.Net like the Core reference guide
| > from Francesco Balena "Programming Microsoft Visual basic .Net" ( note
that
| > the 2005 edition will be availlable in mid january 2006 ) you feel
| > yourself at home within a few weeks , and never want to switch back in a
few
| > months
| >
| > VB.Net is now as powerfull as all the rest of the Visual studio
languages ,
| > if you can overcome the distribution of the framework with your app ,
You
| > have a far more superior development environment as with VS 6
| >
| > regards
| >
| > Michel Posseth [MCP]
| >
| >
| >
| > "Dan" <Da*@discussions.microsoft.com> wrote in message
| > news:D5**********************************@microsof t.com...
| > > Hi - can anyone tell me how much different VB.net is different from
VB6?
| > > I'm
| > > thinking of transitioning but would like to know more about its
| > > capabilities,
| > > ease of transition, etc.
| > >
| > > Any opinions would be greatly appreciated!
| > >
| > > Thanks -
| > >
| > > Dan
| >
| >
| >