Bug 52447 - XVS installer for VS2017 takes too much space
Summary: XVS installer for VS2017 takes too much space
Status: RESOLVED UPSTREAM
Alias: None
Product: Visual Studio Extensions
Classification: Xamarin
Component: Installer ()
Version: 4.3.0 (C9)
Hardware: PC Windows
: --- enhancement
Target Milestone: ---
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2017-02-10 15:34 UTC by Rustam Zaitov
Modified: 2017-02-13 18:40 UTC (History)
5 users (show)

Tags:
Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.


Please create a new report on Developer Community with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:
Status:
RESOLVED UPSTREAM

Description Rustam Zaitov 2017-02-10 15:34:50 UTC
I wanted to try our products under VS2017.
I got a fresh VS2017 RC
The new installation wizard is nice – you just need to select components which you need.
I selected "Mobile development with .Net"
But I was not able to install it from the first time because it wants to consume 26.6 GB, but I have only 128Gb SSD (I also have 1Tb HDD, but this doesn't help). Obviously, my primary disk is SSD (where Windows is installed, and ProgramFiles and lots of others system dirs are stored)

Well, I don't know how to evict 26.6 GB from 128 GB SSD. I cleaned all NuGet caches, double checked that all data are stored on HDD, but still, I have to evict a few more gigs in order to have 26.6 GB of free space. The last option I had is to create junctions from some files/folders on SSD to HDD. I created a few junctions with mlink tool, with this arrangement I was able to move a few rather large directories from /Users/<UserName>/AppData to my HDD.

Long story short, I finally found 27 GB on my SSD, so VS installer was able to complete the installation. When I launched VS2017 and went to "Tools > Options > Xamarin > Android Settings" I found that installer was smart enough to found Android's SDK and NDK from my previous installation (which are stored on my secondary HDD). At this point, it is not clear why our installer pulls Android SDK which is not going to be used. I mean that installer pulled Android SDK into "c:\Users\<UserName>\AppData\Local\Android\android-sdk\" but VS doesn't use that path, because it will find SDK location from the previous installation (VS2015 I guess).

My question/confusion is why we need to download Android sdk and put it on default location if it is clear that it will not be used?
Comment 1 Daniel Cazzulino 2017-02-13 13:59:43 UTC
If you do have the Android components already installed, you should be able to individually uncheck them, no?
Comment 2 Daniel Cazzulino 2017-02-13 14:00:38 UTC
BTW, the VS2017 is NOT the "Xamarin Universal Installer", it's Visual Studio Installer. So, is the component wrong here?
Comment 3 Daniel Cazzulino 2017-02-13 14:26:46 UTC
After talking to Victor, we think this is a "Feature": you can manually uncheck SDK/NDK from the Visual Studio Installer.

Please reopen if that's not the case.
Comment 4 Rustam Zaitov 2017-02-13 14:48:44 UTC
@kzu yes I can manually uncheck them from the summary tab or Individual components tab. It looks like I missed it because "Mobile development" workload was not the latest I choose so the summary tab didn't highlight it for me.

Here is a screenshot http://www.screencast.com/users/rzaitov/folders/Default/media/4c068b08-038d-42ac-bb7c-2dff8e5c678a

Anyway, if it is possible to detect that dependency already installed then we should uncheck appropriate boxes (dunno is it possible or not)
Comment 5 Daniel Cazzulino 2017-02-13 14:53:09 UTC
It's upstream, so I'll resolve so. Victor can report & track it on devdiv, since this is a VS installer issue. (can you report there too? dunno)
Comment 6 Daniel Cazzulino 2017-02-13 18:40:10 UTC
There's 17+GB of "Google Android Emulator" component which you can also uncheck.