If you need to make sweeping changes that can't be fixed easily, its best to do a major upgrade and make that your new baseline.
-----Original Message----- From: Justin Hull [mailto:justin.h...@assetpoint.com] Sent: 25 September 2012 20:20 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Stuck on error PYRO0243 : Component hasa changedkeypath Update: Digging into the file I discovered/learned some things. 1 - IDs need to match between versions 2 - IDs are case sensitive 3 - Don't go changing the order of files I got the patch working, but in the end it showed me I need to re-write much of how we do things. That was a code snippet of a very large file. I do wish there was a "Fix All" option somewhere when faced with many*10 file differences. Thank you for the response. Justin Hull Sr. Developer Maximizing Asset Performance (864) 679-3513 Office -----Original Message----- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: Tuesday, September 25, 2012 10:25 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Stuck on error PYRO0243 : Component has a changedkeypath When a keypath attribute is not explicitly specified, the first file or registry key in the component is used, but this is not recommended. Do those code snippets show the whole of the components ? You can't change the contents of a component once it's been released. That's a violation of the component rules. You can add new components however. You can also change the contents of the files in the components since that doesn't affect the component definition. -----Original Message----- From: Justin Hull [mailto:justin.h...@assetpoint.com] Sent: 25 September 2012 14:52 To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] Stuck on error PYRO0243 : Component has a changedkeypath I tried searching Google and the archive, but I don't have a clear answer/understanding of why I am getting this error: error PYRO0243 : Component <> has a changed keypath I am trying to create a patch using the base version of a full install against a REL 2. According to some accounts, this occurs when the first resource of a component is changed, but in each case the file names are the same other than the source location. I've attached the two wxs files, but one spot where I get the error is shown below. Is there a way to override the message? In the WixEditor I did not see a keypath attribute on the component. <Rel 2 Code> <Directory Id="sqlTRIGGERSDIR" Name="TRIGGERS"> <Component Id="sqlTRIGGERS" DiskId="1" Guid="A89FC340-C3C3-4841-B3FC-C344B2A2582D"> <Condition>DBTYPE=1</Condition> <File Id="DEMPLOY.SQL_1" Name="DEMPLOY.SQL" Source="\\apshares\data2\Tw8-2\Pro00\DATABASE\mssql\TRIGGERS\DEMPLOY.SQL" /> <File Id="deqevent.sql" Name="deqevent.sql" Source="\\apshares\data2\Tw8-2\Pro00\DATABASE\mssql\TRIGGERS\deqevent.sql" /> <File Id="DEQHIER.SQL_1" Name="DEQHIER.SQL" Source="\\apshares\data2\Tw8-2\Pro00\DATABASE\mssql\TRIGGERS\DEQHIER.SQL" /> <File Id="DEQLUDVA.SQL_1" Name="DEQLUDVA.SQL" Source="\\apshares\data2\Tw8-2\Pro00\DATABASE\mssql\TRIGGERS\DEQLUDVA.SQL" /> <File Id="DEQMETER.SQL_1" Name="DEQMETER.SQL" Source="\\apshares\data2\Tw8-2\Pro00\DATABASE\mssql\TRIGGERS\DEQMETER.SQL" /> <File Id="DEQSEUDV.SQL_1" Name="DEQSEUDV.SQL" Source="\\apshares\data2\Tw8-2\Pro00\DATABASE\mssql\TRIGGERS\DEQSEUDV.SQL" /> <File Id="DEQSRIAL.SQL_1" Name="DEQSRIAL.SQL" Source="\\apshares\data2\Tw8-2\Pro00\DATABASE\mssql\TRIGGERS\DEQSRIAL.SQL" /> <File Id="DINITLOC.SQL_1" Name="DINITLOC.SQL" Source="\\apshares\data2\Tw8-2\Pro00\DATABASE\mssql\TRIGGERS\DINITLOC.SQL" /> <File Id="DINITSPC.SQL_1" Name="DINITSPC.SQL" Source="\\apshares\data2\Tw8-2\Pro00\DATABASE\mssql\TRIGGERS\DINITSPC.SQL" /> <File Id="dinlgmat.sql_1" Name="dinlgmat.sql" Source="\\apshares\data2\Tw8-2\Pro00\DATABASE\mssql\TRIGGERS\dinlgmat.sql" / <Base Code> <Directory Id="sqlTRIGGERSDIR" Name="TRIGGERS"> <Component Id="sqlTRIGGERS" DiskId="1" Guid="A89FC340-C3C3-4841-B3FC-C344B2A2582D"> <Condition>DBTYPE=1</Condition> <File Id="DEMPLOY.SQL" Name="DEMPLOY.SQL" Source="\\apshares\data2\Tw8-2\Pro00\DATABASE\mssql\TRIGGERS\DEMPLOY.SQL" /> <File Id="DEQCATMS.SQL" Name="DEQCATMS.SQL" Source="\\apshares\data2\Tw8-2\Pro00\DATABASE\mssql\TRIGGERS\DEQCATMS.SQL" /> <File Id="DEQEVENT.SQL" Name="deqevent.sql" Source="\\apshares\data2\Tw8-2\Pro00\DATABASE\mssql\TRIGGERS\deqevent.sql" /> <File Id="DEQEVUDV.SQL" Name="DEQEVUDV.SQL" Source="\\apshares\data2\Tw8-2\Pro00\DATABASE\mssql\TRIGGERS\DEQEVUDV.SQL" /> <File Id="DEQHIER.SQL" Name="DEQHIER.SQL" Source="\\apshares\data2\Tw8-2\Pro00\DATABASE\mssql\TRIGGERS\DEQHIER.SQL" /> <File Id="DEQLUDVA.SQL" Name="DEQLUDVA.SQL" Source="\\apshares\data2\Tw8-2\Pro00\DATABASE\mssql\TRIGGERS\DEQLUDVA.SQL" /> <File Id="DEQMETER.SQL" Name="DEQMETER.SQL" Source="\\apshares\data2\Tw8-2\Pro00\DATABASE\mssql\TRIGGERS\DEQMETER.SQL" /> <File Id="DEQSEUDV.SQL" Name="DEQSEUDV.SQL" Source="\\apshares\data2\Tw8-2\Pro00\DATABASE\mssql\TRIGGERS\DEQSEUDV.SQL" /> <File Id="DEQSRIAL.SQL" Name="DEQSRIAL.SQL" Source="\\apshares\data2\Tw8-2\Pro00\DATABASE\mssql\TRIGGERS\DEQSRIAL.SQL" /> <File Id="DINCTLTY.SQL" Name="DINCTLTY.SQL" Source="\\apshares\data2\Tw8-2\Pro00\DATABASE\mssql\TRIGGERS\DINCTLTY.SQL" /> Justin Hull Sr. Developer Maximizing Asset Performance 864-679-3513 office justin.h...@assetpoint.com http://www.assetpoint.com ----------------------------------------------------------------------------- - Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users SDL PLC confidential, all rights reserved. If you are not the intended recipient of this mail SDL requests and requires that you delete it without acting upon or copying any of its contents, and we further request that you advise us. SDL PLC is a public limited company registered in England and Wales. Registered number: 02675207. Registered address: Globe House, Clivemont Road, Maidenhead, Berkshire SL6 7DY, UK. ----------------------------------------------------------------------------- - Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ----------------------------------------------------------------------------- - Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
