Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
>Resolution: Works For Me
Submitted By: TwoYrOldSaysWhy (twoyroldsayswhy)
>Assigned to: Derek (derekc)
Summary: DAO350 merge module does not register
When using the DAO350.msm from InstallSheild with a WIX
generated msi ... the dao350.dll is not registered when
the msi install completes successfully. I tested this
on a fresh XP install.
After some more digging I determined that none of the
registration entries were being put in the registry.
So I used Dark.exe to take the DAO350.msm and make a
dao350.wxs file out of it to see what it thought was in
there. It showed the normal stuff and did contain the
So then on a whim I built DAO350.msm using WIX and the
dao350.wxs that Dark generated and used that in the
MSI. After installation it appeared to register as
Hmmmmm .... there is more to this than meets the eye so
I wrote a bug up on it.
I don't get it and since I use so many InstallShield
merge modules I want to make sure something isn't wrong
I didn't see anything particularly wrong with that merge
module. If you continue to hit problems, please re-activate
the bug with the following files attached:
1. The original InstallShield msm causing problems.
2. The decompiled msm that is working.
3. The msi file with the original msm merged inside.
4. The msi file with the decompiled msm merged inside.
With all these files, we can then look at how the Registry
rows are merged to see if they are getting added properly.
WiX does not actually merge in modules - mergemod.dll does
it - so some of these issues may lie in that code, not WiX.