run a batch file during uninstallation

[reynen]

Hello,

In my MSI installer I am able to run a Custom Action/Run Executable during the installation process (it runs a batch file that I install as part of the MSI)

During the uninstllation process, I would like to run a second batch that was installed with the MSI before it starts removing files. Ideally before it checks to see if the installed EXE is running.

how can I configure the custom action to do this?

Thanks

[Ulrich]

I assume that you set o condition on the first batch file, "Not Installed", so it does not get executed again during the removal. In a similar manner, you need to set a condition, "Installed" on the second batch file, so it is not executed during the installation.
As for the application not being active, you can use a short Lua script, run System.EnumerateProcesses(), and check if your application is inactive before proceeding, or show a message to close it before attempting again.
If I misunderstood your question, please clarify.

Ulrich

[reynen]

Thank you for your reply. I have made a few attempts at using conditions as you described but am not having any luck.

Just to be clear, my 'Install Service' custom action is working perfectly. It runs only during the installation process and at the appropriate time.

The 'Uninstall Service' custom action is either running during the installation process (which I do not want) or not at all.

If my uninstall custom action was running at the appropriate time during the uninstall process, it will stop the service and should not trigger the "The following applications should be closed ..." dialog box I am seeing.

I am attaching an RTF document with some screen shots that show how I have the custom actions configured. If you see the problems on these screens please let me know how to change. I can send the .msifact file if that would be helpful.

There is a good chance I am missing something very obvious. I have never used the custom actions before

Thanks

[Ulrich]

Yes, there is a mistake. Instead of using a Custom Action for the service, it is better to use the specific action for this kind of operation. Custom Actions should only be used for stuff without an already dedicated action available. Please remove your Custom Actions, and use this instead:



Now set up a "Create Service" action, and a "Control Service" action. This will install the service on the target system, and start it (if so desired). Windows Installer will handle the reverse action during the uninstallation, stopping the service (if you enabled this option), and removing it from the computer (with another option), as shown below.



Ulrich

[reynen]

I have tried using the 'Create Service' option. The attached document shows how I configured the "create service". Also in the document is the error message I get when I try to start the service (either if I try to start it by hand or using the "Control Service" feature.


This is how I am able to successfully install the service manually

%WinDir%\Microsoft.NET\Framework\v4.0.30319\Instal lUtil.exe dc123CEStarterSvc.exe

what am I doing wrong?

Thanks

[Ulrich]

Are you attempting to control the service name (dc123CEStaterSvc)? The error message looks as you are attempting to start the display name, but I could be wrong. Instead of posting screenshots inserted into docs, please attach the project file, or open a support ticket in the customer portal, attaching the file there, so I can have a proper look.

Ulrich

[reynen]

OK. I just created a ticket and included the files

[Ulrich]

I have revised the project and gave you some pointers. I hope it helps.

Ulrich