Thanks Eusebiu!
Not sure the customer would be happy to have the password in the registry ( even encrypted) some of my customers are banks and tax organisations types who are very particular about security.
I'm was a little confused with your statement
"However, I'm afraid that if the service is still installed, you will not be allowed to replace its source files."
But I think I have worked it out.. because the upgrade first runs the uninstall which uses the uninstall settings of the original installer? .. .. hmmmm so it would only be for future upgrades beyond the next.
Maybe for in this installer I could check "if the the service exists and is NOT using LocalSystem account "Then I could provide a dialog warning the installer before the uninstall starts? That should be as simple as checking the service reg 'ObjectName' value? Can that be done without need custom actions. ( If Reg value exists, provide a dialog with text and a option to quit the install)
Oh and I tried copying the registry ( including security binaries) of the service and replacing it afterwards.. but the encryption is obviously a bit more complex than that!
Many thanks for your assistance.
FOLLOW US
Get the latest news in Application Packaging