Although you can't access this event data automatically from the language, you can write a component that receives the data and relays it to your program. However, it doesn't directly handle events from late-bound COM objects. Isual Basic® 6.0 is a good tool for creating, assembling, and testing COM components. The Visual Basic client receives the notification from the bridge and extracts all the information relative to the event from the supporting object. The bridge component transmits the intercepted event data back to the Visual Basic client using another supporting COM object that is capable of holding event data and attributes. This article explains how to build a bridge component that does just that. SUMMARYSince a Visual Basic client doesn't handle events directly from late-bound COM objects, it needs some way to capture all the events and parameters launched by any COM object server instantiated at runtime and not known at design time. This article assumes you�re familiar with Visual Basic and ATLĭownload the code for this article: Connpoints.exe (99KB)īrowse the code for this article at Code Center: COMBRIDGE_EVENT In this article COM: Handle Late-bound Events within Visual Basic Using an ATL Bridge
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |