Bug 42020 - Xamarin downloading .zip files on Compiling
Summary: Xamarin downloading .zip files on Compiling
Status: VERIFIED FIXED
Alias: None
Product: Visual Studio Extensions
Classification: Xamarin
Component: Android ()
Version: 4.1.0 (C7)
Hardware: PC Windows
: High enhancement
Target Milestone: 4.3.0 (C9)
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2016-06-21 02:03 UTC by Reader Man
Modified: 2016-11-22 18:07 UTC (History)
8 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:
VERIFIED FIXED

Description Reader Man 2016-06-21 02:03:49 UTC
# Steps to reproduce
When Opening a Xamarin.Forms solution, and compiling it for the first time on a fresh VS 2015 installation, it will go and fetch some .zip files from the net, and that will take a long time, depending on the internet connection speed.
And Visual Studio, will look like it has hanged while compiling the solution.



# Expected behavior
So, it should first Show a dialog describing what is happening in the back ground, and maybe some progress indication of how much downloaded, and what is left.
Plus, maybe there should be another way to download these files, and put them in the correct place, like having a setup.exe file, that can be downloaded once, and it will install the needed files, to any fresh VS 2015 installation.


# Actual behavior
VS 2015 update 2, looks like its hanging while its compiling the solution.

# Supplemental info (logs, images, videos)


# Test environment (full version information)
OS: Win 10
IDE: Visual Studio 2015 update 2
Xamarin: installed 4.1.0.530
Solution using Xamarin.Forms nuget 2.3.0.49
Comment 1 Reader Man 2016-06-21 17:10:22 UTC
this was also written here:
https://github.com/dotnet/roslyn/issues/12128

as i don't know if this should be reported to Xamarin or Microsoft.
Comment 6 Reader Man 2016-06-22 22:54:48 UTC
Just to be clear on the timing on when it happens:
Fresh installation of VS 2015
Creating or opening a Xamarin.Forms solution.
Then compiling it.

these steps will clearly show the problem.
and a bigger issue, if the developer thinks that there is something is wrong or gets tired from waiting and cancels the build/compiling.
the downloaded .zip(s) get corrupted, and further compilation will not work at all unless the developer discovers the problem, by searching the internet, and deletes the corrupted.zip(s).
Comment 7 Daniel Cazzulino 2016-06-23 13:29:34 UTC
Yes, we know how to reproduce it. The thing is: we can't redistribute Google's binaries ourselves, they have to be downloaded on demand (since they are *big* and we don't know which ones you'll need/use).

The corruption of the zips will be fixed in our next release.

We're looking at ways to make the long-running process more obvious to users, just like VS does for other long-running stuff (like updating the VS MEF cache, initializing VS templates, loading solution projects, etc.)

Thanks for your patience while we implement a better and more resilient experience given the external limitations we have.
Comment 8 Reader Man 2016-06-23 15:06:47 UTC
Thanks for putting it in your agenda.
Comment 9 Daniel Cazzulino 2016-09-16 13:05:30 UTC
Turns out we couldn't find a way to listen to the MSBuild ongoing process for this, so we are still looking for a way to solve this.