Notice that before I installed Orcas on my Vista Business setup, I first deinstalled all the VS 2005 add-ons (such as GAX, GAT, software factories, AJAX, and the WCF/WF/WPF extensions), but I did not uninstall VS 2005 itself.
- The installation of .NET 3.5 fails almost immediately. It seems that the Visual Studio setup uses the wrong command-line arguments, since I got a pop-up similarly to what you get when you add -? Or -h to a command-line tool. I had to manually install the 3.5 bits. After that, installation went fine.
- I also installed the Team Explorer parts from the Team Foundation Server folder. I'm happy to inform you that I managed to succesfully connect to an existing TFS server and get all my sources. So no need to change your TFS v1 installation.
- I then installed the Visual Studio Orcas SDK (Feb 2007 preview) and the Feb 2007 versions of GAX and GAT. However, the Guidance Package Manager did not appear in Orcas (but did in VS2005). This basically renders Orcas unusable for production development until somebody figures out the required registry changes.
- I also reinstalled Enterprise Library 3.0.
- Orcas contains a different version of the System.Web.Extensions AJAX assembly. The stuff you can download from http://ajax.asp.net/ is version 1.0.61025.0, but the Orcas version is 220.127.116.11.
- I couldn't find the WCF Configuration Editor you get when you install the WCF Extensions for Visual Studio 2005. I expected it to be a built-in part of Orcas by now.
- Opening existing projects and solutions will trigger a conversion wizard. They must have changed the project format once again.
- The first console application I tried to compile resulted in a "Required file 'alink.dll with IALink3' could not be found'. I fixed it by manually reinstalling Windows6.0-KB110806-x86 from the WCU folder. This article refers to this problem in more detail.
- Obviously, Resharper will not install on Orcas. But looking through their roadmap for version 3.0 shows their plans for including it. We'll just have to wait.
- The Web Service Software Factory-based solution runs fine, but the ASP.NET 2.0 website does not. According to the designer there is a problem with the master pages. Investigating...