We do this by using sequences of commands added to an 'Edit.aic' file that is then processed, so we end up with lists like:
Code: Select all
AddFile APPDIR\WO "C:\agent1\_support\bin\XX\wo\XX.Presentation.Controls.resources.dll"
AddFile APPDIR\WO "C:\agent1\_support\bin\XX\wo\XX.resources.dll"
SetVersion 1.0.858.0
SetPackageName Setup.1.0.858.0.msi
Save
1) Some files types added, such as databases, documents, etc get assigned to a seemingly random component. As a result we end up with a component with 10 files linked to it. While this is not a problem as yet, it may become so.
2) Some files need to form part of features. Typically these are assemblies and Advanced installer seems to create individual components for each file. However, these components are all part of the default installation. We need them to be part of a (predefined) optional feature so that the user can choose to install them or not.
I cannot see any way that we can specify the feature or component that files are added to (only the destination folder, e.g. APPDIR\WO). I also cannot see any way of moving or reassigning the components once created.
Is there a way around this? If not, then it limits our dynamic project updating to changes only to the base installation - not to any features.
FOLLOW US
Get the latest news in Application Packaging