Articles Written by Andrew Whitechapel

ATL DISPID Encoding

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.

Dispinterface vs. Events and Runtime Sinks

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.

Containment and Aggregation

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.

To WTL or Not to WTL, That Is the Question

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

Using the ATL Windowing Classes

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.

ATL Tear-Off Interfaces

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.

Top White Papers and Webcasts

  • When individual departments procure cloud service for their own use, they usually don't consider the hazardous organization-wide implications. Read this paper to learn best practices for setting up an internal, IT-based cloud brokerage function that service the entire organization. Find out how this approach enables you to retain top-down visibility and control of network security and manage the impact of cloud traffic on your WAN.

  • Following an IT incident through to resolution is more than just acknowledging an alert and restarting a server. The recent State of On-Call Report found that it takes most companies an average of 10-30 minutes to resolve an incident with an average of 5 people involved. Imagine how much money and time companies are spending to deal with incident resolution. But what if you had a tool that offered solutions baked in? Or a tool that sent alerts to the right person or team every time? These are the kind of …

Most Popular Programming Stories

More for Developers

RSS Feeds

Thanks for your registration, follow us on our social networks to keep up-to-date