I sometimes create multiple builds under the same version number, i.e. 1.0.2 may have several builds (with or without minor changes - I know I shouldn't but nevertheless...)
Currently my pacth lets users locate the desired directory, then uses this code:
Am I correct in assuming that I can "force" and update by doing the following?
1) Remove the first two lines above (and eliminate the if statement accordingly)
2) Choose "force install" on the file properties for my exe file.
Will that replace the previous exe with the new one?
Is there a way to verify the exe and version, but ignore the MD5?
(That way I could be sure they are overwriting the proper version of the exe without worrying about the specific build!)
Thanks....
Currently my pacth lets users locate the desired directory, then uses this code:
Code:
g_InstalledVersion = VisualPatch.CheckFolderVersion("%AppFolder%", SelectedFolder); if g_InstalledVersion then SessionVar.Set("%AppFolder%", SelectedFolder); etc....
1) Remove the first two lines above (and eliminate the if statement accordingly)
2) Choose "force install" on the file properties for my exe file.
Will that replace the previous exe with the new one?
Is there a way to verify the exe and version, but ignore the MD5?
(That way I could be sure they are overwriting the proper version of the exe without worrying about the specific build!)
Thanks....
Comment