we need help authoring our installers for multiple projects. The scenario is the following:
We have two products:
- Product A
- Product B
- Module A
- Module B
Dependencies are:
- Product A: Module A
- Product B: Module A, Module B
- Product A uses Version 1.1.2 of Module A
- Product B uses Version 1.1.3 of Module A
Product A and Product B are Installer Packages and Module A and Module B are Merge Modules. If we update files in Module A which do NOT afflict Product A BUT Product B, we only build a new version of Product B.
Now our big problem:
If we first install Product B with Module A in Version 1.1.3 and after that Product A with Module A in Version 1.1.2, all files from Module A which haven't a file version are overwritten and get incompatible to Product B. All DLLs with a file version are kept because they have a higher version (1.1.3 compared to 1.1.2).
Advanded Installer has the feature to set a file version for arbitrary files. But after some testing it does not seem to work.
The question is: What structure is the best for our scenario?
FOLLOW US
Get the latest news in Application Packaging