Re: Comparing two EXEs
- From: "Brion L. Webster" <brion.webster@xxxxxxxxxxxxxxxxxxxxxx>
- Date: 6 Jul 2005 09:24:33 -0700
Bob wrote:
I know this is slightly technical, but I couldn't decide which group to drop it in.
When we make builds of our products, our QA department wants to check the executables to ensure that the ones that were not supposed to change in fact did not change. So they do a byte compare of the new release with the last release. Unfortunately, when we build, we recompile all EXEs. There must be date/time information (or something else?) in the EXEs that make this byte compare fail even if the code did not.
My question: Is there a way to compare an EXE to a previous compile of the same EXE and determine if there were actual code changes?
If you do something like comp file1.exe file2.exe /A, you'll most likely see changes. If you write a custom app to just compare resources, like version #, comments, etc., you could add logic to say something like "if the file size, version #, and other random stuff are the same, pass the file, else alert".
-Brion .
- References:
- Comparing two EXEs
- From: Bob
- Comparing two EXEs
- Prev by Date: Re: Freedom!
- Next by Date: Re: Freedom!
- Previous by thread: Comparing two EXEs
- Next by thread: Re: Comparing two EXEs
- Index(es):
Relevant Pages
|
