Some COM clients, including scripting clients, can only access the default (IDispatch) interface on an object. If your object wants to expose multiple interfaces to such clients, one solution is DISPID Encoding. In this week's ATL article, Andrew illustrates one technique for accomplishing this.
Articles Written by Andrew Whitechapel
Some COM clients - including scripting clients - can only access the default (dispatch) interface on an object. If your object wants to expose multiple interfaces to such clients, one solution is DISPID Encoding. This article shows how to do it with the ATL.
Andrew illustrates the underlying mechanics of aggregation vs. containment in ATL, why you'd want to choose one technique over the other, and how each is supported by the ATL through macros and classes.
In his latest contribution, Andrew ponders the question posed by many of you brave enough to dive into the undocumented waters of WTL: When should I use WTL as opposed to ATL or MFC?. In doing so, he walks you through just how easy it is to create a "Hello World" windows application with WTL in order to give you some perspective on just how productive this template library can be
Think ATL is only for components? In Andrew's first installment of his new ATL/WTL column, he presents a complete tutorial (including two demos) on using the ATL windowing classes to write full-fledged Windows applications.
What exactly is a tear-off? Why you might want to use one, and how the ATL supports both regular and cached tear-off interfaces. Are they worth spending time on? In this article, Andrew teaches you everything you wanted to know about tear-off interfaces, but were afraid to ask.