Copying Uninstall.dat (from SUF70)

[csd214]

I have created my first VP project covering 3 versions of the current app. The power of g_OnFileProcessed is remarkable. So is the small size of Patch.exe. The patch works like a dream.

Still I have one problem. The newest version's uninstaller has a new action which I want to bring forward by the patch. I have learned that the .dat file's contents are "screens and actions, the uninstall control panel entry and the uninstall shortcut". I manually tried to copy the newest version's .dat file to overwrite the original file. When I start the uninstaller the screens are displayed without any theme (just grey dialogs). I have additionally copied the Uninstall Support Files and the uninstall engine itself (v7.0.1.0 and 7.0.2.0).

Whatever I do, the screens appear without any theme and the new action is not performed.

Is it possible to surmount this problem?

[Lorne]

Are you using the same theme? Is it named the same? If you check the theme settings in both projects, are they using the same images?

[Brett]

Look at what the UninstallData.AddItem action does in SUF70 when you add a UNINDATA_SCRIPTS item. Look at the XML file created. Then just make your patch use the XML actions to add the same entry to the uninstall.xml file. Any extra scripts you add will be executed during the uninstall. Also read page 236 of the Setup Factory User's Guide.

[csd214]

Yes, the same theme and the same name (Bricks and Paper with my own logo file as top banner)

I have used UninstallData.AddItem() at several occasions but never UNINDATA_SCRIPTS. Is there any available example with "additional scripts that should run during the uninstallation"?

Can I understand your answers like "it is not necessary to change the original .dat file". "All can be done with modification of the .xml file"?

[Brett]

Originally Posted by csd214

Can I understand your answers like "it is not necessary to change the original .dat file". "All can be done with modification of the .xml file"?

Right. In fact, I would strongly reccomend that you never try to install a new .dat file. It is much better (and by design) to use the uninstall.xml file to do these things.

[csd214]

Thanks for clarifying the .dat issue; I'm glad it is like that.

OK, I'm one step further on. I tested UninstallData.AddItem(UNINDATA_SCRIPTS, tNewScript) and the uninstall.xml contained:

<ExtraScript>
<ID>Added Action</ID>
<Timing>0</Timing>
<Script>
RGlhbG9nLk1lc3NhZ2UoIjEiLCAiSGVsbG8gV29ybGQiKQ==
</Script>
</ExtraScript>

It worked as expected.

Could you please comment the Script tag?

Do I have to create all new command lines in SUF70 to find the encrypted script tag and at last use XML commands in VP20 to add the new items?

[Brett]

No, the Script is Base64 encoded both to obscure readability and to protect the integrity of the script. When you write to that XML key you will have to use Crypto.Base64EncodeToString to make the script into base 64 text.

[csd214]

Thanks again; I also liked the last answer. (I found it better to ask in preference to try out the hard way; although I'm thereby is telling the readers that I don't understand everything…).

I already have a SUF70 test program with Crypto actions. I decrypted the script tag and got Dialog.Message("1", "Hello World"); but that was obvious (?).

This shouldn't be as difficult as it could look like. I'm looking forward to try the new actions in VP20.

[csd214]

Thanks to Brett's guidance; short but efficient; I have achieved SUCCESS. This is really a *great* bonus to SUF70 users.

I am new to XML files; I have to learn more. The experienced user is probably smiling when reading my published code for modifying the %ProductVer% tag; but it works!

I used SUF70 to test the uninstall.xml format when you have more than one additional 'ExtraScipts'. It was not a surprise, but the correct format seems to be:

...
</SessionVars>
<UninstallScripts>
<ExtraScript>
<ID>Script #1</ID>
<Timing>6</Timing>
<Script>The encoded script</Script>
</ExtraScript>
<ExtraScript>
<ID> Script #2</ID>
<Timing>0</Timing>
<Script>The encoded script</Script>
</ExtraScript>
<ExtraScript>
<ID> Script #3</ID>
<Timing>7</Timing>
<Script>The encoded script</Script>
</ExtraScript>
</UninstallScripts>
</SUF70UninstallData>

It's utterly incomprehensible, but
* The creation of the patch.exe took "no time"
* I used several hours to create my additional uninstall script (due to several reasons, my lacking XML knowledge, the cumbersome test procedure and more).

I think this should be taken into consideration when choosing the patch option or the full setup option. Indeed, it feels good to be able to use this advanced possibility in VP20. The timing option is awesome.

Good luck to everybody, and to IR with the complete solution "Promote it! Install it! Patch it! Update it!"