In the main script, it looks as though the variable UNINSTALLLINK is born fully formed!
It seems to me that if I knew the {GUID} part I could use that to write installedupdates.dat to the folder for the updated version, where it would be found when that version's 'update' shortcut checks for updates. Does it exist as another variable?
John
How can I get the {GUID} folder name of UNINSTALLLINK?
-
- Site Admin
- Posts: 5361
- Joined: Sun Aug 22, 2010 4:28 am
Re: How can I get the {GUID} folder name of UNINSTALLLINK?
Dear John,
The "UNINSTALLLINK " it is filled by the IA engine and its Initial value set to the full path of the uninstallation setup program.
Please have a look at the UPDATE script ... all the update process is handled there.
Regards
The "UNINSTALLLINK " it is filled by the IA engine and its Initial value set to the full path of the uninstallation setup program.
Please have a look at the UPDATE script ... all the update process is handled there.
Regards
Francesco Toscano
InstallAware Software
White Papers (HowTos) - http://www.installaware.com/publication ... papers.htm
Publications - http://www.installaware.com/publications-review.htm
InstallAware Help -F1 anywhere in the InstallAware IDE
InstallAware Software
White Papers (HowTos) - http://www.installaware.com/publication ... papers.htm
Publications - http://www.installaware.com/publications-review.htm
InstallAware Help -F1 anywhere in the InstallAware IDE
Re: How can I get the {GUID} folder name of UNINSTALLLINK?
Dear Francesco
I have been studying the 'updates' script and putting in lots of debug Message Boxes to see values. I was hoping that there might be a variable that holds the {GUID} folder name part of UNINSTALLLINK. As far as I can see that is the only variable that defines the folder in 'Program Data' where the new installer in held.
As my other current entry points out, the value for both EXEDIR and ENGINECACHE at the point of updating the log, is the {GUID} of the version that has just been replaced. Which is why 'installedupdates.dat' ends up in the folder for the old version, and not the current one. That's just to get frustration off my chest - I will continue this on that entry
John
I have been studying the 'updates' script and putting in lots of debug Message Boxes to see values. I was hoping that there might be a variable that holds the {GUID} folder name part of UNINSTALLLINK. As far as I can see that is the only variable that defines the folder in 'Program Data' where the new installer in held.
As my other current entry points out, the value for both EXEDIR and ENGINECACHE at the point of updating the log, is the {GUID} of the version that has just been replaced. Which is why 'installedupdates.dat' ends up in the folder for the old version, and not the current one. That's just to get frustration off my chest - I will continue this on that entry
John
Who is online
Users browsing this forum: Google [Bot] and 92 guests