see the developers maintain a public version history log and increment the minor version of the executable to indicate any changes like a bug fix or rebuild with a different SDK, changing the program ,

fixing bugs etc so that we can clearly see the executable has been changed but not changing the version number breeds suspicion, a lack of change log gives us no idea if the new build addresses any bug we masy have exprienced in the earlier build... how can you offer support when every version 3 you have released is version 3.0.0, you have to get the customer to fing the executable and determine the exact signing time and date to determine what build they are using when normal versioning would let the customer know that their build is obsolete and they should update to the current build to fix thier problem!