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 process the metadata contained therein, and just linking against it doesn't quite work because of this. OTOH, you could consider just getting the managed class out of the .LIB and compile it independently (not into a .LIB) into a .OBJ file, and then use #using on it... Thr trick would likely be _not_ putting the managed class into the static library too, just put them completely separate. But now that I think about it, I can't see why the compiler wouldn't be able to do the same on a .LIB, since they are, after all, PE files, too. Never tried it, though... -- Tomas Restrepo [EMAIL PROTECTED] You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
