Disclaimer: As you probably know, it is a bad practice to register files this way during installation. The preferred way is to author the actual registry values that get written during registration.
Ignoring the disclaimer, you shouldn't rely on using the value of the ADDLOCAL property. Instead, use the feature or component state to condition your custom actions. Using component state is the preferred way so your conditions should be: <InstallExecuteSequence> <Custom Action='Register' After='InstallFiles'>$StaticBinaries = 3</Custom> <Custom Action='Unregister' Before='RemoveFiles'>$StaticBinaries = 2</Custom> </InstallExecuteSequence> See this page for more details (I recommend bookmarking it): http://msdn.microsoft.com/en-us/library/windows/desktop/aa368012%28v=vs.85%29.aspx http://msdn.microsoft.com/en-us/library/windows/desktop/aa368012%28v=vs.85%29.aspx -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/CustomAction-not-running-tp7263897p7265626.html Sent from the wix-users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Keep Your Developer Skills Current with LearnDevNow! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-d2d _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
