Bug 57625 - Argument order to mtouch can vary between builds
Summary: Argument order to mtouch can vary between builds
Status: RESOLVED FIXED
Alias: None
Product: Visual Studio Extensions
Classification: Xamarin
Component: iOS ()
Version: unspecified
Hardware: PC Mac OS
: Normal normal
Target Milestone: 15.4
Assignee: Emanuel
URL:
Depends on:
Blocks:
 
Reported: 2017-06-20 11:43 UTC by Rolf Bjarne Kvinge [MSFT]
Modified: 2017-07-20 20:50 UTC (History)
5 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:
RESOLVED FIXED

Description Rolf Bjarne Kvinge [MSFT] 2017-06-20 11:43:23 UTC
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?).
Comment 1 xamarin-release-manager 2017-07-20 20:50:23 UTC
Fixed in version 4.8.0.59 (master)

Author: Emanuel
Commit: 7d98e5c7f9783010d1700b63d02ac0f25bc01f6c (xamarin/XamarinVS)
Comment 2 xamarin-release-manager 2017-07-20 20:50:59 UTC
Fixed in version 4.7.0.820 (d15-4)

Author: Emanuel
Commit: 66ceeb77549c095fabd6a5642f2b52dc528740df (xamarin/XamarinVS)