wsgd wrote:
> Rach, Darshan a écrit :
>> Hi,
>>
>> I tried “mt -manifest oqtp.dll.manifest -outputresource:oqtp.dll;2”
>>
>> But still I am getting and error “oqtp.dll.manifest : general error
>> c1010070: Failed to load and parse the manifest. The system cannot
>> find the file specified.”
>>
>> I tried to do a clean and then make a build, but this does not help.
>>
>> Any suggestions on this?
>>
> I suggest you explain the 1st problem, it could help for searching the
> solution :
> - what's happen when you put your dll into PC\program
> files\wireshark\plugins\*<version>* ?
> - which version of wireshark /windows ?
> - which version of wireshark /windows / Visual Studio used for dll
> generation ?
You probably shouldn't create a manifest for your DLL. None of the
plugins that ship with Wireshark do. It can cause WinSxS errors like the
ones described at
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=3272
The main Wireshark executables (wireshark.exe, tshark.exe, etc) load the
CRT at startup. Your plugin shouldn't duplicate that effort.
--
Join us for Sharkfest ’10! · Wireshark® Developer and User Conference
Stanford University, June 14-17 · http://www.cacetech.com/sharkfest.10/