I do know something of Components and key paths, that wasn't the issue. For a while there, in spite of the documentation, I thought this thread was saying WiX couldn't build an MSI file with a directory as a key path. --------------- Phil Wilson
On Fri, Sep 26, 2014 at 10:05 AM, Rob Mensching <r...@firegiant.com> wrote: > There is always a KeyPath for a Component: Directory, File, Registry or ODBC > (who uses that anymore?). Directory is the weakest KeyPath so if the others > are present WiX will default to the first one. This is all in the Component > KeyPath documentation: > > If this attribute's value is set to 'yes', then the Directory of this > Component is used as the KeyPath. To set a Registry value or File as the > KeyPath of a component, set the KeyPath attribute to 'yes' on one of those > child elements. If KeyPath is not set to 'yes' for the Component or for a > child Registry value or File, WiX will look at the child elements under the > Component in sequential order and try to automatically select one of them as > a key path. Allowing WiX to automatically select a key path can be dangerous > because adding or removing child elements under the Component can > inadvertantly cause the key path to change, which can lead to installation > problems. > > _____________________________________________________________ > Short replies here. Complete answers over there: http://www.firegiant.com/ > > > > -----Original Message----- > From: Phil Wilson [mailto:phildgwil...@gmail.com] > Sent: Friday, September 26, 2014 7:40 AM > To: General discussion about the WiX toolset. > Subject: Re: [WiX-users] KeyPath by default? > > Me too, not following. The question is a practical one. If someone built an > MSI containing a file in a Component with no key path (which is therefore > going to be the containing directory) , is there a way to build an equivalent > MSI with WiX? A KeyPath setting maybe? > > I'm not following because the gist of all this seems to be that WiX will > always set a key path, therefore I can't build that equivalent MSI, therefore > there are scenarios in which a WiX-built MSI may not correctly update a > non-WiX-built MSI because of key path differences. > --------------- > Phil Wilson > > > ------------------------------------------------------------------------------ > Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer > Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports > Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper > Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer > http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
