-----Original Message-----
From: wireshark-dev-bounces@xxxxxxxxxxxxx [mailto:wireshark-dev-bounces@xxxxxxxxxxxxx] On Behalf Of Guy Harris
Sent: den 18 oktober 2012 08:11
To: Developer support list for Wireshark
Subject: Re: [Wireshark-dev] r45615: Read the program name rather than hardcoding it
On Oct 17, 2012, at 2:22 PM, Anders Broman <a.broman@xxxxxxxxxxxx> wrote:
>> Guy Harris skrev 2012-10-17 22:13:
>>> On Oct 17, 2012, at 12:35 PM, Anders Broman <a.broman@xxxxxxxxxxxx> wrote:
>>>
>>>> One use case is a internal version which would be nice to be able to
>>>> install co-existing with a release version with separate profiles
>>>> and preferences. Having a different program name makes it clearer that it *is* a internal version.
>>> ...but what's different about it isn't its name, what's different about it is the version.
>> ?
>> The the dissectors would be different...
>
>...but that's not a function of the *name*, it's, again, a function of the *version*.
>
>> On windows the program installation dir, short cuts, registry entries
>> and installer "paths" contains the name Wireshark if you do multiple installations of Wireshark by defining
>>different installation dirs application data would still be shared and uninstalling one version might rip the
>>personal settings etc out - that might be considered a bug.
>
>The personal settings are in your "profile" directory, not in the installation directory; as far as I know, the >NSIS uninstaller doesn't know about them and won't remove them.
>From unistall.nsi
:Section /o "Un.Personal Settings" un.SecPersonalSettings
;-------------------------------------------
SectionIn 2
SetShellVarContext current
Delete "$APPDATA\${PROGRAM_NAME}\*.*"
RMDir "$APPDATA\${PROGRAM_NAME}"
SectionEnd
:
PROGRAM_NAME used to be hardcoded Wireshark
