<< 1 >>
Rating: 
Summary: Learn how to make Visual Studio work for you!
Review: Don't buy this book.I have been programming for over 15 years and need to learn to use VC++. I started reading from the front cover and started doing the examples on VC++. I found the tutorials difficult to follow, very incomplete, and does not explain what you're doing. In short, you're blindly following the instructions and then the instructions don't work. Don't buy this book. Please note the bottom of the front cover says "John Paul Mueller, Best-Selling computer Book Author with 40 Books Published". I doubt I'll find myself buying another one of his books or from this publisher.
Rating: 
Summary: Use This Book for a Door Stop
Review: I purchased this book to use as a reference. I had hoped it would be friendlier & perhaps a little more intelligent than MS documentation. This book simply cannot be called complete and the authors do a poor job of anticipating the sorts of question one might ask when working with VS6 on a day-to-day basis. I haven't investigated other books on VS6 but with this in mind, it seems to me that almost any other book on the subject is likely to be better.
Rating:
Summary: Use This Book for a Door Stop
Review: I purchased this book to use as a reference. I had hoped it would be friendlier & perhaps a little more intelligent than MS documentation. This book simply cannot be called complete and the authors do a poor job of anticipating the sorts of question one might ask when working with VS6 on a day-to-day basis. I haven't investigated other books on VS6 but with this in mind, it seems to me that almost any other book on the subject is likely to be better.
Rating:
Summary: Hardly Complete
Review: I would not consider this book a "complete" reference. It totally lacks any support for Visual Foxpro. Also I found the examples to be very short and not very detailed. I ended up returning this book.
Rating:
Summary: Learn how to make Visual Studio work for you!
Review: Most of the computer books that I've read concentrate on one language. So, if you buy a book on Visual Studio, what you normally get is a single language view of the product, with an assortment of small examples in other languages thrown in for good measure. John Mueller has gotten past the single language perspective in his book. What you'll see is examples where all of the languages are used together to create a complete application. The examples are non-trivial and well designed. John also makes it clear as to why he chose a specific language for a given task. While this book didn't necessarily teach me as much as I would have liked in new programming techniques, it taught me something much more important, how to make best use of Visual Studio as a whole. There are some real plusses in this book. I found the examples all concentrate on the enterprise, rather than on the desktop. That's a real advantage because I don't write many desktop applications anymore. I also enjoyed all of the tips and especially the Web site pointers. About the only omission in this book is a lack of any FoxPro coverage. I don't consider this a very big loss because FoxPro is hardly a good choice for enterprise applications, especially new development. The author's choice of SQL Server is a good one.
Rating:
Summary: Great Book for Enterprise Projects!
Review: The title of this book is completely wrong. For one thing, itsensibly rejects Visual Foxpro and uses SQL Server instead. Inaddition, the book is oriented toward team development, not the individual developer. I probably would have called this book Team Developement for Visual Studio 6 or Enterprise Development for Visual Studio 6. Once you get past the title and accept the book for its intended use, you'll find that it's a real gem. I found that I got a lot of very good team development strategies, along with good tips on what to avoid. I also loved the Web site pointers--they've really made it easier to find what I need quickly. The tips and notes were well thought out and have helped me to avoid many programming pitfalls. The example programs aren't as complex as I would have liked, but they were adequate to demonstrate how to use the various pieces of Visual Studio together in a team environment. I feel the author was trying to make this a problem solving book, but failed to convey that as clearly as he should have. The book contains outstanding troubleshooting information, but you have to dig a little too hard to find it at times. I gave this book five stars for several reasons, but the most important is that the author has provided the team development information that Microsoft failed to provide. If you're looking for a real world guide on how to use Visual Studio with teams, this is the best (and only) book out there worth getting. END
<< 1 >>
| 
