These sound like odd requirements to me. But that said, I'd use the action states of the components to figure this out. If you want to consider it from the first-installed product perspective, it will have to poke in and know at least one of the merge module's components (or perhaps create a configurable merge module that can use the consuming product's ProductCode).
Then refer to ?component-state and $component-action (or use MsiGetComponentState or another language's equivalent) to figure out whether the component was already installed, and/or is being uninstalled. You'll have to store something, perhaps in the registry, to indicate whether it was originally installed with the current product as the component states won't tell you that at uninstall. On Tue, Mar 9, 2010 at 03:45, Lisa Gracias <lisathelugubri...@gmail.com> wrote: > Thanks for that idea. It's much simpler than my approach. > There's an additional condition: The warning should be displayed only if the > product being removed is the one that first installed the merge module, > because only then will it have the shared components in its folders. How do > I find out which product installed it first? > > On Tue, Mar 9, 2010 at 2:28 PM, akash bhatia <911ak...@gmail.com> wrote: > >> Lisa, >> >> Best way is that u can write a custom action at uninstall which checks >> whether other two products r installed or not... set a property for tht >> >> if it found other products then it means tht shared files wont get deleted >> from target machine. and u can populate messagebox accordingly (as per the >> property value) at the end of the installation >> >> On Tue, Mar 9, 2010 at 2:11 PM, Lisa Gracias <lisathelugubri...@gmail.com >> >wrote: >> >> > I have 3 msi's which contain the same merge module. Apart from >> containing >> > components common to all 3 products, the merge module also writes an >> entry >> > to the HKLM registry hive. >> > >> > The first product to be installed, say Product A, will put the shared >> > components in its own folders, and the other two products will use the >> same >> > location for the shared components (even if their other components get >> > installed elsewhere). >> > >> > Now if the user uninstalls the Product A I want to display a warning >> that >> > certain shared components will not be removed, so that the user doesn't >> go >> > and remove those files on their own and break the functionality of the >> > other >> > two products. What's the best way to do this? >> > >> > I tried using a custom action sequenced after InstallFinalize to check if >> > the registry entry created by the merge module persists after uninstall >> > (since that would mean at least one other product that uses it exists on >> > the >> > system), but I don't know how to communicate the results of the check >> back >> > to Wix since I can't set a session property at that stage. >> > >> > >> ------------------------------------------------------------------------------ >> > Download Intel® Parallel Studio Eval >> > Try the new software tools for yourself. Speed compiling, find bugs >> > proactively, and fine-tune applications for parallel performance. >> > See why Intel Parallel Studio got high marks during beta. >> > http://p.sf.net/sfu/intel-sw-dev >> > _______________________________________________ >> > WiX-users mailing list >> > WiX-users@lists.sourceforge.net >> > https://lists.sourceforge.net/lists/listinfo/wix-users >> > >> >> >> >> -- >> Cheers, >> Akash >> >> ------------------------------------------------------------------------------ >> Download Intel® Parallel Studio Eval >> Try the new software tools for yourself. Speed compiling, find bugs >> proactively, and fine-tune applications for parallel performance. >> See why Intel Parallel Studio got high marks during beta. >> http://p.sf.net/sfu/intel-sw-dev >> _______________________________________________ >> WiX-users mailing list >> WiX-users@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/wix-users >> > ------------------------------------------------------------------------------ > Download Intel® Parallel Studio Eval > Try the new software tools for yourself. Speed compiling, find bugs > proactively, and fine-tune applications for parallel performance. > See why Intel Parallel Studio got high marks during beta. > http://p.sf.net/sfu/intel-sw-dev > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
