Is it safe to port my project to .NET 4.0?

I ported the project to VS2010 but not targeting .NET 4.0 yet. It is currently targeting 3.5 SP1 (and CLR 2). The project relies on several third-party components - mostly open source - that were supposedly built against version 2.0 of the CLR.

Can I just migrate the project to the 4.0 runtime? Or do I need to get new versions of all the referenced assemblies that it depends on?

I did a bit of getting familiar with the new .NET 4.0 built-in feature, but I don't think it applies here (there were about two different .NET plugins for an office application in the example I read). My situation is different. My solution references assemblies directly and I don't think it applies side-by-side - unless I understand its purpose.

TIA

+2


a source to share


2 answers


You can probably retarget, but success or failure will depend entirely on the specifics of your application.

Check out the links posted here: Breaking Changes in .NET 4.0 .



Most of the breaking changes will be either compiler problems or Framework problems. You probably don't need to worry about compiler issues because you've already ported to Visual Studio 2010.On the other hand, platform changes are very important because you might not notice them until you've deployed the new version and bug reports started popping up.

+1


a source


Try to run your application with .NET 4.0 (without changing it) using the method described here:

http://social.msdn.microsoft.com/Forums/en/netfxsetupprerelease/thread/d6d8957e-742a-4cc2-b5c1-d9130ea423d0



If this works and there is no problem, you can migrate your project by retargeting to .NET 4.

0


a source







All Articles