carlldev wrote: > It would have been better if I could tell what mode the installer is in > whether it be install, uninstall or repair so that this code isn't tied to a > specific feature or component.
It's possible to mix and match actions at a feature and component level so there isn't a package-wide installation mode. > the custom action I now check the install status of the component that each > file belongs to to check whether it should import or remove. That way we can > implement a change mode as well and each component will be handled > individually > And that's exactly how the WiX custom actions work: Everything's driven by the component action state. -- sig://boB http://joyofsetup.com/ ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. 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
