We specialize in hard to find items
All Categories
*Price and Stocks may change without prior notice
*Packaging of actual item may differ from photo shown
- Electrical items MAY be 110 volts.
- 7 Day Return Policy
- All products are genuine and original
About Beginning Atl Com Programming
Product Description The book covers programming the latest version of the Active Template Library ( ATL ) which is currently in version 2.1. The book uses Visual C++ 5 as the programming environment. Earlier versions of VC++, back to 4.0 may be used in conjunction with the ATL additions that can be downloaded from Microsoft. VC++ is increasingly used to develop ActiveX components for use elsewhere, for example in VB or on the Web. These components have to small and light, and be able to interoperate with whatever their host application is. COM is the Microsoft technology that allows the components to interoperate, while ATL is a tool that simplifies the creation of these components. Where VC++ programmers use MFC to create stand alone applications, ATL is a lighter, faster substitute for creating just components. Amazon.com Review The Active Template Library (ATL) is the part of the Microsoft Foundation Classes (MFC) used to build reusable and very efficient components in C++. Achieving this efficiency can be difficult, as it requires you to delve into the details of Microsoft's Component Object Model (COM) and ATL itself. With Beginning ATL COM Programming, however, it should be possible for any C++/MFC programmer to become productive with this exciting component technology. The book begins with the basics of COM programming, featuring good details on the actual Win32 APIs used throughout COM programming. (This section also discusses the basics of the component definition, including Interface Definition Language [IDL] and related conventions.) While higher-level classes in MFC make it easier to build COM components, you'll have to do most of the work yourself if you're building lightweight ATL controls. The authors cover such ATL topics as event handling (with connection points), automation and error handling, and properties and persistence for ATL-based components. They use plenty of short, effective code examples throughout this tutorial to illustrate key concepts. The book closes with an example of Internet Explorer ATL controls (which are leaner) and "full" controls (which can be reused in such applications as Visual Basic). The world of ATL development is rough terrain, but the team of authors here succeeds in explaining a difficult subject clearly. --Rich Dragan From the Publisher The book is primarily for Visual C++ developers (although ATL is freely available from Microsoft's web site at present and can be used with some Borland compilers). The reader will be fairly experienced in using MFC, and may well have used the Wizards to produce simple MFC controls in the past. The book is ideal for people who need to get to grips with the principles of COM and the ways in which ATL handles much of the complexity for the programmer About the Author George has spent 10 years in C&C++ and developed in Windows since C7 and the SDK. He is an ActiveX expert and a member of Microsoft's IIS team - founder member of all the IIS / ISAPI discussion forums Dr. Richard Grimes is a former distributed computing architect with Parallax Systems in the U.K. and now is a full time Author, Consultant and Speaker specializing in COM and DCOM programming Julian Templeman is a lecturer in C/C++/Java . He specializes in COM and MFC based development. He is an established Author and speaker Alex Stockton is a Physicist and computer book Technical Editor. Alex is an expert in COM /DCOm/C++ and ATL development Excerpt. © Reprinted by permission. All rights reserved. Chapter Four Automation and Error Handling During this chapter, you'll see a number of different terms to describe the interfaces supported by an Automation object. This is largely for historical reasons. The term 'Automation' was first coined in the phrase 'OLE Automation' when COM was first developed. The philosophy then was that a programmer could write several Automation objects - some with user interfaces and others without - and then 'glue' them together to creat
