VS 11 does not pay attention to install location - visual-studio

I've download VS 11 Developer preview. I do not have sufficient disk space in my C drive, so I entered "E:\Program Files\Visual Studio 11\" as the install location and the installer continues, but after a while, my C: drive goes out of disk space and I get the following error in the log file:
(vs_professionalcore) failed: Error: 1601 ErrorMessage: Out of disk
space -- Volume: 'C:'; required space: 606,561 KB; available space:
178,516 KB. Free some disk space and retry.
Note that no files gets copied to my E: drive during the installation process. What's the solution?

This isn't unique to VS 2011. All versions of Visual Studio (at least all the .NET flavors I have used since 2002) have strong dependencies that can only installed onto the C: drive.
These dependencies can be stuff like the .NET 4.5 and various runtime components. The IDE itself is all that can be placed on another drive.
You usually see this in the installer where it will show that after changing the drive letter still large parts of the C: drive will be used.
I decided to fire up a VM and see what the difference was between C drive install and E drive install on VS 2010 Ultimate. As you can see the difference was only ~2GB with the bulk being on the C drive still as I stated above.
Visual Studio 2010 Ultimate C Drive Full Install
Visual Studio 2010 Ultimate E Drive Full Install

Unfortunately I don't believe there is a solution here. This sounds like a simple bug in the installer. The only real option is to file a bug on Visual Studio Connect to ensure it's fixed for RTM
http://connect.microsoft.com/visualstudio
Note: This is a preview release so quality is not that of RTM. It's certainly a case I would expect to be fixed for RTM though. When I worked in Visual Studio QA in particular often installed to non-default locations.

Related

How do I install Visual Studio Completely in D drive?

I need to install Visual Studio 2022 for Unity. I specified the installation location in my D drive
but C drive's space runs low. Thus, I could not install it. I don't know what components get installed. I've looked for many methods, and mklink caught my eye but not confident about it. If there was any other way to, I would be glad to hear it.
No, unfortunately most of Visual Studio still gets installed on the main drive. Regarding to this forum thread 75% of VS gets installed on the main drive and just 25% on the chosen drive.
So you have no choice but to make space on your c drive.

Installing visual studio community won't change the installation directory

I just downloaded Visual Studio 2017 community and tried to install it but when I did I made directory D: separate from main directory C:
Everything I had in installation had message not enough space even tho i have around 300GB free space in D: and around 50GB in C:
Installationg has around 50GB and it is showing me the C: drive memory with that message that I don't have enough space even tho it is changed to be installed into drive D:
Here is an screen shot of installation:
When we choose another drive to install VS, it still requires the space on the system drive, please have a look at this: Why Visual Studio 11 Requires Space on the System Drive, because the shared components, packages and Windows Installer and package caches still need to install on the system drive.
From the screenshot, it looks like you choose all workloads or most of them, it is huge and usually we can select the needed workloads per your development requirement, you can refer to Visual Studio Community 2017 workload and component IDs to know the detail description of those workloads, then uncheck some workloads to make it small.
After the initial installation, we still can modify it to install more workloads through run this installer and click the icon beside ‘Launch button, choose ‘Modify’ to select more workloads or individual components to install.

Recover Visual Studio installation from external hard disk

I recently had to replace my hard disk on my laptop, which contained my Visual Studio installation. When the new hard disk was added, unfortunately the person involved in setup has put Windows 8.1 on an internal SSD (I am using Dell XPS) and made this the system drive -- since this is ~30GB only, re-installing Visual Studio is not an option it seems, as my understanding is that even if the install path is changed to the new hard drive, VS will still need significant space on the system drive (I have ~6GB left).
My old hard drive is being used as an external drive, and it seems all the data is fine, and can see that the VC compilers work fine via the command line. My question is, if there is a method by which I can get the Visual Studio installation up and running on my old hard drive(external), as all the components needed are present -- is there a config file or some such that I could use, and manually enter the registry information to make it work? Is there anything else I could do?

How to stop Visual Studio 2010 SP1 "configuration" every time I start an Office 2010 app?

A recent Windows Update or software installation seems to have broken my one week old Dell XPS 17 which comes pre-configured with Office 2010 Home and Business edition. I installed Visual Studio 2010 on top and then SP1 and then the Silverlight 5 Tools for Visual Studio. This is all on a 64-bit version of Windows 7 Ultimate edition.
Whenever I start Outlook or Word an annoying Visual Studio 2010 "configuration" dialog pops up and runs for several minutes, locking the Office 2010 app out until it's completed.
I found a report of the problem on Microsoft Connect for the Release Candidate of VS2010 and the suggested fix was to add a "missing" folder Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE**FromGAC**
That empty folder is already there.
Another suggestion was to "repair" Office 2010. Done that. Again it didn't fix the problem.
Anybody know how I can fix this. I'm using an SSD to make my system lighting fast from boot up. This is making it just as bad as a very slow hard drive!
Okay I could fix it on my PC system.
Start the Procmon.exe tool from sysinternals
Start OL (or another apps like Word) and wait until the VS reconfigureing windows apears.
Stop Procmon.exe
Look to the "Z:" resource OL is looking for remember the reg path
Open REGEDIT and search for this reg path
If found (you should) rename drive Z: to another existing drive like K:
Repeat step 4. to 6. util no more Z:'s are available
Start OL again and bingo the reconfigure windows from VS will not popup any more.
I would suggest to use the C: drive instead of K:, becasue the C: drive always exists.

Microsoft Visual C++ 2010 Express project creation failed

Before I begin, I would like to note that I am running Windows XP SP3.
Recently, I noticed that my installation of MS Visual C++ 2008 Express would no longer create new projects, only open previously created ones. Please note that it has been able to create projects in weeks prior.
Rather than trying to find a solution for the 2008 version, I took the opportunity to upgrade to MS Visual C++ 2010 Express. After downloading and installing it, I encountered the same problem, only this time (will not create new projects), I noticed a message near the bottom of the window that read "Creating project '[project]'... project creation failed". I then uninstalled both versions (2010 and 2008), rebooted, reinstalled 2010, and... same problem.
I then followed this tutorial, where I (re)registered VsWizard.dll, then modified the owners of HKEY_LOCAL_MACHINE\SOFTWARE\Classes\VsWizard.VsWizardEngine.10.0 and HKEY_LOCAL_MACHINE\SOFTWARE\Classes\VsWizard.WizCombo.9.0 to Administrators, and gave all users Full Control/Read permissions. This seems to be the solution that a number of other websites suggest, but it still did not help.
Thus, I am at a loss of where to go next. I, unfortunately, have no Restore Point to fall back on, so I need a different solution, if possible. Any help would be greatly appreciated.
I had a lot of issues and frustration with solving this "issue", nothing worked.
I changed my default ProgramFiles directory to my D drive as my C drive runs a SSD. By monitoring the visual studio process, I discovered that it was looking for MSBuild / Microsoft.Cpp on my D drive (not on my C drive, where my operating system is located). This was what caused the issue.

Resources