why interop.xxx.dll generate by .net dev
-
when refing com dll(eg. xxx.dll),the .net dev auto generates a corresponding interop.xxx.dll,i can't understand this oddball action,why does it occur?
-
when refing com dll(eg. xxx.dll),the .net dev auto generates a corresponding interop.xxx.dll,i can't understand this oddball action,why does it occur?
william_zhou wrote: i can't understand this oddball action I can't understand this oddball statement. Do you take a similar view of everything you don't understand? Did you notice that using the COM dll you referenced isn't much different from using a .NET dll? No IUnknown, QueryInterface, CoCreateIntance, etc. Well, that's the functionality the interop dll provides. It handles conversions and marshalling between COM and .NET data types and handles the dirty work needed to use COM components with the CLR, which doesn't know COM from a hole in the ground. There is a lot of information available on the subject, should you be interested. Beyond (COM) Interop: Has Anyone Seen the Bridge?[^] Calling COM Components from .NET Clients[^] Charlie if(!curlies){ return; }
-
william_zhou wrote: i can't understand this oddball action I can't understand this oddball statement. Do you take a similar view of everything you don't understand? Did you notice that using the COM dll you referenced isn't much different from using a .NET dll? No IUnknown, QueryInterface, CoCreateIntance, etc. Well, that's the functionality the interop dll provides. It handles conversions and marshalling between COM and .NET data types and handles the dirty work needed to use COM components with the CLR, which doesn't know COM from a hole in the ground. There is a lot of information available on the subject, should you be interested. Beyond (COM) Interop: Has Anyone Seen the Bridge?[^] Calling COM Components from .NET Clients[^] Charlie if(!curlies){ return; }
thank Charlie, you have told me what i want to know,and the more correlative information is useful to me, thanks a lot!