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.
In bug #56563 comment #10 the customer provides two build logs, the second is a build without any changes.
In theory the second build should be much faster (since nothing changed), but this happens:
> A full rebuild will be performed because the arguments to mtouch has changed with regards to the cached data.
which occurs because the order of the arguments to mtouch changed: https://gist.github.com/rolfbjarne/1d9a66b6852d97ec99fac033927fda02
While mtouch could theoretically detect that these changes are inconsequential, I'd prefer not complicating an already complicated algorithm, and instead have VS provide the assemblies in a stable order (alphabetic order maybe?).
Fixed in version 188.8.131.52 (master)
Commit: 7d98e5c7f9783010d1700b63d02ac0f25bc01f6c (xamarin/XamarinVS)
Fixed in version 184.108.40.2060 (d15-4)
Commit: 66ceeb77549c095fabd6a5642f2b52dc528740df (xamarin/XamarinVS)