Re: [WiX-users] Custom actions that are part of shared components

Stephen Walch wrote: > > (?ProductComponent = 2) AND ($ProductComponent = 3) > > > So why would (?ProductComponent = 2) yield true during the second > install? Could this be a timing issue? (In my sequence, the test is > After='InstallFinalize'.) > Timing might be an issue; I'm not sure i

Re: [WiX-users] Custom actions that are part of shared components

Bob Arnson wrote: > 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 C

Re: [WiX-users] Custom actions that are part of shared components

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

[WiX-users] Custom actions that are part of shared components

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