Re: Bizzare error following change of _export to __declspec(dllexport)
- From: "Martin Pritchard" <martinpritchard@xxxxxxxxxxxxxxxxx>
- Date: Fri, 3 Mar 2006 09:35:22 -0000
Ta,
Have entered it in and going to try and debug it.
Thanks for your help,
Martin
"David Lowndes" <DavidL@xxxxxxxxxxxxxxx> wrote in message
news:atmd02pm9hk6bmu7fie879cja561vkdtc2@xxxxxxxxxx
Any ideas where I can find out how to debug the registration process of
the
dll?
Martin,
Assuming this is a normal COM registration you're talking about, all
that happens to register it is that it's run like this:
regsvr32 yourdll.dll
Enter that as the command line/parameter in the debugger settings of
the project, and set a breakpoint on your DLL's DllRegisterServer
function - or let it run till it crashes and see if you can determine
why it crashes.
Dave
.
- References:
- Bizzare error following change of _export to __declspec(dllexport)
- From: Martin Pritchard
- Re: Bizzare error following change of _export to __declspec(dllexport)
- From: David Lowndes
- Re: Bizzare error following change of _export to __declspec(dllexport)
- From: Martin Pritchard
- Re: Bizzare error following change of _export to __declspec(dllexport)
- From: David Lowndes
- Bizzare error following change of _export to __declspec(dllexport)
- Prev by Date: Re: access memory
- Next by Date: Re: Help for me:LNK2019
- Previous by thread: Re: Bizzare error following change of _export to __declspec(dllexport)
- Next by thread: RE: Bizzare error following change of _export to __declspec(dllexport)
- Index(es):
Relevant Pages
|