/build/static/layout/Breadcrumb_cap_w.png

Inputs needed

Hi,

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

Answers (4)

Posted by: pjgeutjens 11 years ago
Red Belt
0
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.

PJ
Posted by: Packagingteam 11 years ago
Orange Belt
0
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.
Posted by: clueless 11 years ago
Senior Yellow Belt
0
is this you?

http://www.packagingteam.com/

nice website
Posted by: bearden3 11 years ago
Purple Belt
0
clueless,

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
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