I have a test server here that I use to run most of my application tests on. I recently bought a 500 meg hard disk for around $200 and I'm partioning this thing off as my not-so Virtual PCs.
At this point I had only Visual Web Developer installed on the first XP partition because I needed to have a one machine for testing the dev environment with it. With all the trouble I'm having with VS.NET on my laptop I'm going to install it on my faster desktop box and see whether it's still so damn slow there.
Aaccckk... VS won't install on a machine that has Visual Web Developer on it. Says there's a Beta version installed. I don't think so <g>... I suppose Visual Web Developer qualifies as beta. I'd say VS.NET release qualifies as a beta if you ask me...
Anyway, I had to run the uninstaller and it took care of removing VWD and who knows what else. Looking at the install running now it looks like it pulled off the .NET framework too and it's reinstalling that and data and XML components again. It seems it would make sense to make this upgrade process more seamless to people who are actually upgrading.
Another interesting note - in the installer there's a special checkbox for Visual Web Developer. I guess this is the ASP.NET designer, but it's actually not the light weight Visual Web Developer surface. Suggestion: Install the Visual Web Developer binary along side with the full VS.NET shell. If these guys can co-exist (supposedly they do - but apparently you have to install VWD AFTER VS.NET) it's often nice to have the more light weight environement at hand.
The good news is on this machine and hard disk, the installer is chugging through the whole ordeal in about 20 minutes... that's promising.