Exposing VB .NET Objects to COM Clients
The majority of this chapter has dealt with the most common use of COM Interop—consuming COM objects from managed applications. There will be times, however, when the opposite will be true—unmanaged applications want to call managed code as they would any other COM object. Exposing .NET classes as COM objects enables any unmanaged COM client to use managed classes as COM servers. This type of functionality is useful on many levels, such as during the conversion of large, complex Windows DNA-based applications comprised of many COM objects running on one or more computers. Having the capability for .NET classes to present themselves as COM objects might allow you to re-implement parts of your application ...
Get Microsoft® Visual Basic® .NET 2003 Kick Start now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
