I've added some modify dialogs for my installation to allow for configuration changes within the installed component. I've noticed that this seems to require the original setup.exe file that contains my installation - a dialog is displayed showing the location where it was installed form originally. Is there anyway to avoid this? I'm not allowing a new component to be installed, just a simple input dialog for an already installed component, I then call a custom action to update the configuration and restart my service.
Please send us all the .AIPs (projects) to support at advancedinstaller dot com so we can investigate them. Also, can you please be more specific about what you are trying to achieve?
On the Modify, Repair, Remove dialog I select Modify and then proceed to put up a dialog to accept a new password that my service uses. This and the custom actions I use to set the password in the registry and restart my service all work great. The only problem I am having is that just before my dialog is displayed another file selection dialog is displayed looking for the original setup.exe that was used to install the product in the first place. Unlike the Remove which does not require the original setup.exe to complete. I realize that the installation puts the msi or enough of the Uninstall code on the machine somewhere to perform this Remove without requiring the original setup.exe. I also realize that usually the Modify implies some other component of the product may be selected to be installed which was not selected to be installed originally, so I can understand why it thinks it may need the original setup.exe file. In my case I only have 1 component and just wish to make a simple configuration change, is it possible to not require the original setup.exe file?
FOLLOW US
Get the latest news in Application Packaging