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
Product Details
Would you like to update product info or give feedback on images?
|
|
Share your thoughts with other customers:
|
||||||||||||||||||||||
|
Most Helpful Customer Reviews
9 of 9 people found the following review helpful:
5.0 out of 5 stars
not for beginners,
This review is from: Beginning Atl Com Programming (Paperback)
This book gives a serious coverage of ATL COM that will repay readers' efforts. It's far from easy, and the organization could be improved in places. For example, I'm one of those people who absolutely has to know what's going on "under the hood", but the implementation details come a little early (in Chapter 1). Had to experiment with the order of interface entries in the idl file and think a lot about vtables, interface pointer casting, multiple inheritance, and so on before I began to understand what Chap. 1 is all about. Some more explanation at judicious places in Chap. 1 would be helpful.To get the most out of this book, download the code from Wrox and fool around with it. This book really covers the nitty gritty of developing ATL COM projects from scratch. Marshaling, threading, connectable objects, persistence are discussed, and a full control is built in Chap. 8. For some reason, perhaps because the word "beginning" appears in the title, Wrox ranks this book below Professional MFC in difficulty (see the flow chart on the back cover of the book). Actually, it's quite advanced and belongs at the top of the hierarchy. I think it's more detailed and difficult (but also more rewarding) than other books on the subject.
12 of 13 people found the following review helpful:
2.0 out of 5 stars
Read another book,
By Richard Stockdale (England) - See all my reviews
This review is from: Beginning Atl Com Programming (Paperback)
As a VC++ and VB programmer, and the attempted reader of this publication for several months, this book never ceases to amaze me at how thoroughly poor it is in several aspects. I was perplexed by the detail that was covered by the first few chapters - immediately the reader in confronted by implementation details without first explaining the overall concepts. It seems as though the authors, have munged theory, tutorial, and reference together in each chapter, which unfortunately serves only to confuse rather than demystify ATL and COM. Other COM books take different approaches - chapters alternating between theory and practical tutorials. My biggest criticism is that seemingly straightforward concepts are explained to death, whilst the more complicated features are explained extremely poorly. I fear this book has definitely suffered from the 'too many cooks spoiling the broth' scenario. After a while I sought comfort in other COM pulblications for VC++ and VB, both from WROX and SAMS, which proved considerably better.
7 of 7 people found the following review helpful:
2.0 out of 5 stars
VERY Confusing,
By Scott Gines (Utah) - See all my reviews
This review is from: Beginning Atl Com Programming (Paperback)
This book was very confusing for me, and I am VERY fluent in C++/MFC. The authors used a LOT of really big words that I had no clue what they meant, without defining what they meant. I feel like they didn't sufficiently explain some of the core concepts, such as what an interface is, what a method is, why you would have 2 interfaces in 1 COM componet, etc... The chapters were too long and should have been broken up into more short chapters. They covered several subjects in each chapter. I think that the authors are very bright people who understand COM very well, and when they wrote this, they read it and said, "That makes perfect sense..." without having any newcomers read it.
Share your thoughts with other customers: Create your own review
|
|
Suggested Tags from Similar Products(What's this?)Be the first one to add a relevant tag (keyword that's strongly related to this product).
|
|
This product's forum
Active discussions in related forums
Search Customer Discussions
|
Related forums
|