Re: So stuffed up
"Jack" <jl@knight.com> ha scritto nel messaggio
news:e8oOqT7yIHA.1772@TK2MSFTNGP03.phx.gbl...
I think I should try VS2005, but the problem is I don't have the
app-wizard file for VS2005 (no supported files from the max sdk). This
app-wizard brings me a lot of convenience. Do you feel that I should start
building the project from scratch with VS2005?
Jack: programming is not "guessing".
I mean: you should have some points clear:
Is your SDK a set of COM objects/DLLs?
If so, you are free to use VC6, VC7.1, VC8 (VS2005) or whatever.
But if your SDK is *not* a COM-based SDK, and you don't have source code
(just header and .lib or DLL files with C++ interface), then you *must* use
the same compiler that was used to build your SDK.
So, was your SDK built using VC6? Then, you must use VC6.
Was it built using VC2005? Then you must use VC2005.
Frankly speaking, if your SDK comes with VC6 wizards, I think that it is
built using VC6, so you are fine using VC6.
Have you tried what I wrote in another post of mine, i.e. to double-check
that your importing/exporting mechanism is correct?
I pasted from previous post:
---[begin]---
[...]
Another suggestion was to put the method implementation *outside* header
file:
// In header .h file:
CoreExport virtual TCHAR * GetRsrcString(long id);
// In .cpp file
TCHAR * ClassDesc::GetRsrcString( long id )
{
return _T("Something...");
}
BTW: Do you properly use preprocessor macros for
__declspec(dllimport/export) ?
// --- In header file:
#ifndef CoreExport
#define CoreExport __declspec( dllimport )
#endif
// --- in .cpp file:
// Define before #including header
#define CoreExport __declspec( dllexport )
#include "ClassDesc.h" // Header file
....
---[end]---
HTH,
Giovanni