Re: PB Generated DLL
- From: "voidcoder" <voidcoder@xxxxxxxxx>
- Date: Thu, 11 May 2006 11:59:51 +0200
Well, do you have any *.DEF file in your DLL project?
"Nick Farrow" <NickFarrow@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:17A4168C-A0F9-480E-A9EB-03B53C1F4BFD@xxxxxxxxxxxxxxxx
Thanks Paul,
Checked with good old dumpbin and the extern "C" route looks to be producing
the standard non mangled exports. Must be something else ...
"Paul G. Tobey [eMVP]" wrote:
Well, those two will definitely generate different results. You can use the
dependency viewer that should be installed in the Visual Studio path
somewhere (search for "depend"), to see what actually was exported, or you
can use dumpbin, the command line tool, to see what's in the DLL.
Paul T.
"Nick Farrow" <NickFarrow@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:197A9274-01BA-466C-BEC7-AFF97A4085F9@xxxxxxxxxxxxxxxx
Hi,
IS there a trick to exposing the entry points from a PB generated DLL ?
I have tried extern
"C" __declspec(dllexport)
__declspec(dllexport)
And the dotnet app thats trying to latch onto these always throws a
EntryPointNotFound exception ?
Any idea of the correct linkage to use ?
Thanks
nick
.
- References:
- Re: PB Generated DLL
- From: Paul G. Tobey [eMVP]
- Re: PB Generated DLL
- Prev by Date: CF 2.0 on headless configuration
- Next by Date: Re: Wake up from suspend
- Previous by thread: Re: PB Generated DLL
- Next by thread: how to identify different appliction call in the stream driver which can open more one time.
- Index(es):
Relevant Pages
|