Peter Bromberg's UnBlog

For a list of all the ways technology has failed to improve the quality of life, please press three. -- Alice Kahn This is due to some assembly redirects that are added to the devenv.exe.config file by installing the GAX (Guidance Automation Extensions). Here is the fix, and it's an easy one: 1) Navigate to: C:\Program Files\Microsoft Visual Studio 9.0\Common7\IDE in Windows Explorer 2) Load devenv.exe.config in your favorite text editor. 3) Find this string: "Microsoft.VisualStudio.TemplateWizardInterface" 4) Comment out the element so it looks like this: <dependentAssembly> <!--assemblyIdentity name="Microsoft.VisualStudio.TemplateWizardInterface" publicKeyToken="b03f5f7f11d50a3a" culture="neutral" /--> <bindingRedirect oldVersion="0.0.0.0-8.9.9.9" newVersion="9.0.0.0" /> </dependentAssembly> 5) Restart Visual Studio 2008. All fixed!

"A computer lets you make more mistakes faster than any invention in human history - with the possible exceptions of handguns and tequila." -- Anonymous Well, I downloaded Visual Studio 2008 Beta 2. I mounted the image as a virtual DVD with the free VCDControl Tool on Windows Vista Ultimate, 32-bit. I uninstalled the Orcas BETA 1 from Control Panel "Programs and Features", which does a chain uninstall of all the bits. Now I am ready to install the BETA2. I click on the SETUP.EXE from off the virtual DVD drive and nothing happens. Try several times. OK, that doesn't work. Let's try executing the .msi instead. Uh-Oh. The msi tells me I have to install with Setup.exe, which I already know doesn't work. Reboot, try again, same BS. FIX: Copy everything from the VCD drive onto a folder on your phyiscal hard drive, and run Setup.exe from there. That should fix it. Everything else about my install went perfectly, and I didn't even need to repair Visual Stud...

Well, unless you've had your head buried in endless code and don't ever come up for air, you know that Visual Studio Codename "Orcas" BETA 1 is out, and you have two choices: 1) Download all the pieces for a VPC installation and run it in a VM, or 2) Download the iso image and install it on the machine proper. I've never been enamored of number 1; I just don't like the feeling of running something in a virtual machine and dealing with all the memory and other issues; and besides, I want to really test this thing out and the best way to do that, in my book, is to take the plunge. Now of course the question becomes -- is it going to be happy with being on the same OS as Visual Studio 2005, and vice-versa? For me, the answer is "yes". So far I have noticed nothing unusual at all. Each guy acts like he knows nothing about the other, and as far as I'm concerned, that's perfectly fine with me! They do mention prominently that when you uninstall Orc...