How OS diffentiates COM dll and assembly??

  • Thread starter Thread starter Esha
  • Start date Start date
How OS diffentiates COM dll and assembly??

I can't think of a situation where the OS has to do that.

But if it does, it can look at the PE headers to determine if a
library is a managed module or not.

COM in-proc libraries are required to export certain entry points,
such as DllGetClassObject.


Mattias
 
You must log in or register to reply here.

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

calling .net 2.0 assembly from .net 1.1 1
Combing COM dll and C# assembly in sigle assembly 2
Huge problem with References DLL's. Please Help 3
COM & NET integration 1
Strong Name for VB COM dll 2
Resolving assembly dependencies when using a windows service 0
Unable to add reference 0
how to reference COM dll from C# without the COM dll being registered in the registry? 1

Back
Top