Back in early November, just after the RTM release of VS2005 & SQL2005, I posted about a custom targets file you can use with MSBuild to get VS2005 to build projects against the v1.1 CLR. This is fantastic as you can use some of the great new IDE features within VS2005 and remove VS2003 from your machine and thus, freeing up some much needed disk space for virtualization, music, pictures, or anything else.
It’s not that the solution was a hack, but it didn’t account for every situation. Well, the MSBuild team was thinking about starting a new project that will provide this ability that accounts for all situations… thus making VS2005 a complete replacement for VS2003. If you don’t follow one of the developers blogs (Geek Runs Through My Veins), let me be the one to cue you in: they’re going for it!
The project is called: MSBee. This stands for MSBuild Everett Environment (Everett was the codename of the VS2003 project). The blog I just mentioned is posting a play-by-play on the status, challenges, and process of the project. Below you’ll find a link to some of his their previous posts. MSBee isn’t available yet, but they are interested in hearing from early adopters.
[Update 12/19/2005] Following up from comments to this post, Tom Fuller of SOAPitStop posted his questions to a MSBuild forum. MSBuild is a build environment, it's not an upgrade path from v1.1->v2.0. It only provides a way for you to build CLR v1.1 projects from within the VS2005 IDE. You may have other issues when working on a CLR v1.1 projects within the VS2005 IDE. For example, when you add a reference to a Web service in VS2005 when you're working with a CLR v1.1 project, it will add references to the CLR v2.0 classes.
One way to work around these issues is to create custom project items in VS2005 as outlined in an article in this month's MSDN magazine by Matt Milner.
The title of this post is a bit misleading so I've changed it.