Install Visual Studio 2008 Sp1 on "D" Drive - visual-studio

I am trying to install VS2008 sp1 to my work machine - it has a pathetic 10Gb C drive. The SP1 bootstrapper doesn't give the option to install items to D, only C. It needs 3Gb free and the machine only has about 700Mb.
VS allowed me to install to D originally why not the SP. The only thing I can think of that it requires system files installed in Windows etc, but I can't believe there are 3Gb worth of system files?

Worth a read:
http://blogs.msdn.com/heaths/archive/2008/07/24/why-windows-installer-may-require-so-much-disk-space.aspx

I was faced with the same problem, and ended up moving my Outlook archive.pst and the windows.edb (the new live search index file) over to D: to make room instead of trying to cram a square peg into a round hole with SP1 splitting drives. A huge help in this regard is WinDirStat, which scans a drive of your choice and identifies the size of every folder and file so that you can reveal some random large entities and move them if you can.

If you have an empty partition, you can try to create a mounted drive (i.e. map the partition to an empty folder on the C: drive) and see whether the SP1 bootstrapper will be able to use it.

I also ran into the same problem on a server that only has 20gb on the C: drive. I found a way to free up enough space to get the job done by reassigned the system's virtual memory allocation to use D: drive instead of C:. This freed up about 4gb in my case.
On Windows XP the place to set this is in My Computer system properties, Advanced tab, Performance Options:
http://support.microsoft.com/kb/308417

I had the same problem with VS2008 installed on a C: drive that was only 12Gb in size.
I uninstalled VS2008 completely by following the manual steps in this page,
and then by using the auto-uninstaller:
http://msdn.microsoft.com/en-us/vstudio/bb968856.aspx
I then rebooted the machine.
I then re-installed VS2008 on the E: drive.
I then rebooted the machine.
I was then able to install SP1 - as now it did not need quite as much space on C: drive.

When you say "10Gb C drive", do you mean it's a 10-gig disk or a partition? If the former, you should really be looking at replacing the drive - it's old, and I'd be starting to worry about how much longer it has to live.
If the latter, then assuming that the C: drive restriction can't easily be worked around, then I'd look at increasing the size of the C: partition. Depending on how full the remainder of the drive is, this can take a while. I'd also be considering spending some tens of dollars ($40 or $50, I'd guess) on a partition manager from someone such as Acronis or Paragon. Kick it off just before you finish work for the day - it may take several hours, especially if the disk's fairly full.

Are you in place upgrading your current version or have you uninstalled VS 2008 Gold? By default, the installer won't let you change the directory if any existing versions of VS are installed.
To move the installation, you will need to uninstall all editions of 2008 you have installed (including any Express Editions) and then the choose installation location option should enable.

I vaguely recall having this happen to me when I had Office 2007 installed first before VS 2008. I don't remember what options that I had installed for Office 2007.
Update: I remember now it had to do with the fact that I had Visual Studio Tools for Office already installed. When I upgraded my computer I did a clean install of everything without problems by installing VS 2008 before installing Office 2007 and VSTO. So most likely you have to uninstall whatever is causing VS 2008 to want to go to a specific drive.
Even if you do get it to switch drives it still is going to put a lot of stuff on the system drive.

You could also download the full VS2008 SP1 ISO image from here.
Then you can either burn it to DVD or use a tool such as Virtual CD-ROM Control Panel from Microsoft to mount the ISO as another drive.
After mounting the ISO as a virtual drive, you can run the SP1 install from there.

Related

Move Visual Studio 2022 to Another Drive after Installation without Reinstalling

A couple of months back, most probably in November last year, I had to install Microsoft Visual Studio on a drive(D) other than C because my C drive did not have enough space to host the software. Two weeks ago I cleaned up my C drive and now I want to move the Visual Studio installation to the C drive because the C drive is located on an SSD drive, and the other drives are on HDD.
The Microsoft Official Document reference says that I have to reinstall my Visual Studio. But always there are some exceptional experiences for the users other than the official documentation statements.
One very important cause for my avoiding this reinstallation is, that I live in such a corner of the globe where 30GB will take me like 3 to 4 days to download. Moreover, it will also hamper regular tasks and the custom settings and tweaks I have applied to my development environment.
That's why I am writing this to avail community help if anyone has ever experienced such an issue and solved it anyhow.

Upgrading Visual Studio

