It looks like you hijacked an existing discussion thread, so I'll start a new one. ...
Yes, that's the way it works. That might not be the best way to remove files if you decide you want them back later. An alternative is to make the component transitive and use a property to make the actual file be present or absent, so if you later decide you want the file present just set the property value. It can be tricky to make that work in all cases, such as adding/removing features, repair, patches etc because you need to preserve the property value that is keeping the file present or absent. "The msdn doc says the following for component id in the column table. ComponentId --> If this column is null the installer does not register the component and the component cannot be removed or repaired by the installer. This might be intentionally done if the component is only needed during the installation, such as a custom action that cleans up temporary files or removes an old product. It may also be useful when copying data files to a user's computer that do not need to be registered. Does this mean in the full msi, components with null id will not be registered and if deleted then will not put the msi in repair? Which further indicates that at patch time we can call a custom action to delete these components , and this will not throw the msi in repair mode?" Phil Wilson ------------------------------------------------------------------------------ CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments & Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
