I have an MSI installation created using InstallShield 2009 that installs the .NET service by setting the ".NET Installer Class" to "Yes" on the component that contains the exe service. This basic installation containing files and exe installs OK. I created a small MSP update that updates the service exe file in the original installation. When I start MSP on a system containing a basic installation, I get error 1001 because it is trying to reinstall the service during the installation of the MSP update.
A Flexera spokesperson’s response to this problem is that if you need to update the .NET executable, set the .NET Installer Class component to No and create your own custom actions. Flexera also admitted that they are not documenting anywhere that if you set the ".NET Installer Class" to "Yes," you will not be able to create MSP updates for your installation. It is impossible to go back and change the basic installation from the moment of its release, and an update must be created against it. I myself came up with a workaround by including a special action in the MSP update that deletes the service during the MSP installation. This installs a small MSP update, but this workaround does not work to remove MSP from ARP.
I need to know how best to solve this problem in future installations. How to install the .NET service so that you can easily update the service later with a small MSP update?
Linda source
share