10/19/2007

The Project XXX could not be opened because the Microsoft Visual C# 2008 compiler could not be created

If you have any experience installing Microsoft Beta or CTP offerings, then uninstalling to make way for a newer version, then with Visual Studio 2008 (Orcas) the above may be somewhat familiar.

Surprisingly, the answer is to install the latest version of the Silverlight Tools here:
http://www.microsoft.com/downloads/details.aspx?FamilyID=b52aeb39-1f10-49a6-85fc-a0a19cac99af&DisplayLang=en

That may not be the only answer, but it seems to have worked for a number of people including me.

If you are having trouble uninstalling Visual Studio ORCAS because the MSI information got clobbered somehow, or it reports not being able to find some "network location" (DOH), one of the fastest ways to clean things up is to use some of the tools out there, many of which have been provided by installation guru Aaron Stebner. Here's a post by Brad Abrams that highlights two tools you can use.

MSIInv takes an inventory of all your MSI-installed software (even stuff you cannot see in Add/Remove or Programs and Features). It provides you with the GUID so that you can just run msiexec /x {clsid of software}. This often solves the problem. You can also use MSIZap (also detailed on the post with a download link).


As well, I have been able to use the MSICUU "cleanup" utility which is even easier to use.

Have fun. It's us against them.

In other news, if you are concerned about the freedom of the Internet ("Net Neutrality"), read this about what Comcast is doing.