Component has a changed keyPath error

3 messages Options
Embed this post
Permalink
Scharp, Craig

Component has a changed keyPath error

Reply Threaded More More options
Print post
Permalink
Hi wix users,

 

I'm trying to create a small update patch to replace some files on the
website and getting this error running Pyro:

 

error PYRO0243 : Component 'somecomponentname' has a changed keypath.
Patches cannot change the keypath of a component.

 

I'm not using keypath in my wxs file and the components that are getting
this error are in same directory between the two wxs files (rtm and
update).  I'm researching this and not having much luck.  Has anyone run
into this?  Should I be using the keyPath attribute in my installs?

 

Thanks in advance for any thoughts or suggestions!

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
WiX-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/wix-users
Blair-2

Re: Component has a changed keyPath error

Reply Threaded More More options
Print post
Permalink
If keypaths are not explicitly declared they are implicitly set based on a
simple set of rules. However, authoring changes between one build and
another can cause the rules to designate a different resource as the
implicit keypath.

To avoid this, you should set explicit keypaths. Normally, the principle
file in a component should be its keypath. Lacking any files, the principle
registry value/key should be the keypath. Other possible keypaths include
ODBCDataSources and the component's own directory (set by using the KeyPath
attribute in the Component element).

-----Original Message-----
From: Scharp, Craig [mailto:[hidden email]]
Sent: Friday, November 06, 2009 8:58 AM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] Component has a changed keyPath error

Hi wix users,

 

I'm trying to create a small update patch to replace some files on the
website and getting this error running Pyro:

 

error PYRO0243 : Component 'somecomponentname' has a changed keypath.
Patches cannot change the keypath of a component.

 

I'm not using keypath in my wxs file and the components that are getting
this error are in same directory between the two wxs files (rtm and
update).  I'm researching this and not having much luck.  Has anyone run
into this?  Should I be using the keyPath attribute in my installs?

 

Thanks in advance for any thoughts or suggestions!

----------------------------------------------------------------------------
--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus
on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
WiX-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/wix-users


------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
WiX-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/wix-users
Rob Mensching-7

Re: Component has a changed keyPath error

Reply Threaded More More options
Print post
Permalink
FYI, if you run with -pedantic warnings, the WiX toolset will spit out
warnings about this sort of thing.

On Fri, Nov 6, 2009 at 6:54 PM, Blair <[hidden email]> wrote:

> If keypaths are not explicitly declared they are implicitly set based on a
> simple set of rules. However, authoring changes between one build and
> another can cause the rules to designate a different resource as the
> implicit keypath.
>
> To avoid this, you should set explicit keypaths. Normally, the principle
> file in a component should be its keypath. Lacking any files, the principle
> registry value/key should be the keypath. Other possible keypaths include
> ODBCDataSources and the component's own directory (set by using the KeyPath
> attribute in the Component element).
>
> -----Original Message-----
> From: Scharp, Craig [mailto:[hidden email]]
> Sent: Friday, November 06, 2009 8:58 AM
> To: General discussion for Windows Installer XML toolset.
> Subject: [WiX-users] Component has a changed keyPath error
>
> Hi wix users,
>
>
>
> I'm trying to create a small update patch to replace some files on the
> website and getting this error running Pyro:
>
>
>
> error PYRO0243 : Component 'somecomponentname' has a changed keypath.
> Patches cannot change the keypath of a component.
>
>
>
> I'm not using keypath in my wxs file and the components that are getting
> this error are in same directory between the two wxs files (rtm and
> update).  I'm researching this and not having much luck.  Has anyone run
> into this?  Should I be using the keyPath attribute in my installs?
>
>
>
> Thanks in advance for any thoughts or suggestions!
>
>
> ----------------------------------------------------------------------------
> --
> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
> trial. Simplify your report design, integration and deployment - and focus
> on
> what you do best, core application coding. Discover what's new with
> Crystal Reports now.  http://p.sf.net/sfu/bobj-july
> _______________________________________________
> WiX-users mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
>
>
> ------------------------------------------------------------------------------
> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
> trial. Simplify your report design, integration and deployment - and focus
> on
> what you do best, core application coding. Discover what's new with
> Crystal Reports now.  http://p.sf.net/sfu/bobj-july
> _______________________________________________
> WiX-users mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
>


--
virtually, Rob Mensching - http://RobMensching.com LLC
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
WiX-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/wix-users