The Key Path is how Windows Installer decides whether a component is already installed or not. If the key path is present, the installer doesn't do anything regarding the other resources in that component. For files it will also look at the version numbers, but for registry data it simply determines whether the key or value is present.
 
The same problems arise with adding a registry key/value to or removing one from a component as for adding and removing files. Best practice is to keep one component per resource.
 
 
--
Mike Dimmick


From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jeff MacDuff
Sent: 16 October 2006 18:28
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] What is KeyPath in refrence to Registry keys

I am trying to port some Wix from one file to another, in the V1 file … there are about 100 registry keys and each one with it’s individual component ID. I would like to consolidate all of the registry keys into 1 component.

 

However, I can only list one of the keys with a KeyPath=”yes” but I don’t know what keypath is or what it’s behavior is …. Looking at the help file the definition is:

 

Set this attribute to 'yes' to make this registry key the KeyPath of the parent component. Only one resource (registry, file, etc) can be the KeyPath of a component.

 

 

So currently I am trying to figure out what keypath refers too? I cant find any more info on it and why it would be “bad” if the value is no.

 

-Jeff

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Reply via email to