I went ahead and tried to install the new VS2005 beta I picked up at VSLive this week. Unfortunately I haven’t had much luck with it – it killed all of ASP. Net and worse the IIS Management Console. It looks like there’s a failure registering various virtual directories under ASP. Net 2.0. But the real bummer is that it crashes the IIS Admin console. As soon as I bring up the management console and right click on a Web site the MMC blows up with an exception. Trying to run an existing ASP.Net application results in immediate 404 errors (?).
I’ve been really clamoring for an update but I guess I shouldn’t get too excited. I’ve been more than anxious to get a more recent build of Whidbey/.Net 2.0 to test a few things I have been working on. Yeah, yeah, the software is not ready but there are a few technologies I’m more than a little interestested in learning more about and several of them I committed myself to do sessions on at a couple of conferences later this year (on the original assumption of a ship date at the end of this year instead of the middle of next year ).
In the end I had to uninstall the 2.0 framework and then re-register version 1.1 with ASPNET_REGIIS to get my existing applications to run again.
It’s really frustrating to have Microsoft push out stuff in this state. Hopefully this is an isolated issue that’s specific to my setup, although I doubt it since there’s nothing fancy on my local machine running Windows Server 2003. Although the CD is clearly labeled that this is an unsupported and untested build it’s pretty sad to have something in this state out a half a year after the original alpha shipped in what passes as a semi-offical build that is also going to be posted on MSDN for subscribers. In addition to the failure with ASP. Net and IIS I also looked through some of my sample apps I had been playing with some new features in Whidbey and the designers and VS.Net itself is acting really flaky – more flakey even than the original alpha.
So much for my excitement… Time to dig out Virtual PC and install it on a clean VPC…