Re: Linking VS6.0 DLL to .Net 2003 - CString Error

sreenubkaimal@xxxxxxxxx wrote:

But if i recompile it in VS.net , will I b able to call the dll from a
wrapper written in VS 6.0 ?

I think i need to explain it ..

The main prob is that
1. The DLL can be created using .Net 2003 OR VS 6.0. (It should be an
MFC dll)
2. The DLL exposes classes and methods which uses CString.
3. Wrapper should be written in both .Net and VS 6.0 , for the same
dll.

The caller and the DLL have to use the same version of the compiler. So if you want to use the DLL from both a VC6 caller and a VS2003 one, you need two versions of the DLL.

David Wilkinson
.

Relevant Pages

  • Re: Looking for information on creating a multithreaded com projec
    ... Is there any specific reason to create this COM server as an MFC dll? ... Try it out using ATL project and by inserting a new ATL object. ...
    (microsoft.public.vc.mfc)
  • More Unicode woes - calling a MFC DLL
    ... DLL and in ExitInstance calls AfxFreeLibrary to unload it. ... Now, this works fine for both Unicode and ASCII builds, but there's ... the Unicode debug MFC dll is loaded. ...
    (microsoft.public.vc.mfc)
  • Re: Creating some sort of control by MFC. Problems
    ... In my main project I have a tab control which has few tabs. ... On that tab there are some windows where different modules of my application are implemented. ... Also I would like to implement module's window design and logic in separated DLL so I will be able to modify modules without recompiling main program. ... But actually it looks like more complex solution then just solution number one where I create simple MFC DLL. ...
    (microsoft.public.vc.mfc)
  • Re: MFC dll and exe porting to 64-bit
    ... MFC exe was able to load the dll dynamically and can find the exported ... The exported function CreateInstance(char*, char*, int, ... So I went on created a sample MFC dll and exe trying to prove. ...
    (microsoft.public.vc.mfc)
  • RE: MultiByte Application With Unicode DLL
    ... the memory leak would be caused by mixing Unicode MFC ... DLL with non-Unicode MFC DLL. ...
    (microsoft.public.vc.mfc)