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 On Thu, Sep 25, 2014 at 11:02 AM, Rob Mensching <r...@firegiant.com> wrote: > I don't quite follow. > > 1. The KeyPath will be set however the non-WiX-based MSI creation tool sets > it. That's very much dependent on how the tool works. > > 2. If someone rewrites their installation package in WiX after using some > other tool then they will need to understand how the WiX toolset works. Right? > > Note: if that person used dark to decompile their non-WiX-based installation > package to get started in WiX then the KeyPath will be set explicitly > (because dark is pedantic like that). > > 3. If the migration from one MSI creation tool to a different MSI creation > tool changes the KeyPath then the "installation problems" that come with > changing the KeyPath of a Component will happen (if any). That has nothing to > do with the WiX toolset and everything to do with the migration (again, note > dark is pedantic and would do the right thing). > > _____________________________________________________________ > Short replies here. Complete answers over there: http://www.firegiant.com/ > > > > > -----Original Message----- > From: Phil Wilson [mailto:phildgwil...@gmail.com] > Sent: Thursday, September 25, 2014 10:31 AM > To: General discussion about the WiX toolset. > Subject: Re: [WiX-users] KeyPath by default? > > In other words, 1) someone builds an MSI with a non-WiX tool with a component > with no KeyPath that uses the MSI default of the containing directory and > then 2) builds an upgrade/patch/whatever MSI that similarly contains no > KeyPath definition and WiX chooses something else as the KeyPath and 3) they > get "installation problems"? Is that really the case? > --------------- > 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
