Hello,
we are recently testing InstallAware Studio 9 because we want to replace our Visual Studio generated installation.
Our idea was that we pack the plugins, extensions etc. in mergemodules and add these modules as different features to the InstallAware generated installation. Is this possible?
We want to do this because the different developers of the plugins can create their installation in Visual Studio as mergemodule and the developer who generates the main setup only needs to add these modules without the need to know what special install settings the plugin needs.
Thank you very much,
Ciao,
Sven
Add mergemodule per feature
Thank you for your reply. We do not need to build mergemodules with IA as Visual Studio is able to do so. We want to consume them but on a per feature base. As an example:
We have an Application (Feature A), the base program. We defined in Visual Studio a Mergemodule that keeps the registration information, the files to copy, etc. Then we have a Plugin (Feature A.1) for this base application. The installation of this module is defined using another Visual Studio created Mergemodule.
What we want is that when Feature A.1 is selected the merge module for the plugin should be installed. When it is not selected it should not be installed.
At the moment it's only possible to install a mergemodul not to defined when - is this right?
We have an Application (Feature A), the base program. We defined in Visual Studio a Mergemodule that keeps the registration information, the files to copy, etc. Then we have a Plugin (Feature A.1) for this base application. The installation of this module is defined using another Visual Studio created Mergemodule.
What we want is that when Feature A.1 is selected the merge module for the plugin should be installed. When it is not selected it should not be installed.
At the moment it's only possible to install a mergemodul not to defined when - is this right?

