https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=5847
--- Comment #6 from Bill Meier <wmeier@xxxxxxxxxxx> 2011-04-22 10:32:40 EDT ---
I don't know if there is a "best practice" for this situation.
I should note that I deal that the same kind of issue for other applications:
For example, when I have several different programs installed to show images or
video & etc.
In those cases I pretty much have to manage the file associations myself or
have to explicitly open a file in whichever application I want to use.
So: I suggest the following:
1. Implem,ent the use "more self-contained filesystem and registry paths" as
described in comment #4. If a version of Wireshark which "owns" certain
associations is un-installed, then the associations should be removed. I
wouldn't make any effort to try to do any re-associations to another installed
Wireshark version if it exists.
The above deals with the issue of being able to keep track and uninstall
multiple wireshark versions and is better than what is done currently.
If there is a need to associate the file extensions with a different version of
Wireshark, obviously that version can simply be re-installed.
(Or: the associations can be manually configured with a little bit of effort).
2. If there really is a need for a way to easily change/assign Wireshark file
associations (in Windows) presumably a "file associations" dialog can be
implemented.
IMO step 1 is all that is needed for now.
Assuming there's no objection to the above, as an exercise to learn about the
use of NSIS, I'll take a whack at doing step 1. (I suspect the change may be
fairly simple).
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
