Jonathan Crossland
Posts: 630
Nickname: jonathanc
Registered: Feb, 2004
|
Jonathan Crossland is a software architect for Lucid Ocean Ltd
|
|
|
|
Converting an Enterprise Level App from VS 2008 to 2010
|
Posted: Nov 13, 2009 4:32 AM
|
|
The Wizard opened straight away, I clicked next.
After a few popup dialogs, requesting from me things such as Can't find the source control, remove source control binding? and would you like to upgrade the web projects to .NET 4.0?, which I responded yes to all.
The first problem came when the web project tried to bind to IIS, but failed. the wizard asked if I would like to create the virtual folder, I said yes and it failed, since it already existed. Accepting this to be a fair point, I created a new IIS Application, mapped to my project, edited the project file (right click on the project which failed to load) and selected Edit Project file. The edit context menu is a simply but great new useful feature.
I then reloaded the project from the same context menu and it loaded perfectly.
Running the application worked first time. I ran our manual Sanity Test, our automatic unit tests and all passed first time.
In short, upgrading the web app to .NET 4.0 upgraded and ran perfectly well.
but what would it do if I changed the target platform back to 3.5?
I went directly to the project properties and changed the target platform to 3.5, at which point I was informed that a project reload was required.
I then went through all 16 projects in the solution. Some had changed to 3.5, some were still on 4.0. I changed all projects to 2.5, compiled and ran.
The first Error
I got the following error:
"Could not load file or assembly 'xxx' or one of its dependencies. This assembly is built by a runtime newer than the currently loaded runtime and cannot be loaded."
Oops, I missed one.
I changed the version to 3.5, rebuilt. Still error.
What happened was all the projects hooked up to Microsoft.VisualStudio.QualityTools.UnitTestFramework.dll - refused to change to version 2.*. The project reverted back to version 4.0, and I could not keep it in 3.5.
Eventually, after trying tons of manual attempts to reference alternative versions, rebuild etc, nothing worked and I was done.
Start from the top
I decided to start from scratch, get my backup up and start the wizard from scratch, this time, not upgrading to 4.0 from teh get-got.
After repeating the exercise and not moving to .NET 4.0, I discovered that all the UnitTestFramework dependent projects had been forced to version 4.0 and I got the same error as before.
You can view the problem on
Microsoft Connect, and as I did, discover that not much of a solve has been written there. (Please leave your feedback on the site)
STOP. It is a shame that one would consider the .NET Unit Testing Framework to be such a small piece of the whole 2010 pie, was the reason I cannot upgrade an Enterprise project. Not good for test first is it?
[Let me just point out that Visual Studio .NET 2010 is in Beta 2, at the time of this post]
Read: Converting an Enterprise Level App from VS 2008 to 2010
|
|
Previous Topic
