Re: Re: Painfull TortoiseSVN reinstall

On Mon, Nov 19, 2012 at 10:19 PM, Tomasz Trejderowski
<tomasz_at_trejderowski.pl> wrote:
>> Is any of those a shell extension? I don't mean whether it uses the
>> shell but whether it's an actual shell extension. And also not just a
>> context menu handler but a copy-hook-handler, icon overlay handler?
>
> Yes! As for copy-hook -- 7-Zip or WinRAR. As for icon overlay --. It's Dropbox. I have never had even 10% of troubles TSVN causes, when I was updating Dropbox. Actually, it is one of the most silent, and not obtrusive installers / updaters I've ever met. I can say same about 7-Zip or WinRAR.

Dropbox does NOT update its overlay handler dll but keeps that at a
constant version so it won't have to update.
So do other apps.
TSVN updates it's extension handler dll every time because it has to
(for reasons I'm not going into here).

>> We did force a full reboot before, but users complained that it's not
>> really necessary and they prefer having to shut down the affected
>> processes instead.
>
> After getting all the responses here I'm ready to admin, that I was wrong and took off to early conclusions about shell restart process itself.
>
> But the whole TSVN updating idea wouldn't be so trouble to me, if TSVN could restart after that anything it shut down.

http://msdn.microsoft.com/en-us/library/windows/desktop/aa372466%28v=vs.85%29.aspx

>
> For this purpose I can't understand, why you don't use simple ShellExecute plus remembered list of apps and do the restart manually? Instead, you're talking about some restarting functionality, that should be embedded into applications being restarted. Is this another problem that comes out from MSI installer? Maybe considering some other solutions (InstallShield, Nullsoft) would be an option to solve this?

InstallShield uses msi as well.

Seriously? ShellExecute?
Please think long and hard before you go there further...

> No, I'm not getting this at all. If others shell extensions (like mentioned one: Dropbox, packers plus many more) can update DLLs and themselves without making such mess, then it lead us to the conclusion, that not shell update itself is a problem, but MSI installer. Why then don't get rid of them and try to use something else? Something that other shell extensions are using to carry their system-level updates?

As I said above: they don't update the extension dlls. And when they
do, they show the very same as TSVN or require a reboot.
Or don't require a reboot and hope for the best. I've seen all.

Now, please:
Either learn how installers work and why they work like this, or just
accept that you have to restart after upgrading TSVN. Either way, I
won't comment on this anymore.

Stefan

-- 
       ___
  oo  // \\      "De Chelonian Mobile"
 (_,\/ \_/ \     TortoiseSVN
   \ \_/_\_/>    The coolest Interface to (Sub)Version Control
   /_/   \_\     http://tortoisesvn.net
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=3029662
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].