B
Bret Pehrson
I just need to confirm now (after I've spent several days chasing mystery
metadata warnings/errors) that this is *NOT* possible:
Link a managed C++ static library into a (managed) C# application.
NOT POSSIBLE?
Please respond *only* if you *know* the answer, I'm not interested in
conjecture.
For those that care: my project is *not* trivial, and is a migration from C++.
The library in question is composed of 100's of files, and isn't trivial to
convert to either a DLL or C# (at least w/o seriously affecting my timeline).
Finally, presuming that the above is not possible, why wouldn't the C#
compiler/linker emit a simple error such as "Cannot link C/C++ static library
with C# project"?
metadata warnings/errors) that this is *NOT* possible:
Link a managed C++ static library into a (managed) C# application.
NOT POSSIBLE?
Please respond *only* if you *know* the answer, I'm not interested in
conjecture.
For those that care: my project is *not* trivial, and is a migration from C++.
The library in question is composed of 100's of files, and isn't trivial to
convert to either a DLL or C# (at least w/o seriously affecting my timeline).
Finally, presuming that the above is not possible, why wouldn't the C#
compiler/linker emit a simple error such as "Cannot link C/C++ static library
with C# project"?