The issue is the fact that the very process of building the installer requires a new commit, so I want to understand why it happens, and then come up with a workaround for that. I think I'm on the right track here - by trial and error I figured out that sha1 is generated from the file specified in the File property. I ended with identical value, when I used the following tool to get the SHA1 for that file:
https://emn178.github.io/online-tools/s ... cksum.html
So it looks like Advanced Installer is calculating SHA1 for my executable whenever I save the AI project. This is not ideal, because in C# world at least, building the same executable each time, does not produce the same binary output for identical inputs (more info about that
https://stackoverflow.com/questions/892 ... ling-again).
The question now is if there is a way to stop AI from embedding that value in the project (I'm guessing not), or at the very least can I safely ignore it and not check it in, whenever CI server completes a build (in other words, what is that value used for by AI)?