Like the most of you I wanted to have a close look at some new features of Orcas. While starting with the newer applications I became more and more frustrated by the minute. In the most basal screens I got al kind of strange errors. The funny part is, I'm using the VPC Microsoft is delivering on their Website. As with .NET 3.0, .NET 3.5 still relies on .NET 2.0 and I think this is were some of the problems are originated from.
Update from Alex:
If you have trouble or failures like Mike and a lot of others did, don't use the Virtual PC image, but instead create your own. Download the self-extracting installers for VS Orcas and TFS Orcas. Also, do NOT install VS2005 and Orcas side-by-side. This is the cause of all your pain and error messages (well, not all, but the a lot of the ones related to this subject). Why, o why did Microsoft install VS2005 Team Suite together with Orcas when even the release notes say this causes these issues.
Alex, you hit the nail on the head.
Here are some screendumps.
Microsoft .NET Framework 2.0 Configuration (Snap-in failed to initialize)
Project Properties (Microsoft.VisualStudio.Shell.WindowPane.OnCreate())
Workflow Designer (Microsoft.VisualStudio.Shell.WindowPane.GetService(System.Type))
This is so MS. I hope to find a solution for these problems, but I think I already know it (April CTP).