Hey all, this article is very helpful except that nothing can be changed in these install paths.
Even in the screenshot, it shows the greyed out install locations that can't be changed.
⚠Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
@WildYorkies Thanks for your feedback; we appreciate it. Question: Are you trying to modify a previous installation? If so, please know that the Installations locations feature works only for new installations of Visual Studio. That being said, we can update the page to make this clearer, and we can update the screenshot accordingly.
Thanks @TerryGLee . I'm trying to change the install location for _new_ packages. For example, I don't want 20 gigs of xamarin files going on my C drive. I want them on my D drive instead.
However, because the locations are greyed out, I cannot change them. Not sure why.
I'm having the same problem. I already have the core installation of Visual Studio in my second drive (D), but the extra tools (Xamarin, dotnet, etc.) are set for my main drive (C) and cannot change them.
I have the same issue. I'd like to move the "Shared Components" location to a different hard drive, but it's just greyed out and I can't change it, without uninstalling/reinstalling Visual Studio entirely
What I did was to move the files from C:\Program Files (x86)\Microsoft Visual Studio to D:\Program Files (x86)\Microsoft Visual Studio and then use mklink /j to make a directory junction so everything can still think that the files are in C:.
$o the clear micro$oft $olution i$ to download the profe$$ional (or higher) ver$ion. Way to go micro$oft.
You can't move these directories after installing anything at this time. This is because many packages we install (first- and third-party), once installed, must keep going to the same location and themselves cannot be moved.
Problem here is clearly some inept focus on Microsoft's end as to what a high priority issue is. This is a high priority issue! The thing automatically picks your existing drive for beta installations, even if you choose [Custom Installation]. You end up in a position to where you have to remove your original installation & re-install that to another drive, so the product will automatically pick the alternate drive. It's really pathetic that you would waste so many programmer's time on something that should be less than a 1-day fix for your company on its end, to automatically prompt for drive location for all beta product installations would be a best case scenario.
Most helpful comment
Thanks @TerryGLee . I'm trying to change the install location for _new_ packages. For example, I don't want 20 gigs of xamarin files going on my C drive. I want them on my D drive instead.
However, because the locations are greyed out, I cannot change them. Not sure why.