|
dev
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
.NET Framework 2.0 to 3.0These different versions of frameworks which seems quite too many for
me, do they provide any sort of downward compatibility. I mean can I assume that if I write a application on .net framework 2.0 will it work okay when I move to 3.0 ? Or do I need to do some sort of conversion? Is anyone have any personal experiences. I know that if we have to make use of new features we need to probably re-write some part of the applications, but when I really don't want to make any tangible changes to one of my application and still want to run it on the next framework version will it work ? Especially from 2.0 to 3.0.? Well, 3.0 isn't a real new version of the framework. Its pretty much
..Net 2 + WinFX assemblies. So if you make an application in 2.0, it will run perfectly fine on 3.0. This is more or less true of all versions; if you target 1.1, it should run fine on 2.0 or 3.0 or 4.0. Of course to be sure you'll have to test and check to see if there are any breaking changes from each version of the framework. HTH Andy r.manikan***@gmail.com wrote: Show quote > These different versions of frameworks which seems quite too many for > me, do they provide any sort of downward compatibility. I mean can I > assume that if I write a application on .net framework 2.0 will it work > okay when I move to 3.0 ? Or do I need to do some sort of conversion? > > Is anyone have any personal experiences. I know that if we have to > make use of new features we need to probably re-write some part of the > applications, but when I really don't want to make any tangible changes > to one of my application and still want to run it on the next framework > version will it work ? Especially from 2.0 to 3.0.? Hi,
r.manikan***@gmail.com wrote: > These different versions of frameworks which seems quite too many for The .NET framework 3.0 is the .NET framework 2.0 plus additional > me, do they provide any sort of downward compatibility. I mean can I > assume that if I write a application on .net framework 2.0 will it work > okay when I move to 3.0 ? Or do I need to do some sort of conversion? > > Is anyone have any personal experiences. I know that if we have to > make use of new features we need to probably re-write some part of the > applications, but when I really don't want to make any tangible changes > to one of my application and still want to run it on the next framework > version will it work ? Especially from 2.0 to 3.0.? libraries. The compiler is the same. There is no conversion needed. If you want to do Windows Presentation Foundation, Windows Communication Foundation, Windows Workflow Foundation or Cardspace, you install the framework 2.0 and then you install the framework 3.0 on top of that. HTH, Laurent -- Laurent Bugnion, GalaSoft Software engineering: http://www.galasoft-LB.ch Private/Malaysia: http://mypage.bluewin.ch/lbugnion Support children in Calcutta: http://www.calcutta-espoir.ch From 2.0 to 3.0, you should be fine. Same with backwards compatibility,
except if you use some of the new features. You should compile the final release in the version of the Framework you are targeting for deployment. -- Show quoteGregory A. Beamer MVP; MCP: +I, SE, SD, DBA http://gregorybeamer.spaces.live.com ******************************************** Think outside the box! ******************************************** <r.manikan***@gmail.com> wrote in message news:1164897530.210637.314240@n67g2000cwd.googlegroups.com... > These different versions of frameworks which seems quite too many for > me, do they provide any sort of downward compatibility. I mean can I > assume that if I write a application on .net framework 2.0 will it work > okay when I move to 3.0 ? Or do I need to do some sort of conversion? > > Is anyone have any personal experiences. I know that if we have to > make use of new features we need to probably re-write some part of the > applications, but when I really don't want to make any tangible changes > to one of my application and still want to run it on the next framework > version will it work ? Especially from 2.0 to 3.0.? > Thanks guys for your replies..
Is (re)compiling necessary when I am not changing my code at all for each version of framework? Cheers, Mani. Cowboy (Gregory A. Beamer) wrote: Show quote > From 2.0 to 3.0, you should be fine. Same with backwards compatibility, > except if you use some of the new features. You should compile the final > release in the version of the Framework you are targeting for deployment. > > -- > Gregory A. Beamer > MVP; MCP: +I, SE, SD, DBA > http://gregorybeamer.spaces.live.com > > ******************************************** > Think outside the box! > ******************************************** > <r.manikan***@gmail.com> wrote in message > news:1164897530.210637.314240@n67g2000cwd.googlegroups.com... > > These different versions of frameworks which seems quite too many for > > me, do they provide any sort of downward compatibility. I mean can I > > assume that if I write a application on .net framework 2.0 will it work > > okay when I move to 3.0 ? Or do I need to do some sort of conversion? > > > > Is anyone have any personal experiences. I know that if we have to > > make use of new features we need to probably re-write some part of the > > applications, but when I really don't want to make any tangible changes > > to one of my application and still want to run it on the next framework > > version will it work ? Especially from 2.0 to 3.0.? > > Hello Mani,
No, but your app may request the framework where it was compiled M> Thanks guys for your replies.. M> M> Is (re)compiling necessary when I am not changing my code at all for M> each version of framework? M> M> Cheers, M> Mani. M> Cowboy (Gregory A. Beamer) wrote: Show quote >> From 2.0 to 3.0, you should be fine. Same with backwards Michael Nemtsev [C# MVP] :: blog: http://spaces.live.com/laflour>> compatibility, except if you use some of the new features. You should >> compile the final release in the version of the Framework you are >> targeting for deployment. >> >> -- >> Gregory A. Beamer >> MVP; MCP: +I, SE, SD, DBA >> http://gregorybeamer.spaces.live.com >> ******************************************** >> Think outside the box! >> ******************************************** >> <r.manikan***@gmail.com> wrote in message >> news:1164897530.210637.314240@n67g2000cwd.googlegroups.com... >>> These different versions of frameworks which seems quite too many >>> for me, do they provide any sort of downward compatibility. I mean >>> can I assume that if I write a application on .net framework 2.0 >>> will it work okay when I move to 3.0 ? Or do I need to do some sort >>> of conversion? >>> >>> Is anyone have any personal experiences. I know that if we have to >>> make use of new features we need to probably re-write some part of >>> the applications, but when I really don't want to make any tangible >>> changes to one of my application and still want to run it on the >>> next framework version will it work ? Especially from 2.0 to 3.0.? >>> --- WBR, "At times one remains faithful to a cause only because its opponents do not cease to be insipid." (c) Friedrich Nietzsche  |
|||||||||||||||||||||||
Other interesting topics