currently we have 2 msi files. Both are same. Only there is a difference in Moduledependency table. We need

guidance, so that we can decide to create seprate package or common package. Both msi installs same set of files.
0 Comments   [ + ] Show Comments


Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.


from the help files:
The ModuleDependency table keeps a list of other merge modules that are required for this merge module to operate properly. This table enables a merge or verification tool to ensure that the necessary merge modules are in fact included in the user's installer database.
So looks to me you have packages that only differ in the requirements for the included merge modules. What you want to do about it kinda depends on the nature of the difference. First question is: are the included merge modules the same for both packages? If so I'd say take the package with the most stringent requirements. Imo there won't be a need to create seperate packages in this case.

Answered 05/19/2010 by: pjgeutjens
Red Belt

Please log in to comment
We have 2 msi packages. MSI1 is packaged, and MSI2 is yet to package. MSI2 contains this extra line in moduledependency table. so can we just add this entry in msi1? As I told before everything else is same. In difference we do not find anything.
Answered 05/19/2010 by: Packagingteam
Orange Belt

Please log in to comment
is this you?


nice website
Answered 05/19/2010 by: clueless
Senior Yellow Belt

Please log in to comment

It must not be the same because on that website, they say they are "experts in Windows Installer technology". If that was the case, then PackagingTeam wouldn't be asking this question. LOL
Answered 05/19/2010 by: bearden3
Purple Belt

Please log in to comment
Answer this question or Comment on this question for clarity