Cool web site - 1368 COM Integration Appendix H Fig. H.5 Fig.
1368 COM Integration Appendix H Fig. H.5 Fig. H.5Fig. H.FiFi5g. H.5g. H.5Add Reference dialog DLL Selection. When a COM component is registered, its GUID is stored in the Windows Registry; programs then can use the registry to locate and identify the component. Once a program has located a desired component, it uses the component s type library to find and use the library s objects and methods. A type library describes all of a COM component s interfaces, types and methods; the type library is included in either the component .dllfile or in a separate .tlbfile. The separation of component identifiers (located in the Windows Registry) from the data represented on the disk (the library file) is the source of many problems associated with the COM architecture. By contrast, .NET components avoid these problems by maintaining all identification information internally. When Visual Studio imports a COM component, it creates a file that contains all identification and data-description information internally. Visual Studio obtains the component GUID from the Windows Registry and converts the data description from the type library-format into the .NET assembly format. This processing creates a new DLL file, called a primary interop assembly, which then is placed into the applications bindirectory. The primary interop assembly is used by .NET to locate COM methods and to translate component data types between the .NET platform types and COM component types. The translation for each COM component is performed by a Runtime Callable Wrapper (RCW). The RCW is a proxy object created by the .NET runtime from the information in the object s primary interop assembly. The RCW manages the COM object and performs communication between .NET code and the COM object.
Go visit our java server pages services for a reliable, lowcost webhost to satisfy all your needs.