We want to have the ability to have installers that do "plugins" to our product.
So, for example, if our main product is already released, and we decide to create a plugin, we would create a separate installer that would do the installation of adding in this new component.
Is there a mechanism to tie this plugin to the main installer? We would want it to do things like:
1. If the main product is uninstalled, it would also be uninstalled automatically
2. An upgrade of the main product would leave the plugin intact
3. The plugin installer would continue to work with multiple version of the product (i.e. the plugin could be installed with version 1.0, or with version 2.0 where the product code has changed, but the upgrade code is the same)
So, for example, if our main product is already released, and we decide to create a plugin, we would create a separate installer that would do the installation of adding in this new component.
Is there a mechanism to tie this plugin to the main installer? We would want it to do things like:
1. If the main product is uninstalled, it would also be uninstalled automatically
2. An upgrade of the main product would leave the plugin intact
3. The plugin installer would continue to work with multiple version of the product (i.e. the plugin could be installed with version 1.0, or with version 2.0 where the product code has changed, but the upgrade code is the same)