I am upgrading Visual Studio and it's 14 gigs in size. My worry is with my internet connectivity.
If my connection fails, would it start afresh or continue with what's not loaded in the system?
I know this isn't a programming question but I would appreciate your help.
I can't give you a definitive source, but in my experience the VS installer simultaneously downloads and installs its components. The already downloaded components are locally stored (I think even in the directory from where you start the installer) and will be re-used if you cancel the installer and restart it. That way you could even share the downloaded files among multiple computers.
However, as state in the comments, there are offline installers available. If your connection is wonky, the web installer might even be a better bet since your ISO or whatever may or may not be resumed if partially downloaded.

Installing Visual Studio on another drive

I will be getting another pc where drive C: will be SSD and the rest of the drives HDD. The SSD size is significantly smaller so I don't want it to get full from just codes and Visual Studio stuff.
I came across this guide:
http://www.placona.co.uk/1196/dotnet/installing-visual-studio-on-a-different-drive/
but at the bottom, it says that it's not a permanent solution because updates will still get installed in drive C:
I haven't tried this yet but:
does the latest version of visual studio allow you to install on another drive?
would it be better if I create a VM (on another drive) then install Visual Studio there? any downside on developing while in a VM?

Visual Studio Professional 2013 requires up to 10GB across all drives...even HP_TOOLS(F:)?

I'm using HP ProBook 4520s and I'm trying to install Visual Studio Professional 2013 on Windows 7. I have not advanced my installation because I reached a window that says, "Setup requires up to 10GB across all drives."
In My Computer I have:
Local Disk (C:) 109 GB free,
HP_TOOLS (F:) 1.48 GB free of 1.98 GB,
and Paging Partition (K:) 12.1 GB free of 14.9 GB.
I assume that if I go ahead with the installation that not all components will install correctly due to the F: drive and the Paging Partition having limited space(it says 12.1GB are free, but maybe in reality 9.99?). So what solutions are available so I can install VS 2013 on my PC? Maybe this?
It does not mean you need that space on each drive. That would be stupid. It means it needs that space once and probably some of it on the drive you install too and some of it on your system drive.
Go ahead and install it.
In your case it will install everything on C: and won't use any space on the other drives.
The warning is aimed at users who want to install to a non-system drive, (ie not the C: drive). In those cases it will install some data to the C: drive and some data to the drive that was selected for installation.
The same seems to apply for Visual Studio 2015 too.

Error when installing Visual Studio 2005 on Vista

I am getting the following error when trying to install Visual Studio 2005 on my 64bit, Vista computer:
"1305.Error reading from file
C:\Program Files (x86)\Microsoft
Visual Studio 8\Microsoft Visual
Studio 2005 Standard Edition -
ENU\SITSetup.dll"
I have successfully used the same DVD's to install Visual Studio on my old XP machine, and I can find the file (SITSetup.dll) on the DVD...and copy it off...so I don't think this is a case of having a bad DVD. At the time the error message pops up, I can see the file on my hard-drive, but it has a 0 size.
I've Googled this problem, and found some ideas, but nothing has worked thus far. Any suggestions would be appreciated.
I have to confess on this..especially since someone voted for the question.
Everything I said in my original posting about using the disks successfully in the past -was true. However, after innumerable shots at trying to get this install to work, I finally went back and looked at the DVD, and found that either myself, or one of my kids, left traces of food stuck to the underside of the DVD. After cleaning the DVD off, the install worked fine. This is embarrassing.
I assumed the DVD was fine because I had used it before, as well as being able to copy files off it. However, the last time I used it was years ago, and sometime in between then and now...something got on it. I guess the lesson here is never skip the basic checks!
I just installed it yesterday on my Vista box (32-bit, which may be the problem). It seemed to go through fine so I don't know what to tell you other than than when I first launched the app it notified me of "known compatibility issues" and recommended that I install both the SP1 and Vista SP! updates. No further issues past that.
As such, I would suspect either a problem with the 64 bit OS (though Microsoft says it's fine...) or other software on your machine. If you have a virus scanner running, for instance, disable it while installing.
If your Vista machine is a guest running under VMware, try copying the entire DVD to your hard drive and install from there.
I don't know if the same random glitches occur on real machines.
I can confirm that this is a problem for me on Windows 2008 Server while not on XP or Vista (all 32-bit). Not sure why there's any kind of issue here but it seems to be permissions related.
Also tried run as administrator etc but no luck.

Resources