> On Sep 20, 9:39 am, "teekay..._at_gmail.com" <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
>> I am not familiar with msi installer, but doesn't the reference
>> counting take care of that?
>> 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.
> On a similar topic, I wonder what would happen if I install
> TortoiseOverlays again without uninstalling the previously installed
> one. This could happen when users are upgrading my tortoise client
> over the older release of the client.
> My understanding is that doing this increases the reference count, but
> I am not sure how the reference count works from the user perspective.
> Does a ref count of more than 1 imply that the user would have to
> uninstall TortoiseOverlays multiple time if they wish to completely
> remove TortoiseOverlays later (after installing my tortoise client, of
The reference count is only increased if the ID of the msi stays the
same but the version info does not. If both ID and version info stays
the same, an msi installation won't do anything (if the installation is
done with UI active, the user is presented with the options to remove or
repair, if no UI is available (i.e., command line installation), then
nothing will happen at all)
Also, if you upgrade your application, you should uninstall the 'old'
version before installing the new one - good installers provide such an
If you're using the merge modules, then the reference count will be
increased for the TortoiseOverlays module. In that case, you must make
sure that the old version is uninstalled during an upgrade.
> Also, how do we handle it in the situation where TortoiseOverlays
> itself need to be upgraded itself?
In case TortoiseOverlays gets a new version, the msi will take care of
upgrading. The merge module also will handle the upgrades.
This won't cause any problems, since the TortoiseOverlays must stay
compatible between versions (otherwise we would violate the COM
interface rules, and Explorer would not like that).
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.net
Received on 2008-09-28 10:16:57 CEST