Re: Identical binaries from same source code

Tech-Archive recommends: Speed Up your PC by fixing your registry



On 13 mar, 16:36, Jon Skeet [C# MVP] <sk...@xxxxxxxxx> wrote:
The CLI spec gives details of the PE format, but it's possible that
there are some implementation-specific fields that are being generated
every time.

We want this to be our last alternative.


By the way, I wouldn't set the GUIDs and times to zero - I'd choose
appropriate values and always reuse those.

You are right. We are setting zeroes in our tests. The idea is to
reuse good values as you say.


Note that if you sign your assemblies, all of this editing will
probably (hopefully, even) invalidate the signature - in which case the
suggestion at the top of this post is probably the only practical one.

We don't need to sign the assemblies.

Would it be possible to make the CRC comparison ignore specific parts
of the binaries, so long as you could explain that they don't affect
the behaviour of the code? That way we wouldn't need to work out what
values to use for the new binaries, just reasons why they're not
important.

This is not a solution, they must CRC it easily. We can't control this
process.

We are getting good results using mono-cecil. It's almost done.

Thank you all very much.
.



Relevant Pages

  • Re: Identical binaries from same source code
    ... Consulting the spec as the last alternative? ... Another alternative might be to look at the Mono compiler source code - ... appropriate values and always reuse those. ... of the binaries, so long as you could explain that they don't affect ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: Measuring OO Reuse
    ... I've been tasked with designing metrics to help track progress on a ... measuring reuse. ... accessed in different assemblies, it is reused. ... subject matter context that determines reuse value. ...
    (comp.object)
  • Re: Identical binaries from same source code
    ... I meant we prefer to use well tested third libraries rather than ... manually parse the binaries by ourselves. ... the fact that the assemblies *aren't* signed makes it simpler. ...
    (microsoft.public.dotnet.languages.csharp)
  • RE: ASP.Net 1.1 shadow copy + reflection problem
    ... I use SC explicitly since I need to load libraries ... the bin then SC would be on by default and the binaries would not be locked. ... I needed to be able to update the binaries and so I activated the SC ... Now I am experimenting strong naming the assemblies since I read that if you ...
    (microsoft.public.dotnet.framework)
  • Side-by-side examples
    ... I have a collection of binaries that are developed in VS2005. ... system registers these binaries and uses COM to interact with them. ... Side-by-side assemblies seem to be a good choice. ... some sample code/examples would be very helpful. ...
    (microsoft.public.dotnet.framework.interop)