I'm unsure of anyone else's experience but this has never worked for
me - and I have also got the same C++ error boxes during the dissector
loading on startup. I suppose, in theory, it would be ideal if you
could just drop the dll in, but I have resigned to the fact that I
have to deliver a custom build to users if I want them to be able to
use my plugins. Ideally (and keeping in with the spirit of
open-source) you should check in your new dissector to the Wireshark
SVN repository and get it included in the next build so your users can
just download an official version, but I can understand (as I'm in
that situation) that your firm may not want details of their
proprietry protocol's made available in open source.
On a side note, the only thing I don't like about it is the words
'Development Build' stamped on the UI graphics - but you tend to find
that once users have seen how useful it can be they forget about it :)
If anyone knows a way around this, though, I'd also be very grateful
for the advice!
Thanks,
Chris
On Fri, Nov 7, 2008 at 5:10 PM, Kaatz, David <David.Kaatz@xxxxxxxxxxxx> wrote:
> I build a dissector plugin dll on the 1.0.4 source.
>
> Should I be able to just give someone who has installed WS 1.0.4 my new
> dll and it will work if they put it in their $(INSTALLDIR)\plugins\1.0.4
> directory? Because I tested that on my own system and it causes a
> couple errors at startup, although WS will run I click through the
> errors.
> If it is possible what are the steps I need to take to get the dll to
> work this way?
>
> Attached jpgs show the errors.
>
> Thanks Chris for your prompt reply to my earlier installer question.
>
>
> Dave
>
>
> _______________________________________________
> Wireshark-dev mailing list
> Wireshark-dev@xxxxxxxxxxxxx
> https://wireshark.org/mailman/listinfo/wireshark-dev
>
>
