How is that enough to get the CLR hosted.  That would imply that all managed DLL's have CLR startup code in them and they all
'host' a copy of the CLR and we would then have multiple managed heaps etc.  That can not possibly be right.

-------------------------------------------
Roy Chastain
KMSystems, Inc.

I was of the opinion that the unmanaged C++ CRT only initialized the CLR when the code was compiled to use CLR.  I was also under
the impression that this would only happen in the EXE not in a DLL.  Now it appears that my impressions and understandings are not
at all right, so the question now becomes.

In the case of a STRICTLY unmanaged EXE (not compiled to use CLR) calling a managed (Mixed Mode in this case) C++ DLL, does the
runtime initialize the CLR on every call into the DLL or does it do it once in DLL main (or the equivalent)?

Second question, is why is this such a mystery?  I have not found any documentation from MS that would EVEN SUGGESTS that this
approach works.  All of their documentation talks about calling CorBindToRuntimeEx from the unmanaged code and then doing COM like
things to find interface pointers.

In a nut shell, what are the trade-off between what appears to be a reverse It Just Works method of calling managed code from
unmanaged vs. explicitly hosting the CLR as is (almost) documented by Microsoft?

-------------------------------------------
Roy Chastain
KMSystems, Inc.