I have an executable that can be installed as a Windows service.
It supports install/uninstall from the command-line.
I can run "myservice.exe /instance=0 /i" to install the "MyService0" service.
I can then run "myservice.exe /instance=1 /i" to install the "MyService1" service.
Likewise, "myservice.exe /instance=1 /u" will uninstall the "MyService1" service.
How can I configure an installer to handle this with the following assumptions?
The service executables are contained in a single feature.
Single copy of myservice.exe on the target computer.
Instance 0 is always installed.
User can choose to install (or not) instances 1-9.
User could choose the relevant instances by enabling a sub-feature for each instance, or with a custom dialog with a property for each instance (whatever will work)
When installer is run at a later time to modify or uninstall, the UI should reflect which instances were previously installed.
When installer is run at a later time to modify, the user should be able to install/uninstall instances.
The service names/display names/descriptions for each instance are well-known and could be hardcoded in the installer if necessary.
FOLLOW US
Get the latest news in Application Packaging