exe file that change each time you do a build (with no code changes). I have made a small utility that will generate a checksum for a. I aim to build the tool using a simple winforms app using If anyone has any tips on how I could write a little checksum tool that ignores the header info then please let me know. This possible solution is what I will be pursuing next. So now my quest is to see if I can generate a checksum tool that ignores certain parts of the header info and get the external regulators and internal team to use. Name etc, and have both the external regulators and internal test team use said tool to generate the checksum then as long as the source code is the same, then the generated checksum would also be the same (well I hope!). If we can build our own tool to generate a checksum that ignores the date time stamp, and possible other factors such as machine We have just discussed a possible solution here. The problem then is that the checksums are different the deployed application has not been approved. Will be different from the two outside regulators and what we build at our end. When we get approval to deploy, our test team here will then build the same version of the source code and the MSI package that is generated is what we are allowed to use for the deployment. When both parties approve and sign off the test process they will generate a checksum of the.
#Beyond compare crc vs. binary install#
More specifically a MSI package that they then install and test the application in their environment. The regulators will audit the code and do a build to generate an. I have been told that our source code is delivered to two outside regulators. I then get the checksums for each of the three files and what do you know - they are the same. Using PE explorer I can edited the date time So far as a test I have compiled a simple solution three times (same source code) (within an hour period) and saved three copies of the build with a different name. It also allows me to change the date time stamp and save the file. This little utility allows me to look at the PE of a compiled. Inserted into the PE header as well that cause the checksum to be different such as the machine name, but at the very least because the time is always changing and is used to generate the checksum, you will get a different result each time you build the same This is because the compiler puts the date and time in the PE header of the file. CRC checksum of our build needs to match that of the testers.Įach time you build your solution a new checksum will be generated. The testers check the systems using a CRC checksum. When the code has been approved we will need to do a post build which we will use to deploy. Side Note 2: The reason I need to do this is that our testers will get a copy of the source code and then do a build on their build Using this tool however is not practical as I have automated the build process. That is different each time that is causing the CRC checksum to be different each time. If I edit and modify this across my build files I can they get the same CRC checksum, so it looks like it is only the DateTime stamp This tool allows me to edit and save the DateTime stamp. Side Note 1: I have experimented with using a utility called PE Explorer. I have already done a lot of looking around have not been able to find anything that would help. Effectively can I make the DateTime stamp a constant, or are thereĪny settings that I can use to make sure the generated CRC checksum stays the same on each build that I do to the same code on the same build PC. I want to know if there is any way that I can solve this solution. Made sure that the assembly and file versions for the project stay the same.Ĭhecked other project properties for anything that effects the build actions. Uses the date time stamp as part of the build process and this is part of what causes the CRC checksum to be different each time. No changes to the solution / project properties makes a difference to the generated checksum at each build. At present a different CRC checksum is generated each and every time I build the project. Values each time (provided that no source code has changed). I have requirements to build the project and have the same CRC checksum I am working on a small C# WPF project in Visual Studio 2010. I am trying to get a practical solution to a problem that has been troubling me.
0 kommentar(er)
