teekaysoh_at_gmail.com wrote:
>
> On Sep 20, 9:51 am, Stefan Küng <tortoise..._at_gmail.com> wrote:
>> teekay..._at_gmail.com wrote:
>>> According to the Dumentation.exe, the tortoise client's installer
>>> "must not deinstall" TortoiseOverlay:
>>> '''
>>> If you have a non-msi installer, you can call the msi installer
>>> like this:
>>> msiexec /i TortoiseOverlays-1.0.0.XXXX-win32.msi /qn /norestart
>>> But in that case, you also must not deinstall it when your client
>>> gets
>>> deinstalled.
>>> '''
>>> I am not familiar with msi installer, but doesn't the reference
>>> counting take care of that?
>> Reference counting is done by module, not by package. It's not possible
>> to install a package (an msi) twice.
>> That means, reference counting only works for the merge module, not the
>> msi itself.
>>
>>> The problem I see here is that the users will need to manually
>>> deinstall TortoiseOverlay (assuming there's only one tortoise client
>>> using TortoiseOverlay), in order to make room for other tortoise
>>> clients that do not use TortoiseOverlay.
>> The msi installer adds an entry in the 'software' panel. So users can
>> uninstall it manually without problems.
>>
>> The best way to handle this is to create a real msi installer for your
>> application and use the TortoiseOverlays merge module to install the
>> overlay handler.
>> I know that many people like to use 'easier' installers than msi, but MS
>> requires msi installers for all applications now anyway if they want the
>> 'works on Vista' certificate.
>
> Honestly, I don't really care about the certificate, at least for now.
> But thanks for sharing this note.
Honestly, I don't care about the certificates either. But msi has other
advantages too, like distribution via GPOs.
>> What you could do however: you could create your own msi installer just
>> for the TortoiseOverlays handler using the provided merge module. That
>> way, reference counting would work and you could uninstall your own msi.
>
> I am a bit confused on this. If I install TortoiseOverlays with my
> own installer this way, wouldn't that create two separate
> installations of TortoiseOverlays if I also installer TortoiseSVN?
> Would this cause problem with MS Explorer?
Yes, this would cause two installations: one for TSVN, and one with your
own installer. But: since you would install TortoiseOverlays with the
provided merge module like TSVN does, msi would recognize that two
applications use the same module and correctly handle this with its
reference counting.
> In any case, any resource on how to create my msi installer out of the
> merge module. I apologize, as I am really new to this whole msi thing.
I've attached an example WiX file to create such an installer.
Stefan
--
___
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.net
Received on 2008-09-21 08:56:53 CEST