U
Ubergeek
I recently came accross an article that stated that there were
unresolved issued with calling native (i.e. "unmanaged" C++) from
managed C++.
Does anyone know what the precise details of this issue is, and if there
have been any fixes/workarounds yet?. I am using C# (VC7.1) for my
frontend, but all my logic is tied up in Win32 C (and some C++) dlls.
If I understand the issue correctly, so long as I compile the native
C/C++ Dlls with VC6 (not VC7.1), I should not have an issue, and I will
be able to wrte managed C++ wrappers around my C/C++ API without any
problems - is this a correct assesment of the issue?
unresolved issued with calling native (i.e. "unmanaged" C++) from
managed C++.
Does anyone know what the precise details of this issue is, and if there
have been any fixes/workarounds yet?. I am using C# (VC7.1) for my
frontend, but all my logic is tied up in Win32 C (and some C++) dlls.
If I understand the issue correctly, so long as I compile the native
C/C++ Dlls with VC6 (not VC7.1), I should not have an issue, and I will
be able to wrte managed C++ wrappers around my C/C++ API without any
problems - is this a correct assesment of the issue?