Merge two different packages?
Hi there!
I have two different packages I want to merge into a single package.
If I install only one of the package does the application not work, so I need both anyways and do not want to distribute them as two packages.
Any ideas? I am running AdminStudio Pro 6 with value pack 1 (InstallShield 10.50)
/Jonas
I have two different packages I want to merge into a single package.
If I install only one of the package does the application not work, so I need both anyways and do not want to distribute them as two packages.
Any ideas? I am running AdminStudio Pro 6 with value pack 1 (InstallShield 10.50)
/Jonas
0 Comments
[ + ] Show comments
Answers (5)
Please log in to answer
Posted by:
Ilikebananas
18 years ago
Hi jonasm,
The only tool I know of is the msimerg.exe tool from the installer SDK. The tool allows you to merge two databases. You will get conflicts for example in the filetable (sequence collumn) and the registry table (registry collumn), and possibly more. You would need to find a solution for solving (or preventing) those conflicts. It might not be worth the effort.
I would probably nest the installations in a parent msi.
Ilikebananas
The only tool I know of is the msimerg.exe tool from the installer SDK. The tool allows you to merge two databases. You will get conflicts for example in the filetable (sequence collumn) and the registry table (registry collumn), and possibly more. You would need to find a solution for solving (or preventing) those conflicts. It might not be worth the effort.
I would probably nest the installations in a parent msi.
Ilikebananas
Posted by:
jonasm
18 years ago
Thanks for your reply!
It seems like a hard work to solve the conflicts, but your help is appreciated so you just got a +1 score!
/Jonas
It seems like a hard work to solve the conflicts, but your help is appreciated so you just got a +1 score!
/Jonas
Posted by:
revizor
18 years ago
jonasm,
whether you go this route or not is totally up to you, however I'd like to forewarn you: try not to combine packages that may be updated independently of each other. This way, if, say, application A gets updated every month, and application B stays static, you will be forced to do manual rework every month combining the static package with the changed one. I myself made this mistake a few times in the past...
whether you go this route or not is totally up to you, however I'd like to forewarn you: try not to combine packages that may be updated independently of each other. This way, if, say, application A gets updated every month, and application B stays static, you will be forced to do manual rework every month combining the static package with the changed one. I myself made this mistake a few times in the past...
Posted by:
Ilikebananas
18 years ago
Hi jonasm,
Thx for the rating. [:D]
I'm interested to know what solution(s) you used.
Ilikebananas
Thx for the rating. [:D]
I'm interested to know what solution(s) you used.
Ilikebananas
Posted by:
jonasm
18 years ago
I did it the hard way....
I opened the projects side by side and compared them files for files and registry for registry.
Then took all changes and added them manually to one of the projects.
/Jonas
I opened the projects side by side and compared them files for files and registry for registry.
Then took all changes and added them manually to one of the projects.
/Jonas
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.