How to automatically detect and release DLLs that have really changed?

Question

Whenever we recompile an exe or DLL, its binary image is different, even if the source code is the same, due to different timestamps and checksums in the image.

But our quality system implies that every time a new DLL is published, related validation tests must be run again (often manually, and take a considerable amount of time.)

So, our goal is not to release DLLs that haven't really changed. Ie: with an automatic procedure (script, tool, whatever ...) that detect different Dlls based only on the informative information they contain (code and data), ignoring timestamps and checksum.

Is there a good way to achieve this?

Answer 1

Base version information and update version information only when changes are made.

Answer 2

Make your build tool double dll. No matter what differences exist between them, the result of timestamps or checksums is guaranteed. Now you can use this information to compare with your next build.

Answer 3

, , , - . .

Answer 4

. , , - , , dll/exe. , dll/exe, , .

, . , . Portable File Format , , . , , dll/exe, , .

, - , , . , , .