On Sat, Jul 31, 2010 at 10:41 AM, Stefan Küng <tortoisesvn_at_gmail.com> wrote:
> On 31.07.2010 01:43, George Dean wrote:
>>> If you upgrade from an earlier version of TortoiseSVN, you have to
>>> run a "repair install" right after the upgrade finishes. To do
>>> that, run the installer again and click on the "Repair
>>> Installation" button. I'm sorry about the inconvenience.
>>>
>>> If you want to know why the repair install is required, you can
>>> read about the technical details in my post:
>>> http://tortoisesvn.net/majorupgrade
>>
>> Perhaps you could add a custom action script earlier in the install
>> sequence, before the upgrade component list is resolved, to delete or
>> move the offending registry keys so that the keypath would no longer
>> be detected?
>
> Custom script don't run elevated at that stage. Only later the scripts
> can run elevated (elevation is necessary to remove HKLM registry
> entries). And at that later stage, the keypaths are already detected.
>
> Or do you know of a way to run scripts elevated at that early stage?
>
Hi Stefan,
There is easy solution: revert back to use separate component for
registry keys, but mark component to use parent folder as keypath. To
do this just add KeyPath='yes' to Component element and remove
KeyPath='yes' from RegistryKey element. I've tested it and it seems to
fix all problems described in your blogpost [1]. Did you considered
this solution?
[1] http://tortoisesvn.net/majorupgrade
--
Ivan Zhakov
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=757&dsMessageId=2646381
To unsubscribe from this discussion, e-mail: [dev-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2010-08-13 12:33:13 CEST