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.
Could you please check if both packages are signed? If not, Windows detects they are both diff product and install them as separated packages. If they are, then this is a bug
@Jose Both builds are signed, here is the screencast: http://www.screencast.com/t/I7XfruTb
Fixed in version 0.35.99.37 (master)
Author: Jose Miguel Torres
Commit: e98f800e81b7e61d6d86abc48622a818a23d74dd (xamarin/profiler)
Looks like that for MSI only major, minor and build are taken into account to perform an upgrade so that MSI will no upgrade from 0.35.99.10 to 0.35.99.11. So the fix will allow the 0.35.99.11 to be considered as an upgrade from 0.35.99.37 on.
Verified with 0.34.0-36.msi