Hey Russell, That's great feedback. I like the concept. It's probably only the PE timestamp as you identified, we should have an option to zero it out.
Jb On Tue, Apr 7, 2015 at 7:45 PM, Russell Wallace <[email protected]> wrote: > I'm testing some code using Mono.Cecil, trying in the first instance to > make sure the operation of reading a CLR program and writing it out again > unchanged is idempotent, that is, the first time this is done a few bytes > might change just because Cecil does things differently compared to the > original compiler, but doing it a second time should change no bytes. > > From what I can see so far, this almost works, except that one group of > three bytes changes; it looks like a timestamp. > > Is there a way to fix this, i.e. set the timestamp to 1/1/70 or some other > constant value? > > -- > -- > -- > mono-cecil > --- > You received this message because you are subscribed to the Google Groups > "mono-cecil" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- -- -- mono-cecil --- You received this message because you are subscribed to the Google Groups "mono-cecil" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
