Can a MSM contain its dependecies?
Posted 25 September 2006 - 10:10
I have a problem regarding to msm deployment.
I have an msm (X.msm) that collects as a dependency Y.msm.
When I want to deploy my X.msm to a third party (that will use it in a MSI project)I also need to provide them the Y.msm seperatly. (In build time, on the third party MSI, the Y.msm needs to be on their machine).
I would like to know if there is a way that my X.msm can concretely contain Y.msm, so I won't need to supply the Y.msm to the third party.
Posted 25 September 2006 - 10:52
I thought of another idea:
Add the inner (Y.msm) merge module as one of X.msm installed files and somehow link some tables so that X.msm can use this file as the dependency it needs.
I have no clue if this is possible nor how to implement it...
Posted 25 September 2006 - 11:30
Of course you could create a Z.msm that contains the contents of both X.msm and Y.msm. But whenever a new version of X.msm or Y.msm is released you also need to update your Z.msm. When you do this be sure to keep the component GUIDs in sync. And if X.msm or Y.msm are coming from a third party check their license agreement to be sure you are allowed to extract the contents of their merge module and build a new module from it.
Posted 25 September 2006 - 13:44
M.msi merges X.msm and Y.msm ver 188.8.131.52.
Y.msm ver184.108.40.206 is a dependency of X.msm.
In other words, the MSI should merge different versions of the same msm (Y.msm)
Posted 25 September 2006 - 16:40