|
#1
|
|||
|
|||
|
Question about patch.exe
I should be careful (I have only read the User Guide), but…
I created a patch for v2004.1 and 2004.2. The installed version is 2005.0 (newer). VP tells that I already have the newest version (2004.2). I modified the On Startup script to assign the correct value to g_InstalledVersion. Patch.exe told me This program will patch <%ProductName%> on your system from version 2005.0 to version 2004.2. Doesn't VP take care of the faulty situation when the user runs an outdated patch? [v2.0 RC1] |
|
#2
|
||||
|
||||
|
Are your versions in the right order? They should be listed with the oldest in the furthest left tab to the newest at the furthest right.
Also, during the build process, are you including the new version in the build? Is it checked during the publish wizard? |
|
#3
|
|||
|
|||
|
I haven't added v2005.0 to the project. I just simulated (by intention):
* The user has installed the latest version through an ordinary setup * Then he "finds" Patch.exe (previously downloaded) What I wanted was that Patch.exe told the user; "You already have a newer version on your system." ". As far as I understand VP does not read the version no of the installed version; to VP the "newest version" is the rightmost tab? (I have problems with some users, they pay their yearly bill (to get access to the update), but they forget to run the update. They continue to use their old version; they don't realize what they are doing before "the auditor is coming..". (Tax regulations change from year to year.) Then my support phone is chiming. CRISIS! -- Yes, I know. True Update! It's coming…). |
|
#4
|
||||
|
||||
|
Well, in real usage the user would run the old patch and it would tell him that it could not find your software on the system because the patch would not recognize the latest version. I guess in order to answer your question fully I will need to know what script you are using to do this testing.
|
|
#5
|
|||
|
|||
|
Quote:
Maybe there is something wrong with my key files; I really have to check (I tried to build (in a hurry) the folder structure when I learned the VP idea. If the proper answer is "not recognized", I'm happy with the solution. (I should be more careful before posting.) |
|
#6
|
|||
|
|||
|
My version tabs were completely out of order, sorry.
I deleted the project and started from scratch; it doesn't take a long time. Patched from 2004.0 to 2004.1; success. Installed v2005.0, started the patch (still including only v2004.0-1). Result: "Software not found." Excellent! I'm reassured. (And I can add some scripted message, "You have a newer version", if I want.) The complete patch.exe (two versions) is only 33% of my main exe and 19% of the full setup. I'm impressed. (I have owned VP10 for years, but never used it. "I don't need this one." I was wrong (once again). I have some system files that never should overwrite an existing file. I wondered, where should I tell VP20? As I understand the logic in VP20, I don't have to worry. Thank you. |
«
Previous Thread
|
Next Thread
»
| Thread Tools | |
| Display Modes | |
|
|
All times are GMT -6. The time now is 09:51 PM.






Linear Mode
