Geeks With Blogs


This blog has moved to

 Subscribe in a reader

Add to Google Reader or Homepage

View my teams slideshare
These postings are provided "AS IS" with no warranties, and confer no rights.

IUpdateable has moved to Please visit

I am currently (Feb 2010) moving lots of Azure samples originally built in Visual Studio 2008 to Visual Studio 2010 RC. I just realised there is a simple mistake folks can fall into. Easy to do, easy to avoid.

When opening an Azure solution originally built in Visual Studio 2008  you will see the Conversion Wizard.


Once you click Finish you will see this dialogue box with a default of Yes. Do not click Yes! Instead click No.


The reason is simple. As of Feb 2010 the Windows Azure Fabric in Microsoft Data Centres is not running the .NET 4.0 RC, it is instead running .NET 3.5 SP1. Therefore you want to stick with .NET 3.5 SP1 for your projects to get the equivalent experience with the development fabric – which means you won’t have access (just yet) to some of the really good stuff such as Entity Framework 4.

End result is a nicely converted solution.


Related Links:

Posted on Tuesday, February 23, 2010 1:54 PM Cloud Computing | Back to top

Comments on this post: Visual Studio 2010 Conversion Wizard and Azure solutions – do not change target to .NET 4

# re: Visual Studio 2010 Conversion Wizard and Azure solutions – do not change target to .NET 4
Requesting Gravatar...
The easy way to do this instead of going through the conversion wizard would be to open the .csproj files individually and changing the tools version from 3.5 to 4.0 and keeping the target framework as v3.5

Create a new .sln file for vs2010 and then add an existing project to the solution and reference the .csproj file

This would mean the .csproj files are backwards compatible as well as having 2 .sln files to run your project under

Left by Paul Stack on Feb 23, 2010 2:35 PM

Your comment:
 (will show your gravatar)

Copyright © Eric Nelson | Powered by: