5 comments about C# COM+ Programming (With CD-ROM).

1. Excellent book for a person that needs to understand how C# and COM+ work together. Well written.



2. COM+ is equivalent with Java's EJB. I was utterly disappointed to find the book littered with misspellings. There is no depth to its topic coverage. The book's table of contents is misleading. Save your heard earned money and wait for something near the quality displayed by Oreilly's Enterprise JavaBeans.



3. This book is poorly organized and lacks focus. The topics' coverage is shallow. Even with the lightweight content, it should be titled or described as "How to Transition COM+ programming with VB to C#".



4. I honestly don't like writing bad reviews but I feel compelled to save people money when I can. Unless you are looking for a manager's overview of COM+ programming don't buy this book. Coverage of COM+ itself is very light. The author appears to assume that the reader has picked that up someplace else... probably by writing COM+ components in VB 6. There are no in-depth discussions of the technology or even best practices. The jist of this book is that now you use attributes to COM+ enable your code written in C#. The coverage of what attributes are available to you and within those attributes what options are supported and what they mean is likewise incomplete and lacking in depth. However, where I really lost respect for this book was when I looked in the registry to see what was going on from a COM perspective for the classes that I had built based on the code fragments in the text. What a mess. Stale registry entries for previous builds of my components were everywhere. It took me an hour to get the mess cleaned up and several more to piece together what was going on and realize that there are a lot of COM specific attributes never mentioned in this book that you need to known about in order to build a COM+ component _correctly_ using C#. And as I have discovered that is the crux of the situation. To do COM+ using C# you need to be _very_ familiar with COM-CLR interop. Basically you need _much_ more information than this book provides.

   In summary I believe that reading this book will serve only to make one `dangerous' not proficient in COM+ development using C#.




5. If you're looking to get a solid background and understanding on the subject matter, this book does a very good job of covering the bases (not just the basics). What's better is that it comes in a size (# of pages) that one can actually hope to digest. Well done.

2 comments about Success With C++/Book and Disk.

1. This is a good book for the beginning C++ programmer. The book is well written, well organized. All the source code complies and if you work through all the source code, you'll have a good understanding of C++ after you finish.



2. I read this book some time ago, but continue to use it as a reference. This book was written with the beginner in mind. Kris has a unique way of explaining the topic so that it is comprehendible for the entry-level C++ developer, but is not overly simplified as to cause an intermediate level developer to loose interest. This book is also excellent for procedure level programmers (such as strait C and Pascal programmers) wishing to make the jump to C++. That is a particularly hard market to please because the developer is an intermediate or advanced level developer, but may need an entry level C++ or OOP book in order to master the concepts of OOP. Most entry level C++ and OOP books tend to bore such developers, This book handles them in perfect stride.

4 comments about Essential Visual C++ 6.0 Fast: An Introduction to Windows Programming Using the Microsoft Foundation Class Library (Essential Series).

1. Microsoft Foundations Class (MFC) library in 200 page ? sorry I don't think so.

   Sure many of us (programers) need sometimes to learn a special subject fast but this book is not for exprianced programmers - it's too shalow.

   Ok so it's not for exprianced programmers , how about people how just entered the world of windows programing , well here the book is too fast. MFC is NOT easy ! even if you are good in C++ the book's 200 pages on MFC is just confusing and not enough.

   I really don't recommend it for any of the above so I really don't know for who this book suits. (this is why I was cheap in stars).

   I will conclud my review with a suggestions -

   1. don't learn C in 21 days

   2. don't learn C++ in 21 days

   3. don't learn MFC fast

   or to sumerize it don't learn anything in 21 days. it simply don't do you any good , it just hurts !

   sorry , but it isn't my kind of a book -

   Enjoy




2. This book was definately not worth it. 200 pages of code with not a very good expaination behind it. The author tells you the "how" and not the "why". If you want to learn to program with MFC and know how and why your program works, then stay away from this book. If you want the code without needing the how or why, then this book is for you. This book is more of a reference than a learning tool.

   If typos and misspelling bother you too, then stay away from essential visual C++.




3. The previous reviewers are correct in saying this book is too fast for beginners; it has very little by way of explanation as to what's going on in the example programs given. But it shows working, minimal MFC programs that the programmer can enter in directly without using the Visual Studio graphical tools and wizards. I found this illuminating since most Visual C++ tutorials use the wizards, which generate example projects with numerous source files, which obscures what's going on. I think the target audience for the book might be someone like a physicist who wants to write a simple Windows program, but who doesn't want to spend time learning MFC -- all he or she would need to do is copy the relevant example (e.g., the example in chapter 15 which plots a graph) and modify the code as needed. If the goal is to learn MFC with understanding, Prosise or Kruglinski et al would be much better, and certainly much more comprehensive. (But the learning curve is steep whichever route is taken.)



4. This book is a reasonable choice for someone who has learned true object oriented programming in C++ but has not been exposed to Windows programming with MFC. The reader must understand function overloading and the operation of constructors for derived classes in depth or the book will be very difficult to follow. There are some minor typos, and the author does not explain everthing that goes on, but it is FAST. A scientist or engineer can get to a nice GUI for his application in a hurry without having to depend on the Wizards. For this narrow audience, the book is a good choice.

5 comments about Applied C++: Practical Techniques for Building Better Software (C++ In-Depth Series).

1. A true disappointment. Other books in the series (Sutter, Alexandrescu, Koenig & Moo) have been instant classics, but I get the feeling that Stroustrup didn't really read this one (he's the "series editor", not the "book editor", and not mentioned in the acknowledgements). If he had, I doubt he'd let the following gems see the light of print:

   -- "It is easy to spend too much time researching the problem in hopes of finding the most efficient STL component. For example, we could have also chosen to use std::set, as this matches the requirements of our object very closely. ...If you have not used many STL components, you will soon discover that you end up using only a small subset of objects..." (p. 107) In the context, the authors have just selected a std::map whose value type they plan to ignore completely. The C++ standard library is TINY compared to most other currently popular languages, and much more consistent. Wouldn't it be more worthwhile to take a second to learn about std::set just this once, so you'd remember it next time?

   --"Namespaces were added to the language to prevent name collisions, but aside from their use in the standard C++ library, we have seen little use of them elsewhere." (p.74) Then, they go on to advocate prefixing all class names, a la "apString". Why not just make an "ap" namespace, if you realize that that's what namespaces are for? Maybe they haven't seen any use of namespaces because they systematically avoid them out of sheer stubbornness?

   The book is filled with other inane advice displayed in special boxes: "If you decide to graphically depict your object relationships, take advantage of both axes to represent them." Darn, why didn't I realize this sheet of paper was two dimensional? Glad I bought the book!

   The only remotely redeeming factor is the stuff on image processing, but any two-bit text devoted to image processing would be better. Heck, just about anything you could dig up on Google would be just as good, I imagine.

   Finally, the included CD stinks. After all that, what you get is essentially a makefile with some lousy code--not even a dummy application that lets you see it in action.

   I wish I could give it 0 stars, but it doesn't seem to be possible. Don't waste your money--almost any other AW book on C++ would be a better choice.




2. I was a little bit disppointed with this book, especially when I look at other books in this serie.

   Although I cannot find any point totally wrong in this book, I cannot find anything that I did not already knew. I believe that this book is best suited for people rather new to the profession, or maybe even more to people who only use C++ as a better C, and would like to start using C++ specific features.

   Maybe in this case, they can find in one book what usually requires at least three books. But that would not take them as far as those three books would do.

   I think my biggest disappointment with this book, is that when the authors discuss about their design, they explain how it work in details, sometime they even suggest why they choose this possibility, but they almost never review other possibilities to weight to pro and con of each one.

   The text is sometime a little bit tedious to read (the kind of repetition that one would expect in documentation where everything has to be detailled, but not in book).

   Finally, there are some technical points where I disagree (or where I beleive a better solution exists, and should at least be evoqued):
   - The use of prefix instead of namespace, making code more difficult to read, and I believe even more innapropriate in a book than in real life
   - Not a word about the template techniques that might unroll the loops they tediously unroll manually
   - The use of trait associated with pixel type could probably ease the use of the library (for instance, specifying the type to be used by default when adding two pixels)
   - I think it is rather surprising the way the authors complain about a change in the standard from a well defined behaviour to a buggy one that broke their previous design on purpose (you may think I am cynical, but they _complain_ about this special point at least three times in the book (for their function add2), but never explain why the standard is written as it is)




3. There are many books about C++, and there are many books about software development. This book is one of the best I've seen at combining the two topics. The authors are obviously real-world developers because they offer real-world solutions and approaches, unlike the authors of many development-oriented books who apparently live in ideal worlds where every project goes perfectly.

   C++ continues to be one of the most popular programming languages ever, and I highly recommend this book not only to any developer who writes C++ applications for a living, but also to team leaders and architects who want to make sure their teams are writing the best code possible. I can say based on years of experience that the techniques offered in this book are critically important for real-world, robust, production-quality C++ applications.




4. As a programmer who had never done any image processing before, this book helped raise my knowledge from zero to a reasonably good understanding of 2D image processing, and provided me with a very useful framework that I am using everyday in my job.

   I feel that the book also does a good job demonstrating template techniques, and provides a good overall SW development process to follow.

   The authors have been very responsive to questions and problems, which I greatly appreciate.

   The only thing I really didn't like was the lack of makefiles for the non-template code. I would have liked to have a makefile that creates a library automatically. I ended up doing it myself, which frankly wasn't all that difficult.




5. I wholeheartedly agree with the reviewers that gave this book 1 star. From page 12, when the first class in the book (apImage) itself is incompletely defined (the definition "pixels_" is missing) it is a steep and fast ride downhill. This book is going to be returned -- this would be the first time I am returning a book.

5 comments about 1001 Visual C++ Programming Tips (Miscellaneous).

1. You either already know what it says or it is too hard to understand.



2. You either already know what it says or it is too hard to understand.



3. One of the best programming titles I own. It is my best book on Visual C++.

   The book is packed with working source code examples (hundreds). I was able to cut and paste working code from the book into my apps which saved me time.

   Highly recommend.




4. I find this book gives short details on just about every subject it holds.
   Although some may agree its good for beginners, its definetly something i wouldnt read front to back when im new to C++.
   But the good thing about this book is if your looking for a function or cant remember what certain code does, it does explain it well enough for you to remember and also gives you little hints and tips for what your searching for.
   Id almost say its a MUST HAVE for any C++ programmer.



5. Well since the book was written to be a refference to someone who is pretty handy with Visual C++, beginners do not read this book.
   But, if your like me, I have a hard time remembering some funtions of some MFC classes and so on.
   This Book makes a great refference and shows you examples and a full explantion of how that piece of code works.
   Definetly a must have for any MFC programmer like myself :).

5 comments about C and the 8051, Vol.I: Hardware, Modular Programming & Multitasking (2nd Edition).

1. Is perfect 8051 text and/or reference for coming from another processor, for going embedded, and for either the novice or expert C programmer (embedded or not). Covers both ANSI C and Assembly for the 8051, using Keil's Assembler and Compiler (which is what Franklin sold as their own for many years). Includes a Demo Keil full set of tools on CD (limited to amount of code, but still creates the HEX files). And, anything learned from the book or CD directly transports to the full Keil tools in the workplace (which are most likely the most prevalent 8051 software tools in use). GET THE LATEST EDITION (2nd or later), unless you are into FORTH or PLM! Cover's multi-tasking and efficient approaches for 8-bit micro programming, as well as some straight-forward hardware interfacing examples.



2. This book is extremely difficult to follow, nearly 30% of the content of the book is held in footnotes, making the text nearly impossible to comprehend. Most of the book is written in first person, and makes many dangerous assumptions about the background of the reader. None of the assumptions are listed and it is up to the reader to decifer them. This book is little more than a collection of class notes from a professor and would only be of value to someone actually taking the class. I am very sorry I wasted my money on this book.



3. This book is perfect if you have two things: (1)a very basic background in ANSI c, (2)a intermediate bacground in 8051 assembly.

   This book is NOT a beginner step by step book in which a reader could learn the 8051 and c with this single book. I had a firm handle on writing assembly and c code for the 8051. Unfortunatly I was pretty unclear how one could have much memory control using C. Shultz's book answered it all for me including how one would control and interrupt vector table with C.

   Shultz obviously knows what he is doing and leaves some information to the reader to figure out. The book is rather expensive for the sheer amount of information that could be obtained. If this were handled better, this book would have recieved a 5-star.

   I'll certainly recommend this book to anyone looking to fill in the gaps of mixing 8051 with the C language.




4. I found this book to be very informative, written well, and quite good at explaining the concepts. But you should take my background into consideration. I have a 4 year degree in computer science, am very familiar with system architecture and operating systems concepts, and have several years of C programming experience.

   I would strongly reccomend this book to any software engineers looking to experiment in electronics/microcontrollers. However, don't expect to learn C from this book, or to learn the ins and outs of 8051 assembler. It merely provides a good, broad foundation for most of the things you would want to do with one of these things.




5. I have read the reviews of those above me and have to ask... did they even read and *use* the listed material? Most everything of importance is in the footnotes which cover nearly 40% of the book. This is the second edition of his book, and still, he cannot get even FOR loop writen in asembly written correctly. Secondly, the Computer Engineering department of the University of Missouri - Rolla, has decided on a whole, the book is worthless. Too much time is spent correcting his errors as opposed to learning the material. What Shultz does do well is the methodology. It really is a shame he has no plans at all to go back and fix the errors in the book.

No comments about Computer Algorithms / C++.

5 comments about The C++ Training Guide (Training Guide Series).

1. Every book has things that I don't like and this book has a few. But, compared with ALL the other books I have tried to read, this one is head and shoulders above the crowd. The disk comes with a C++ compiler so you get everything the book tells you that you should be getting. I needed that comfirmation as a confidence builder; I learn by doing. I learned C++ and I am moving on to Heller's "Who's afraid of more C++?," which is the sequel.

   Just another note: Heller doesn't just teach the syntax of the language, he teaches you the details of programming. He taught me hexidecimal math. He helps you understand how the C++ is translated by the compiler. I have never seen such a generous discussion in any C++ book. Which leads me to my complaint... I am impatient and all these details took some discipline. If you want to benefit from these chapter, some of them require a good deal of thinking.

   I am sure that I am much farther along because of this extra information. And maybe my programs won't generate so many General Protection Faults as a result of that discussion.




2. sir/madam,

   I am in the starting stage in c++. Please send c++ programms and Notes.

   Thanking you, Lakshmanakannan.




3. I have not read this book. I don't know alot about programing. I know some HTML and a little Javascript. I know alot about linux and unix but zero C++. I really need to know if this is a good book for a begginer like me.



4. If you are looking for a real book plz don't choose this one. I felt really cheated... it is very very very very beginner ... and the way it is written is very poor.. even the fonts are misrable ....



5. The C++ Training guide is an outstanding book for a beginner who wants to learn programming. Here is why:

   - Crystal clear description of how program code actually works, all the way down to the hardware level (machine language, bits, registers, etc.). - A clear relation of how the various C++ "tools" can be applied in programming, as opposed to simply listing them and how to write them. - The inclusion of dialogues between the author and a novice using the book. An author can easily take for granted that something he understands is just as clear to a beginner. These dialogues help point out and resolve conceptual obstacles the author would not have thought of. - The use of concrete examples to illustrate points. - The provision of a compiler (on a companion CD). - The inclusion of exercises to try your skill, with solutions in the text. - Incredible detail and completely thorough coverage. - A friendly, conversational tone that makes the book a pleasure to read. - Clear, down to earth language. - An author who is INCREDIBLY accessible. I had a lot of problems with installing and setting up the compiler. Steve exchanged a number VERY detailed e-mails with me, sticking with me until it was completely resolved. He is amazingly patient.

   Steve Heller loves programming, and has a natural talent for explaining things. This book was wonderful not only because it teaches the nuts and bolts of the C++ language, but because it shows how it all actually works in the computer, all presented in a straightforward, logical manner, that makes it quite enjoyable to read. It is almost like reading a novel.

   I noticed another review that knocked the writing, and complained the skill level was for beginners. That reviewer must be a plant. I am a writer myself, and can attest to the high level of the writing. As to the skill level, it says on the book that the skill level is "Beginning/Intermediate." Go figure.

5 comments about Visual C++ 6 Database Programming Tutorial.

1. This book is awful! The books loses focus and forgets who its audience is over and over. There are discussions about the mandatory features that need to be implemented when writing a database driver, Visual Source Safe, and many other topics that don't have any thing to with writing a C++ database application.

   To make matter worse the book is also riddled with typos - both grammar and code. The book spends more time discussing MFC than it does implementing the database code. The coding style displayed in this book is that of a beginner. If you are an beginner programmer this is an example of how NOT to program. The code is very inconsistent and poorly laid out. Functions for common pieces of code are never created and instead copied each time that it is needed - sometimes 3 or 4 times in one tiny example application).

   This isn't the typical book that you would expect from Wrox. Their books are normally solid, but this one really misses the mark. Save your money.




2. An excellent book to learn C++ database programming using MFC and ATL. The examples are clear and the code compiles and works! I am a professional Visual Basic programmer who uses ADO in building Visual Basic interfaces to Access, Oracle and SQL Server databases. I have C++ experience, but little C++ Windows programming experience. I highly recommend this book if you want to learn C++ database programming.



3. This book is so full of grammatical and typographical errors, it is virtually unreadable. I read through about half the book and gave up. There are an average of 5 errors per page - that's over 1000 errors in a 200 page book! I want my money back. The author and publisher should be ashamed to have offered this book to the public.



4. As someone who has basic skills in Visual C++ and a little better knowledge of databases and using Access, I found this book to be more of a help than a hinderance. I learned a few extra things that were of relevance to me. I found its explanation of MFC to be helpful, while the first 2 chapters were review of old info for me.

   Before buying it, however, I'd try to find it at a university library or get it though interlibrary loan.

   "An introductory book that attempts to cover the main data access technologies currently in use, including ODBC, DAO, OLE DB, ADO AND RDS."

   Keeping that in mind, the author accomplished that task.




5. I have to agree with the folks that panned this book. I don't know what the reviewers who applauded it were looking at.
   
   Sadly this is another example of what we see too much from Wrox, a hastily written, superficial, badly edited ( I would say not edited at all. I can't believe the number of typos and grammatical errors. ) book rushed into print to try and cash in.
   
   For shame, Wrox.

1 comments about Microsoft Visual C++ .NET Language Reference (Pro-Documentation).

1. Amazon has listed the wrong publication date for this book. It is not 2006 - the actual publciation date is 2002 (and Amazon's correction system won't let you put in the correct date).
   
   The reason the publication date is important is that much of the material in this book about managed extensions is outdated and does NOT apply to Visual C++ 2005. For instance, __gc class is now replaced with ref class, tracking handle ^ replaces pointer *, etc. So, if you have old managed code you need to convert to 2005, this book will be of no help. And if you're writing new managed code, this book will lead you in the wrong direction.
   
   This is an OK book as a reference for conventional C++. Microsoft needs to publish an updated version for managed code. But I doubt they will since they don't really want us to use C++ (they are pushing us to use their own languages, C# and Visual Basic).