Now that Visual Studio 2010 Beta 2 is out, it is a lot of fun to use the fully interactive design surface for Silverlight. However, it comes at a cost: you need to use the conversion wizard to bring your Visual Studio 2008 solutions and projects up to the expected format for the designer tools and new build environment.
If you deliver your source ultimately to a Visual Studio 2008-targeted source project, or have issue adopting a beta product until its release, this is a pain.
I wrote a tool last month for round-trip converting Silverlight-specific solutions and .csproj files between the versions, and want to share it as-is, with no warranty, hoping someone finds it useful.
Here are two potential solutions for dealing with the conversion issue, actually the second builds from the first.
Use Source Control
If your project is not churning that often in added and removed files, source control is the easiest solution to this problem!
- Open your solution in Visual Studio 2010
- Allow the conversion wizard to complete
- When checking in, carefully revert the .csproj and .sln files (assuming no changes to their contents)
Easy enough. But not crisp enough!