Cleaning up after installshield?

Hi!

I have recently converted (actually redid and improved) the install scripts for a few of my employer's applications which were done in installshield...

I have asked for this for many years and this year I was successful...

(In my spare time I am an open source developer so I am more friendly to open source solutions...)

It looks like if I wanted to cleanup after those installs (ensentially removing the uninstall keys in our case, doing more would have little value and be way more risky) it would require to find all the project GUID of those installshield scripts.

Problem is, to make it easy for the users of those applications to install them, the project GUID was changed at each release so it requires to find a loooooooot of project GUIDs.

The other way I could think of would be to sequentially search in the uninstall keys and find the ones which have the right "DisplayName" and "Publisher" and are initlialized like installshield initialized them.

Does anyone have anything to suggest? Something that would do something similar (or better!) to what I was suggesting and that I could do using NSIS?

Thank you very much for your help!

Nick

I don't know if the IS project files are easy to parse but if they are you could use !system to call a batch file that produces a .nsh you can include.

At run-time you can use EnumRegKey to list all the uninstall keys if you just want to detect by name.

Hi!

Thank you, that was a very good idea...

For the kind of script we had (installscript) this was apparently stored in the "ProductCode" in the Property "table" in the .ism file.

(At least that's where I found it...)

Unfortunately we did not keep each iteration of the scripts so I can't do that... )-;

Apparently if they had been the MSI style installshield script I would have had more options to get the Project GUID but these were made using installscript...

Very good idea though...

Thank you very much for your help and have a nice day and week-end!

Nick