HKCU KEYS
how to move hkcu keys into new feature....??
as hkcu keys are there, my application goes for repair in test user so i want to delete it from registries...so need to move them into new feature....please suggest me
as hkcu keys are there, my application goes for repair in test user so i want to delete it from registries...so need to move them into new feature....please suggest me
0 Comments
[ + ] Show comments
Answers (3)
Please log in to answer
Posted by:
zipsantro
15 years ago
Its an ideal behaviour of Windows Installer. If installer has HKCU registry keys, it will go for a repair first time a user will launches in user mode. Moving them into a new feature may not suit your requirement.
Analyze the regitry keys and than take a decision to
1. Delete those from your installer. If these will be used by the application and will be created runtime.
2. Move them to HKLM if required. If it is required to launch for the first time.
Again there can be some discrepancies as I am not sure what those regitry keys does.
Jeeoo!
Santro
Analyze the regitry keys and than take a decision to
1. Delete those from your installer. If these will be used by the application and will be created runtime.
2. Move them to HKLM if required. If it is required to launch for the first time.
Again there can be some discrepancies as I am not sure what those regitry keys does.
Jeeoo!
Santro
Posted by:
raviray
15 years ago
Hi,
Read this article & use the same structure instructed,
http://itninja.com/question/distribution-message21
Thanks & Regards,
RRay
Read this article & use the same structure instructed,
http://itninja.com/question/distribution-message21
Thanks & Regards,
RRay
Posted by:
rbrucelee1978
15 years ago
Move all the HKCU keys to a CurrentUser component. That will make it easier for you to change the feature (however, moving HKCU keys can also generate some ICE errors namely ICE 69).
Having the default structure of the msi also has the same effect that creating an CurrentUser Feature and setting this as the parent feature to the Complete feature (provided that your CurrentUser component resides in the Complete Feature of course). Remember that when the windows installer service does its checks for self healing, it goes from the entry point feature then up to its parent feature and all the way UP to the top level parent feature?
Having the default structure of the msi also has the same effect that creating an CurrentUser Feature and setting this as the parent feature to the Complete feature (provided that your CurrentUser component resides in the Complete Feature of course). Remember that when the windows installer service does its checks for self healing, it goes from the entry point feature then up to its parent feature and all the way UP to the top level parent feature?
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.
