Thanks!
-Original Message-
From: wireshark-dev-boun...@wireshark.org
[mailto:wireshark-dev-boun...@wireshark.org] On Behalf Of Jaap Keuter
Sent: Friday, February 20, 2009 8:19 AM
To: Developer support list for Wireshark
Subject: Re: [Wireshark-dev] Help - Peculiar behavior with DLLs
Hi
Hi,
I never said they couldn't be loaded, I said: "there is a guarantee that it
will
fail unpredictably sometime". These failures can be subtle, like incorrect
decoding, missing information, wrong column information. Stuff like this has
happened and causes great confusion, because it isn't obv
I tried plug-ins across versions.
Only copy msvcr71.dll (msvc2003) or msvc80.dll(mcvs2005) at the wireshark
installed directory,
then compiled plug-ins can be loaded.
___
Sent via:Wireshark-dev mailing list
Archives:ht
Hi,
Plugins aren't portable across versions. They may seem to work, but there is no
guarantee (there is a guarantee that it will fail unpredictably sometime).
See http://wiki.wireshark.org/KnownBugs
Thanx,
Jaap
Blazer, Doron wrote:
> Hi,
>
> I have been developing under the latest development
] De la part de Blazer, Doron
Envoyé : lundi 16 février 2009 18:19
À : wireshark-dev@wireshark.org
Objet : [Wireshark-dev] Help - Peculiar behavior with DLLs
Hi,
I have been developing under the latest development sources (1.1.3 svn), a
plug-in dissector.
I compiled it to a dll - all fine.
Wh
Hi Blazer,
If you're saying what i think it is, you have both a .dll and a .dll.manifest
correct? use:
mt.exe -manifest foo.dll.manifest -outputresource:foo.dll;2
in command prompt after cd to your plugin/foo folder
then after that you should be able to copy your foo.dll to the 1.0.6
Greg
--
Hi,
I have been developing under the latest development sources (1.1.3 svn), a
plug-in dissector.
I compiled it to a dll - all fine.
When I add it to the "plugin" directory it all works fine (working with 1.1.3).
When I install 1.0.6 on a new machine (and add the dll to the "plugin"
directory),
