View Full Version : Merge Modules: What is actually merged?

12-13-2004, 02:00 PM
When a merge module is merged with an MSI, what is actually merged? Seemingly properties are not, and components defined in the MSM cannot be enum'ed via the ISScript function FeatureFileEnum...so what exactly is merged?

I need to share information between my merge module and my main MSI, yet I can't figure out a solid way to do this. I have a very generic MSI installer that can change some of its basic behavior based on what MSM I plug in to it for a particular feature. I was trying to save msyelf some work but it seems that merge modules really don't merge very much.

What am I missing here?

12-13-2004, 06:39 PM
Most items in a merge module should be built into your MSI database; many primary keys from the MSM database are decorated with the merge module ID to avoid naming collisions (this is what's probably happening to your properties), but the data should be in there...