Hello All,

Just wanted to say hello and start with a problem for my first post.

I'm trying to package UltraEdit and set it up to be used as the default handler for all it's associated file extensions; my problem is that Wise creates an extra key called "HKCR\.txt\UltraEdit.txt" (and also creates a new key under each file extension key that is being configured) when installing. This key doesn't need to be there for the purpose of being the default handler and when it is there will cause the system to generate an error about "the configuration registry key is invalid" when I select "New\Text Document" from the contextual menu. If I delete this new key that has been added, UltraEdit is still the default application for the filetype and launches fine.

I set a custom action to delete the key on install but when a repair is performed under a new user profile (HKCU info) the key gets placed back under "HKCR\.txt". Is there any way to get Wise to not add this key? Is there a reason Wise creates a key when setting up file assocations? I can't find anything relating to it in the Tables and presume it's a feature of Wise for some reason.

Any help would be greatly appreciated,
Regards,
Corin
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
> I set a custom action to delete the key on install but when a repair is performed under a new user profile (HKCU info) the key gets placed back
> under "HKCR\.txt".

Well.. this may becuase the HKCR keys and the HKCU keys are in the same component.
Generally it is a good practise to place ONLY HKCU keys under a single component.

I too repackaged ultraedit some time back, but didn't face this problem.. BTW: I also use wise..
Answered 04/24/2006 by: nvdpraveen
Orange Belt

Please log in to comment
Answer this question or Comment on this question for clarity