Re: [ASAP]: Exporting CString in DLL
- From: "Mark Randall" <mark[__OKTHISISFAKE_]yr@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 27 Mar 2006 00:40:21 +0100
"Peter Schmitz" <PeterSchmitz@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:0985C59C-EA05-431E-8AC4-098A2F4AC55C@xxxxxxxxxxxxxxxx
Hi,
thanks for replying! All DLLs use the same function declarations and
LPTCSTR
results in the same linker error. When I remove the strings (for testing
purposes) from the declaration, everything works and links fine....any
ideas?
One last thing. The DLLs that make use of the exported functions of the
new
DLL are converted to the new VS2005 format, the DLL that exports the
function
was created directly with the latest version.
Firstly, CString sucks when working with DLLs because you have to make sure
the type matches (CStringA or CStringW).
Secondly, are you using T defines? ie: _UNICODE and UNICODE.
--
- Mark Randall
http://www.temporal-solutions.co.uk
"We're Systems and Networks..."
"It's our job to know..."
.
- Follow-Ups:
- Re: [ASAP]: Exporting CString in DLL
- From: David Webber
- Re: [ASAP]: Exporting CString in DLL
- References:
- [ASAP]: Exporting CString in DLL
- From: Peter Schmitz
- RE: [ASAP]: Exporting CString in DLL
- From: Peter Schmitz
- [ASAP]: Exporting CString in DLL
- Prev by Date: Re: Design orientated 'C' question
- Next by Date: Re: Function call evaluation order
- Previous by thread: RE: [ASAP]: Exporting CString in DLL
- Next by thread: Re: [ASAP]: Exporting CString in DLL
- Index(es):
Relevant Pages
|