After numerous attempts at installing VS 2008 on Vista machines, I'm about ready to switch to vim. At least I can use apt-get for vim.
The process has basically gone something like this:
- Fire up the installater
- Choose my installation options
- Watch the progress bar do really strange things during the .NET Runtime 3.5 step
- Notice the "your computer requires a reboot to complete the Windows update process" indicator in the taskbar
- Watch the progress bar do absolutely nothing during the .NET Runtime 3.5 step
- Go eat dinner
- Come back to see that installation has failed
- Oh, and that setup.exe crashed
- Reboot, switch to Macbook for a while
- Start installation again (clench sphincter*)
- Select "Normal" install because I'm too lazy to pick my options again
- Oh look, it worked
At first, I figured this was just a problem with my desktop (and potentially Vista 64). Sadly, I was wrong. I just stumbled through exactly the same process in a 32 bit Vista VM on my Macbook Pro. Yar!
* As an aside, "clench sphincter" is apparently more correct than "clinch sphincter", although it looks wrong to me.
Comments (9)
I have a new SR macbook, running 10.5 and running vista x86 business through VMWare fusion. Mounted VS2008 image through VMWare mount cd tools, it became visible in vista. Started install. Required 1 reboot, went fine. VS2008 Team Suite edition. Absolutely 0 problems. I also have VS2005 installed in my vista.
Most likey something is wrong with your vista installation. Anyway hope whatever I typed helps. Good luck!
VS 2005 worked fine for me, but 2008 Pro has given me nothing but problems. I should pay more attention, but it seems like Pro might be the one exhibiting the problems.
BTW, it happened on 2 different Vista installs. Weird stuff.
Yeah i think its your VS image
Yeah, it’s something *you* did wrong. You fucked up. It’s your fault. Installing programs is a serious fucking complicated thing, kind of like building a 747 from popsicle sticks, and you arne’t good enough for it. Jesus christ.
To be fair, it seemed like he was trying to be helpful.
You really should go with vim. That way, you will also have a lot more programming power at your fingertips. But I guess you already know that.
Once, I was forced to use VisualStudio for 3 months. I was coming from IntelliJ IDEA on Linux. Entering VisualStudio was like putting my programming fingers in a day-long prison, where I had to fight to get some decent code lines written. It was a pain in the a.., really. And that was just when it was running. Talk about a crashing piece of shitty software man.
One should think, that M$ would do better with their everyone-must-use-this-tool-to-develop-on-our-platform tool. But no.
It is a problem where the .NET 3.5 framework tries to install x86 components on your x64 system… just a .net framework 3.5 setup failed on a clean x64 vista for me. On a clean load i was successful in loading KB929300 and then restarting. Then installed KB110806 and restarted. Then ran .NET Framework 3.5 setup. USE x64 versions from the wcu\dotnetmsp\x64 on the image (i think thats the path) once you have the framework 3.5 on there correctly you are golden.
Kurt, just found this after attempting this on a Parallels VM’ed x86 Vista. The VS installer looks at the HOST OS hardware, sees it’s x64 (Macbook Pro 10.5.3) and attempts to install the x64 version of the bootloader (or whatever that’s called). It also fails installing the 32-bit version.
Oh, the joy.
By the way, my VS image is from MSDN and it installed correctly on my x86 XP machine. It’s an x64 vs. x86 issues in the VS installer. It looks at hardware and ignores the OS, which is pretty bad in that the development tool installer thinks it knows more than the OS.
It looks like the installer team is messed up.