I am attempting to create reusable Components that package up a few files,
etc., that are common to multiple installer packages. The windows
installer correctly uses reference counting to ensure that the elements of
my component get installed once and only once even (when I install multiple
MSIs that contain the component) and only remove the elements when the last
MSI is uninstalled. Great so far...
My problem occurs when I try to add CustomActions for registering and
deregistering my components. (If you must know, it involves making
STSADM.EXE calls to register a SharePoint "Feature".) I have not figured
out a way to associate my CustomActions with specific Components and they
therefore do not benefit from the above reference counting. If I install
two MSIs, the registration routine gets called twice. Worse, when I
uninstall just one of them, the component is unregistered.
I have tried packaging the components (and associated custom actions) as
both WIX Fragments and Merge Modules, but I get the problem either way. It
seems pretty clear that there is no way to simply invoke a CustomAction
from inside the Component tag, but I am hoping there us another way. Maybe
a Condition that can detect that my Component is going from reference count
0 to 1 (or 1 to 0)? Any help will be much appreciated!
-Steve
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
