John,
> Should I put my managed classes into a separate managed C++ project (one
> that compiles into a standalone assembly)? I don't know what else to
> try.
I think that could be one approach. The problem might be that the compiler
does indeed need to use #using on the library to correctly pro
I have a largely unmanaged C++ application that's broken up into several
static libraries. I have added a managed C++ class to one of these
libraries (let's say it's a.lib) and then referenced that managed class
from some other managed code in b.lib. The libraries all compile
successfully.
Howeve
