Re: CLR details- Are MSCorEE.dll and MSCorWks.dll\MSCorSvr.dll COM ser
- From: "Willy Denoyette [MVP]" <willy.denoyette@xxxxxxxxxx>
- Date: Mon, 27 Feb 2006 22:50:31 +0100
Yes, they are and both COM DLL's...
mscoree.dll exports the standard DLL COM register/unregister functions, like
dumpbin reveals...
58 18 000115F3 DllCanUnloadNow = _DllCanUnloadNow@0
59 19 000105C6 DllGetClassObject = _DllGetClassObject@12
60 1A 000198DF DllRegisterServer = _DllRegisterServer@0
61 1B 00019975 DllUnregisterServer = _DllUnregisterServer@0
while mscorwks.dll does not, however that doesn't mean it's not a COM DLL,
it's not a requirement of COM to export these.
MScorEE.dll is called a shim because it's used to load the CLR in the
process (through COM on Windows).
Willy.
"Manoj Agarwal" <ManojAgarwal@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:2D6109BD-7B1A-4AD8-8DAB-95BE50A32718@xxxxxxxxxxxxxxxx
|I had read that the CLR is actually implemented as a COM server in the
files
| MSCorWks.dll (or MSCorSvr.dll). But when I get a list of exported
functions
| by this dll then it doesn't have the COM functions DllGetClassObject,
| DllRegisterServer, DllUnRegisterServer and DllCanUnloadNow. It has
functions
| like DllCanUnloadNowInternal, DllRegisterServerInternal etc.. So are these
| files really COM servers?
|
| Also, is MSCorEE.dll a COM server? And why is it call the shim?
|
| Thanks,
| - Manoj
|
.
- Prev by Date: Application has generated an exception that could not be handled
- Next by Date: RE: Debugging challenge
- Previous by thread: Application has generated an exception that could not be handled
- Next by thread: Re: CLR details- Are MSCorEE.dll and MSCorWks.dll\MSCorSvr.dll COM
- Index(es):
Relevant Pages
|
