VS2008/2010 backwards compatibility
-
How reliable is the ability to build .NET 2.0 compatible projects under more recent editions? Just wondering.
Visit http://www.notreadytogiveup.com/[^] and do something special today.
-
How reliable is the ability to build .NET 2.0 compatible projects under more recent editions? Just wondering.
Visit http://www.notreadytogiveup.com/[^] and do something special today.
It's fine - you just don't get the later assemblies if you target .NET 2.
"WPF has many lovers. It's a veritable porn star!" - Josh Smith
As Braveheart once said, "You can take our freedom but you'll never take our Hobnobs!" - Martin Hughes.
-
How reliable is the ability to build .NET 2.0 compatible projects under more recent editions? Just wondering.
Visit http://www.notreadytogiveup.com/[^] and do something special today.
have VS2008 build for .NET 2.0 works fine for me, it is what I do most often. :)
Luc Pattyn
:badger: :jig: :badger:
Have a look at my entry for the lean-and-mean competition; please provide comments, feedback, discussion, and don’t forget to vote for it! Thank you.
:jig: :badger: :jig:
-
How reliable is the ability to build .NET 2.0 compatible projects under more recent editions? Just wondering.
Visit http://www.notreadytogiveup.com/[^] and do something special today.
-
well .NET Framework 3.0, version 3.5 uses the CLR of version 2.0 :)
Best Of Regards, SOFTDEV Sad like books with torn pages, sad like unfinished stories ...
Any idea about .NET 4.0? I had a cursory look on Google, but didn't get anything conclusive.
Cheers, Vikram. (Cracked not one CCC, but two!)
-
It's fine - you just don't get the later assemblies if you target .NET 2.
"WPF has many lovers. It's a veritable porn star!" - Josh Smith
As Braveheart once said, "You can take our freedom but you'll never take our Hobnobs!" - Martin Hughes.
But you can add them as references since they use CLR 2.0, can't you? I've used assemblies that were introduced as part of .NET 3.5 with a VS 2005 project, and they worked just fine. I imagine you could do the same with VS 2008 while still targeting .NET 2.0....
Cheers, Vikram. (Cracked not one CCC, but two!)
-
Any idea about .NET 4.0? I had a cursory look on Google, but didn't get anything conclusive.
Cheers, Vikram. (Cracked not one CCC, but two!)
Vikram A Punathambekar wrote:
Any idea about .NET 4.0
I'm fairly certain it won't run on CLR 2.0 - language features like
dynamicand No PIA would require major changes in the CLR.Regards Senthil _____________________________ My Home Page |My Blog | My Articles | My Flickr | WinMacro
-
How reliable is the ability to build .NET 2.0 compatible projects under more recent editions? Just wondering.
Visit http://www.notreadytogiveup.com/[^] and do something special today.
Works just fine - I've developed both WinForms and ASP.NET apps that target .NET 2.0 using VS2008. The only thing that's ever been an issue is when someone else needs to use the same .sln and .csproj files and doesn't have VS2008. I've also developed a small utility that targets .NET 2.0 using VS2010, so by all indications I've seen, that compatibility will continue.
-
How reliable is the ability to build .NET 2.0 compatible projects under more recent editions? Just wondering.
Visit http://www.notreadytogiveup.com/[^] and do something special today.
Works just fine. Once you upgrade a project to VS 2010 the prj and sln files are updated as well so you won't be able to reopen in VS2008.
Brad
-
But you can add them as references since they use CLR 2.0, can't you? I've used assemblies that were introduced as part of .NET 3.5 with a VS 2005 project, and they worked just fine. I imagine you could do the same with VS 2008 while still targeting .NET 2.0....
Cheers, Vikram. (Cracked not one CCC, but two!)
But it stops being a .NET 2 app at this stage - you are requiring the client to download a later version of the framework if they haven't got it installed.
"WPF has many lovers. It's a veritable porn star!" - Josh Smith
As Braveheart once said, "You can take our freedom but you'll never take our Hobnobs!" - Martin Hughes.
-
But it stops being a .NET 2 app at this stage - you are requiring the client to download a later version of the framework if they haven't got it installed.
"WPF has many lovers. It's a veritable porn star!" - Josh Smith
As Braveheart once said, "You can take our freedom but you'll never take our Hobnobs!" - Martin Hughes.
Pete O'Hanlon wrote:
you are requiring the client to download a later version of the framework if they haven't got it installed
Not really. If you only require one or two 3.5-specific DLLs, you can copy them over to your 2.0-only dev machine, add them as references, build your app, and distribute it to clients who have only 2.0. (Obviously you will have to distribute the 3.5-specific DLLs with your app.) The app will run just fine. I did it as recently as this year in a highly controlled environment. (If it doesn't/didn't work for you, pl let me know - I would be very surprised and might dig around to find out why.)
Cheers, Vikram. (Cracked not one CCC, but two!)