Eusebiu wrote:Hi,
In order to achieve this, you can go in the "Prerequisites" page of your main installer's project and add the plugin installer as a "post-install" prerequisite. For more details about adding a prerequisite you can take a look on the
Add Prerequisites tutorial.
If you want that plugin to be always installed, you can go in the "Install Conditions" tab and check the "Always install this prerequisite" option. You can also set the appropriate command lines in the "Setup Files" tab.
Let us know if this helped, otherwise give us more details about your scenario.
Best regards,
Eusebiu
My plugins are sold as separate products, so they can't really be installed as pre-reqs.
Here are the details about my setup:
1) The main product installs a "default" non-functional plugin. Call it PluginFile.dll. It is always version 1.0
2) When a user purchases the plugin, they get an MSI that installs *only* PluginFile.dll version 2.0
3) If I release an update of the main product, it overwrites PluginFile.dll with the original version 1.0
4) If the user were to manually re-run the installer for #2, it would prompt the user to "perform a repair" in which case the PluginFile.dll will be updated to version 2.0
What I'd like to have happen:
I want my main product to run the MSI installer for #2 and silently repair PluginFile.dll to bring it back to version 2.0. To do this, I'd like to know what command line parameters to pass to it to get it to do this.
FOLLOW US
Get the latest news in Application Packaging