 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
.NET Forum / Languages / Managed C++ / October 2007.NET Framework versions
If I tell the compiler to target .NET Framework 3.0 (one of the References options in VC++ 2008 Express), does it still work if they only have a higher version (say 3.5) of .NET Framework installed? Or does it look for and only work with the specific version? The various various versions (e.g., 2.0 ,3.0, 3.5) seem to install independently (i.e., I believe they are co-resident, one doesn't seem to replace the other), so this is why I ask. And of course I'm asking for future versions as well, such as 4.0, 5.0, etc... [==Peter==] > If I tell the compiler to target .NET Framework 3.0 (one of the References > options in VC++ 2008 Express), does it still work if they only have a higher > version (say 3.5) of .NET Framework installed? Or does it look for and only > work with the specific version? If you target a lower version of the framework in 2008, it will run on all higher versions because they are cumulative from 2.0 to 3.5. That is, 3.5 contains 3.0 which in turn contains 2.0. This may not be the case with 4.0 or whatever comes out after 3.5, since the CLR version might change. .Net 2.0, 3.0 and 3.5 are really just a cumulative set of assemblies on the core 2.0 CLR. >This may not be the case with 4.0 or > whatever comes out after 3.5, since the CLR version might change. If this happened, would this mean everything written before 4.0 would stop working for those end-users who only get into the game post 4.0? That seems kind of drastic, and prone to legal action...(hehe)... [==Peter==] >> If I tell the compiler to target .NET Framework 3.0 (one of the >> References [quoted text clipped - 12 lines] > 3.0 and 3.5 are really just a cumulative set of assemblies on the core 2.0 > CLR. > >This may not be the case with 4.0 or > > whatever comes out after 3.5, since the CLR version might change. [quoted text clipped - 21 lines] > > 3.0 and 3.5 are really just a cumulative set of assemblies on the core 2.0 > > CLR. No, sorry for the confusion. My point was that the versions of .Net which VS 2008 targets - 2.0, 3.0 and 3.5 - are really just assemblies on the 2.0 CLR. As such, you can think of 2.0, 3.0 and 3.5 as cumulative releases which just add functionality to the 2.0 CLR. Any future version of .Net will likely run on a different version of the CLR. I didn't mean to imply that 2.0 CLR assemblies won't run on a future version of the CLR. In VS 2008, "targeting" doesn't mean it produces a different binary, it just means that it means certain assemblies need to be present: the 2.0 Framework for 2.0, the Framework _and_ the WPF/WCF/WF assemblies for 3.0, and the Framework, WPF/WCF/WF assemblies _and_ the LINQ assemblies and a few other things for 3.5. > >This may not be the case with 4.0 or > > whatever comes out after 3.5, since the CLR version might change. [quoted text clipped - 21 lines] > > 3.0 and 3.5 are really just a cumulative set of assemblies on the core 2.0 > > CLR. Free MagazinesGet these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...
|
Reply to this Message
|
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2008 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.