Hi, Looking for your Windows Installer / WiX knowledge about SecureCustomProperties behaviour with merge modules:
Setup: - Wix 2.0.5325 - My WiX product FOO.msi merges in a merge module BAR.msm (using Feature/MergeRef and Directory/Merge). - The BAR.msm has a property BAR_SEARCH_RESULT in its SecureCustomProperties propery - (I am the author of the merge module, so I can fix it, but I can't use WiX fragments because the customers of the MSM aren't all using WiX.)4 Problem: - FOO.msi is not authored with the merged property "BAR_SEARCH_RESULT.ABC132...MSM_GUID" in its own SecureCustomProperties property - Therefore, when a repair is run on Vista with full UI, the merge module's BAR_SEARCH_RESULT property is not passed to the execute sequence (log "Ignoring disallowed property..."), which causes an error with a repair CA. Question: - Should a merge module's Secure Custom Properties be automatically put into the consuming MSI's own SecureCustomProperties automatically when it incorporates the merge module? (i.e. is Wix not doing something it should be doing? Much more likely that I don't know best practices here, but I had to ask.) - If not, how should the merge module get the result of its file search during Vista repair? Thanks, Daryn Mitchell ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
