PDA

View Full Version : Visual Studio .NET Install Problem




compukeith
12-22-2003, 10:18 PM
I reformatted my laptop (Dell Inspiron 5100, P4 2.8Ghz, 512MB RAM, WinXP Pro) on Friday night because it was running too slow. Then, on Saturday I started reinstalling stuff and Sunday I got a virus because of a flaw in IIS 5.1. So, I reformatted again as I hadn't gotten much installed.

Anyway, I've spent hours today trying to get Visual Studio .NET to install. I put the first disk in only to get told to put in the "Windows Update Components" disk. So I tried to get that disk to install only for it to freeze when it's installing the setup files. So I tried installing the file seperately per a help file on the CD. I ran the file "bootstrap.msi" from the CD and it freezes with about 10seconds left every time I've run it (a total of about 10 times now).

The help file says that VS.NET cannot be installed without the update components first.

Anyone else have this problem and found a way to fix it or have possible causes? I was able to successfully install VS6.

BTW, if anyone says that it's because I'm trying to install it with VS6 installed, that's not it - before I formatted, I had VS6 and .NET installed perfectly.

Thanks in advance.
-Keith




compukeith
12-26-2003, 12:52 PM
Just wanted to bring this thread back to the front. Anyone got any ideas?

huppel
02-23-2004, 07:30 AM
I've encountered the same problem as you where setup can't read the dll from the cd.
You can manually install the bootstrap by doing the following:
Copy directory stucture where the dll should be from the update component cd into a temp directory on your harddisk. (Can't remember the subdir name, but it should be in the errormessage, also incule the win subdir). Then copy the dll that can't be read from the 1st disk (should be in the same location in hte subdir). Also copy bootstrap to the tempdir. Run it from there, it should install now.

compukeith
02-24-2004, 06:45 AM
I ended up getting everything installed. I just tried again about a month after the initial post and it worked. Something internal must have just kicked into place.