I had a little experience with Des.Pat and this book helped me to speed up my knowledge. I encourage people to start DP with this book. This is less theory and a lot of practice. Which is very good. I have seen other books but they are a lot of theory less implementation and they are talking very very academic. So it's hard to understand. But this book brings you up to academic knowledge by given simple examples.

If you want to get up to speed quickly on OOP practices this is an excellent starting point. I wish more authors would write books like this, both writing style and material. Deborah has an easy to read style that makes the material she covers easy to comprehend.

The book walks the reader through a small and simple project. The downloaded code sample works and the build along instructions are accurate; and if followed will produce the same code as the downloaded version. There were a few time where I got to a point that I thought something was overlooked or wrong; and in each case when I turned the page or read the next 2-3 pages all was explained; this too helped me feel I was getting a good grasp of the material being presented.

So, with all this praise, why did I only give the book 4 stars? In my opinion there should have been another two - three chapters to really complete the material. What is in the book is how to use objects and bind them to Win forms, how to build a three-tier project and how to use the bound forms to edit records. What's missing is the Add & Delete functionality. Using bound objects with the DataGridView you lose the native ability of the grid to do column sorts since the objects being bound to do not implement iSortable (this is mentioned in the book but it would have been nice to have included). There was a nice use of Nullable(of Date) but this too would have been nice to expand (SQL allows for a null date but .NET doesn't allow Date types to be null, this creates some problems that the nullable(of Date) doesn't really overcome.

So, a Great book I highly recommend. It does a great job with the material it does cover; and you get a reusable development framework in the process, I just wish there were a few more chapters to really complete the material covered.

If you know design patterns well, you make different accross developers! This book is describing each design pattern with an example. Sometimes it is difficult to get everything through one example but I'd recommend this book to everyone. I am good at vb.net so application of design patterns in vb.net is a big plus for me.

If you know design patterns well, you make different accross developers! This book is describing each design pattern with an example. Sometimes it is difficult to get everything through one example but I'd recommend this book to everyone. I am good at vb.net so application of design patterns in vb.net is a big plus for me.

I am been reading this book. It covers majority of patterns, nicely categorizied. Book is not very length, explains concepts properly.
I recommend this books for any VB.Net programmer who wants to keep upper hand from thier peers.

I purchased this book a long time ago and I have to admit a lot of the information presented went right over my head in the beginning. I felt the book was too hard to understand mostly because I was still very new to .Net in general. Well, after spending a few months working on a real life project, I got the suspension that our architecture could lead to problems in the future. So I started researching design patterns and asking other people on message boards how they approach design. After all of that, I decided to review this book again and I was amazed at how much of the information was sinking in my brain this time of around. I especially love the section on applying design patterns to the data access tier. I still have more to re-read, but that is my favorite section so far. This is a great book for design pattern newbies like myself. The approaches in this book can also work in C# although some minor syntax changes would have to be made. Well worth the price.

This book is the best explication of what and why, and of what not and why not, that I have read, and I own hundreds of programming books. It covers all three logical layers. BUY IT!

There's definately some good explanation of design patterns in this text, but if you're looking for best practices in .NET coding, you're going to need to look elsewhere.

The book begins with a chapter that explains the basic premise behind the most common creational, behavioral and structural patterns. This chapter is excellent and provided me with the most insight into how I could change the way I develop applications using patterns.

The next chapters deal with how to implement these patterns in the data tier, middle tier and presentation tier. The examples are illustrative, if nothing else. BEWARE THEIR CODING TECHNIQUES! The authors actually implemented the disposal of unmanaged resources like database connections inside of a Finalize() method!!! With the .NET Framework's implementation of automatic garbage collection, this is the absolute last thing you'd ever want to do with an unmanaged resource. They should have used the IDisposable interface.

I'll give them three stars for their treatment of the topic, but these guys are lousy .NET coders.

This book illustrates, explains and simplifies design patterns. It is very easy to read, follow and understand. Although all patterns are mentioned in the book only a select few are detailed in the beginning of the book. The remainder of the book provides information how design patterns are used in the n-tier architecture, such as the data tier, middle tier and presentation tier.

The books offers one of the most fascinating concepts in developing the presentation tier, called MVC, a.k.a. Model, View, Controller. MVC decouples the user interface from the form/control events on a form and placing this logic in a controller class or classes. The controllers have full control of the model aspect of the framework where the controller puts data in the view or the user interface from the model.

MVC uses patterns within its framework. For example the controller is made of algorithms and therefore is a strategy pattern. The relationship between the view and model is an observer pattern, while the view is a composite and the relationship from the view to the controller is a factory pattern. Using the factory pattern the controller is created, uses the data in the model and the view is updated via the observer. The book however goes into to detail how to forgo the observer pattern by using data binding with ADO.NET and a data grid. The observer pattern in MVC is not explained, other than in the beginning of the book as the pattern itself as opposed relating to a framework.

You are not limited to just these patterns within MVC. I have used the visitor pattern, the mediator pattern and the command patterns within my controller classes to achieve different methods to communicate and alter the data within the model. It is my opinion that as long as the View, the Model and the Controllers are decoupled from each other then you have achieved MVC.

With excellent code and UML examples, I suggest owning this book as I find myself studying it time and time again attempting to master MVC and implementing best practice with design patterns. Another good book I highly recommend is C# Design Patterns.

I was originally skeptical when a colleague suggestesd the book, since I'm a C# programmer and the title talked about business objects in VB.NET. Don't let that disuade you! With the code interoperability of .NET it doesn't matter. The code I downloaded from the website compiled first time! (Which rarely happens) and the examples touch every major angle of using the framework. For diehard C# geeks, there are user contributed ports to C#. I've been a little more open-minded in the bookstore since I bought this book. Definitely buy this book!

Tom Fischer, et al, do a nice job explaining the basics design patterns with the newly object-oriented Visual Basic (VB.NET): which pattern is used against what type of problem. This book is great for people migrating from VB6 who have never dealt with objects and it's a good introduction to the topic.

The book covers most of the original Gang of Four (GoF) models in a very readable, pragmatic way.

For those of you that hears about Design Patterns but don't know C/C++ and are having issues finding good ressources to adapt Design Patterns in the VB area, this is the book for you.

Rather than attempting to compete with 'Design Patterns : elements of Reusable Object-Oriented Software', from Addison-Wesley, they extend it so that VB developers can learn how to understand design Patterns and apply them inside our applications.

The book covers the following common patterns :
Singleton, Abstract Factory, Factory, Adapter, Facade, Bridge, Composite, Decorator, Proxy, Observer, State, Strategy,Template.