Bug 15733 - Assembly binaries are nondeterministic when rebuilt.
Summary: Assembly binaries are nondeterministic when rebuilt.
Status: RESOLVED INVALID
Alias: None
Product: Compilers
Classification: Mono
Component: C# ()
Version: unspecified
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: ---
Assignee: Marek Safar
URL:
Depends on:
Blocks:
 
Reported: 2013-10-27 16:11 UTC by Brian Berry
Modified: 2013-10-28 03:11 UTC (History)
1 user (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 GitHub or 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 INVALID

Comment 2 Marek Safar 2013-10-27 16:45:47 UTC
I share your pain but that's what .NET standard requires. It states that MVID (UUID) can be used to distinguish between two versions of a module. That means same source code will produce different assembly.
Comment 4 Marek Safar 2013-10-28 03:11:39 UTC
Yes, that's what people end up doing. I'd just monodis the assembly then remove/replace MVID and do binary compare on that. It may not be exactly what you need performance wise but that's the simplest way I can think of.