Reputation: 3135
Following the idea of this question:
Is there a way to compare two .NET .dlls from the point of view of the CLI instructions and native instructions, to ensure that they are exactly the same, mean will behave exactly the same at runtime?
Typical use case is: you want to ensure that you have a reproducible build environment: that all developer machines compile exactly the same code as the build server.
The hash of the .dll file is not sufficient as the .NET compiler doesn't guarantee two identical .dlls are produced when compiling the same source code twice (and effectively changes a few bytes at the top and at the tail of the dll).
This question is similar to this former one, but the question didn't focus on the functional/behavior aspects of the .dlls, resulting in unclear answers and confused conversation.
Upvotes: 0
Views: 70
Reputation: 3444
One possible way could be to write unit tests. But not sure if it will also cover the statement:
from the point of view of the CLI instructions and native instructions
Upvotes: 1