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 or GitHub 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.
Currently, if you install a Beta from a Beta channel, and then go to the standard channel, MonoDevelop will not display information about the stable channel. It will just show the Beta one.
We need a way for users to downgrade to the stable channel after they have experienced problems with the Beta.
It would help if we also kept the files around so the user can do this without MD's intervention.
I have a patch ready which needs to be tested.
Could you attach the patch here?
Or perhaps we could check it post-branching to try it out?
The patch works as advertised. However the UI for the updater is an all-or-nothing affair. If you disable the Beta/Alpha channel you must downgrade *all* products to their stable equivalents. Similarly if you then re-enable the Beta/Alpha channel, all products must be updated. It is not possible to upgrade or downgrade just one component.
Should this patch be pushed anyway even though the user experience is less than stellar? We can do some work on the client side UI to give people the chance to opt out of upgrades/downgrades for the next cycle.
Oh, i tell a lie. It is possible to opt-out, but it happens after the update has been downloaded.
I'm pretty sure we want that patch on the server ASAP, but unfortunately the client-side UX is really poor for switching channels.
However, I have an idea for fixing it, with something that would combine the best attributes of the old updater and the new updater.
The "check for updates" UI will look somewhat like the old updater UI - an easy way to see what's available in all the channels. This would be a list that would show all the items in each channel with expanders for release notes, and have an easy way to switch between channels - tabs or an updater.
The items in the lists would be the stable, beta and alpha versions of all detected installed products. MonoDevelop would check each installed product's version against the available channels, and figure out which channel it's from, and automatically download updates from that same channel for that product. These would be downloaded and installed using the current automatic download system.
Each item in the update list would show its current status - "installed", if it's installed and up to date, "switch" if it's a different channel to the current installed version, "downloading" if it's being downloaded. Clicking on "switch" would start that item downloading via the automatic downloader, and cancel any other channels' downloads for that product.
This would allow different products to be on different update channels, and would provide users an easy way to see all the available versions.
I've pushed the patch to master so it can be built/pushed to production whenever suits. I'd say do it a couple of days after the next release cycle just in case there are some issues which prevent people from getting the new releases.