We have started creating several managed c++ projects that are interdependent (meaning they reference another managed c++ project).  Since inception of these libraries we have noticed two significant problems:

1.  When performing the pre-build step (implicitly done by VS due to referenced managed c++ project), visual studio does not always copy the compiled assembly from the same build configuration as the project is being compiled with.  EG a debug build will copy a compiled release version of the assembly.  This is a significant issue because the other build configuration could be out of date.  We have to keep cleaning the "other" build configuration to get it to copy the correct assembly file for tlbexport.

2.  We are noticing that since using references (as opposed to #using, which is not build-order safe), building our solution from the command line no longer performes the aforementioned prebuild step, and all assembly dependent types cause compile errors thus killing our build process.  This process does not fail when compiled through the IDE.