Stephen Walch wrote: > > 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. >
This is why WiX and MSI and other folks recommend folks avoid custom actions if at all possible. Properly accounting for when CAs have to be run and can't be run is hard. You might be able to get away with better conditions on your custom actions. Take a look at "Examples of Conditional Statement Syntax" in the MSI SDK for examples. But we should keep this thread going on how WiX might support SharePoint. Maybe there's a way we can tie component state more directly and solve this problem for everyone. -- sig://boB http://bobs.org ------------------------------------------------------------------------- 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
