Saturday, 8 December 2012

Can't target .NET 3.5 after upgrading a Visual Studio 2008 solution to 2012

I ran into an interesting problem today when upgrading a visual studio 2008 project to visual studio 2012, whilst trying to leave the targeted framework to .NET 3.5. Each time I tried to open the solution all my test projects automatically upgraded to .NET 4.0 regardless of what I did. It was impossible to downgrade the project using either the project property page or manually editing the project file. I'd make the change and then reload the project, a project conversion report would be shown and the project was back to targeting 4.0 again.

After a little more digging around I noticed that it was only my test projects that were doing this, all the other class libraries, etc. were perfectly happy targeting 3.5. After a little more experimentation I isolated this to the project type guids section, if I removed this from the project definition then I could re-target my unit test project at v3.5 and everything was happy. Note: As the linked blog post indicates, you might lose the ability to add new tests directly from the "Add New" menu, but it would appear you can either have one or the other, but not both!

No comments:

Post a Comment