I'm happy to say that my VS 2008 Beta 1 to Beta 2 update went fairly smooth and I now have Beta 2 running on my dev machine with no problems. I was quite worried that this would be problematic - if you remember updating between betas during VS 2005 it was almost a requirement to pave over Windows and start over. This update went pretty smooth all things considered.
Watch out if you're doing a Beta 1 to Beta 2 reinstall
I did run into one major problem with the Beta 1 to Beta 2 migration:
The uninstall instructions (make sure you read these if you are updating from Beta 1!!!) missed one component or at least mislabeled it and so I didn't properly uninstall this component:
Microsoft Visual Studio Web Authoring Component
It's not on the list of components to uninstall but I suspect that Remove "Visual Web Developer Design Service Reminder Tools" probably references this same component by another name. Because of that I missed it at first since Visual Studio Web Authoring Component could have been a VS 2005 feature. It isn't <s>...
Before I manually uninstalled this component, I was able to install the .NET Framework 3.5 and Document Explorer, but as soon as the Visual Studio Installer kicked in the install aborted. The error log gives this:
***EndOfSession*** [07/27/07,12:45:47] setup.exe: [2] ISetupComponent::Pre/Post/Install() failed in ISetupManager::InternalInstallManager() with HRESULT -2147023293.
[07/27/07,12:45:49] VS70pgui: [2] DepCheck indicates Microsoft Web Designer Tools is not installed.
[07/27/07,12:45:50] VS70pgui: [2] DepCheck indicates Microsoft Visual Studio Team System 2008 Team Suite - ENU was not attempted to be installed.
[07/27/07,12:45:50] VS70pgui: [2] DepCheck indicates Microsoft .NET Compact Framework 2.0 SP2 was not attempted to be installed.
... more failures all the same
If you see this sort of thing make sure you check that you have indeed uninstalled all previous components.
Bottom line: Make sure you follow the uninstall instructions exactly and don't miss any components (which is easy to do because here's a lot of 'em and the names are very similar for many components).
Make sure you install the MS AJAX Patch
Microsoft also has a policy issue that affects usage of MS AJAX. If you use MS Ajax make sure you run this batch file which sets the proper access policy for the Ajax Libraries. Scott Guthrie has more detail:
1) You should download and run this batch file. This takes only a few seconds to run, and fixes an issue we found earlier this week with the version policy of System.Web.Extensions.dll - which is the assembly that contains ASP.NET AJAX. If you don't run this batch file, then existing ASP.NET 2.0 projects built with ASP.NET AJAX 1.0 and VS 2005 will end up automatically picking up the new version of ASP.NET AJAX that ships in .NET 3.5 Beta2. This will work and run fine - but cause you to inadvertently introduce a .NET 3.5 dependency in the applications you build with VS 2005. Running the batch file will change the version binding policy of the new System.Web.Extensions.dll assembly and ensure that you only use the new .NET 3.5 ASP.NET AJAX version with projects that you are explicitly building for .NET 3.5.
Up and Running
So Beta 2 is up and running and it looks like VS is even more snappy then Beta 1 was and which compared to VS 2005 is considerably more responsive in most respects, especially designer opening (most designers) and even more so the ASP.NET designer. I'm running the full install not VPC so I can get the full effect and (hopefully not - so far so good) pain. I also run VS 2005 and VS 2003 on the same Vista box and they all live happily together in a cozy little VS family.
I ran through all of my Orcas projects and hey they were still all working without any problems. Several of the designers I had problems with in Beta 1 (including the Linq to SQL designer) now properly work as do all the data tools. I was actually stoked to see the new Data Tools for schema and data comparison in the Team Edition - I've been meaning to check this out but never got to it. This integrated implementation might wean me off Red Gate's SqlCompare and SqlDataCompare which I've been very happy with for years (and I think are still easier to use than the VS stuff).
So far I haven't spent much time with any of the new 3.5 features simply because I had some issues in Beta 1 and - well without a goLive license it seems kind of pointless to start building production code. Since there's now the GoLive option I'll be spending more time with 3.5. First stop is reworking my generic business layer to take advantage of LINQ features.
Anyway - first day on Orcas has been good. I spend a good part of the day running Beta 2 and it's pretty solid. No crashes, no major unexpected behavior. VS 2005 is quickly fading into history in my environment since I've been running on Orcas for a couple of months now almost exclusively.
Things are good! Imagine that...