Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
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
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.
Created attachment 17095 [details]
Screen capture that demonstrates the current behavior
## Steps to replicate
1. Ensure your current version of Xamarin is lower than the latest version available in one of the updater channels.
2. Navigate to "Tools > Options > Xamarin > Other" in Visual Studio.
3. Click the "Check Now" link.
4. Click the "Download" button to start the download.
5. Close the modal window to continue working.
The download pauses when the modal window is closed.
(See also the attached screen capture.)
## Possible improvements
a. Allow the download to continue after the modal window is closed.
b. There might already be plans to integrate all Xamarin updates into the "Tools > Extensions and Updates > Updates > Product Updates" menu to be more closely aligned with the way Visual Studio updates are presented. It looks like that menu depends on a web browser to perform the downloads outside of Visual Studio. I imagine the old Xamarin update dialog might simply be removed once Xamarin updates are fully integrated into the "Extensions and Updates" dialog.
Related UserVoice requests for cross-referencing:
*** Bug 52442 has been marked as a duplicate of this bug. ***
Although we agree this would be a very nice improvement, we will have to resolve this bug as not on roadmap.
Instead, we're moving towards the integrated Visual Studio setup (as it is already for VS2017), and phasing out the legacy Updater.
Marking the bug as resolved.