Customer Reviews

Enterprise Solution Patterns Using Microsoft .Net: Version 2.0 : Patterns & Practices

5 star:		(3)
4 star:		(5)
3 star:		(3)
2 star:		(1)
1 star:		(1)

 

 

Actually, this book a great book for beginners.

But, it is a *must* read for Microsoft Solutions Architects and Senior Software Engineers.

However, I recommend that you read Martin Fowler's (et al) book "Patterns of Enterprise Application Architecture", before you read this one. And the book "Design Patterns - Elements of Reusable OO Software" before either of the above.

I know, you have to deal with enough dependancies while coding, you don't want someone you don't know telling you there are dependancies for reading a book. I practice "tough love". Deal with it. ;)

This is a very good book for an architect who designs Microsoft platform based solutions or integrates legacy solutions with Microsoft platform. The electronic version of this book is available on MSDN online. I found it after I bought this book, but I did not regret it.

The examples of the pattern implementations are not comprehensive, but they are a good start. I like this book, because it put many concepts and design paradigms together.

The book provides a good starting point to learn Microsoft .NET, especially if you would like to implement applications using patterns approach. However the book does give you a feeling of good read that it was hurried, and the examples really does not adress the challenges you will face in real .NET projects. I should've picked up the electronic version of the book available free at Microsoft rather than buying this book.

As the name suggest this book will teach you the enterprise patterns as they should be used under the MS .NET framework.
If you are already experienced in developing enterprise solutions, it does a real nice job in ordering things, and putting them into the right perspective.

More importantly if you are relatively new to .NET it will show you how each of the common patterns is implemented in .NET, and the common practices on how to use the framework. Saving you a long time poking through the framework to see what's there.
Since the MS implementations of patterns is sometimes different than the classic implementation, it does a good job in mapping the patterns you may already be familiar with to what the programmers of .NET had in mind.

All in all, if you are actively working to architect a new enterprise system or systems, you'll find this book helpful.

The Version 2.0 thing threw me off and I didn't even check the publish date (silly me). I thought it was for the new .NET 2.0 Framework. It's not.
Some of the OO stuff is really really glossed over in this book. It definitely assumes you have a solid OO background, which, unfortunately, I do not. I guess it's time to try to read through that old gang of four book, but it sure is friggin' dry.

This book covered material for those people work in enterprise level enviornments who are concern about their servers and wanted to keep their servers running 24X7.

This is a book for those professional want to enhance their professional skills and work in distributed system environment (Clustered Servers).

This book give you a good guidance to design great applications in simple readable manner. It covered areas such as Client Tier, Application Tier, Web Tier, and Data Tier. It shows how the .Net Service inter-related and gives you an overview of the .Net framework architect.

The book give you better understand of where .Net is heading and how to organize your programming structure along with your server configuration etc.,

I bought this book since I wanted to know not only what design patterns are feasible on the .NET framework, but how to implement it.

This book takes a text book approach to discussing the pros and cons of a particular design to solve a recurring problem in application design.

This book assumes you have some enterprise application experience and are familiar with the .NET framework. This is an patterns book that is applicable to .NET.

Since I'm a developer, the items of most interest to me were chapter 3, discussing web presentation designs: MVC (implemented in 3 ways), Page Controller, and Front Controller.

What I didn't like was the way that the example in the Front Controller didn't have the capability to dynamically specify which view was to be the target page following a command object execution.

Although the sequence diagrams were very good in helping understanding the concepts of web design patterns; I felt that they should have used more diagrams in the later chapters.

Other than that, I found the book to have sufficient enough information that I needed to know to buy it when I came across it at Borders.

Excellent Book , I bought a Pre-owned book at very low price .
I was little bit apprehensive about the condition when I ordered , but to my surprise it looks like a brand new book .

The Book gives detailed Information about the patterns and Its implementaion in C# language.

I recommend this book for every .NET developer.

If you have been programming for a few years, you would have used a few patterns without even knowing it. Encapsulating rules into a class is a classic one - also called the command pattern. But, describing the concept in a common way is what makes communication easier among the community. Patterns are documented approaches to solving common problems in software design. Microsoft's Enterprise Solution patterns Using Microsoft .Net: Version 2.0 comes off with a great deal of success in explaining the various patterns in a simple and lucid way.

If you use .Net languages for designing software, this book is pretty much a must in your library. Many pattern books so far (even the Gang of four book as well as the classic one by Martin Fowler) have been primarily in other languages AND a bit esoteric/abstract; thus they don't come close to being very useful right out-off-the-book if you are a .Net developer. Using .Net technologies make the sample easier to understand i.e., if you use ASP.Net and C#, the examples have a greater appeal.

The patterns are grouped as a cluster of related patterns. I like the fact that the patterns presented are progressively better at solving a problem. The web presentation patterns section is an example. The examples themselves are easy to understand i.e., if you are familiar to the .Net programming space, unlike the Gang of Four book which had non-business application samples. I also recommend the `Do Factory' set of examples for understanding and applying various patterns.

Don't get confused by the 2.0 in the title which refers to the version of the book rather than usage of .Net 2.0 for the samples (which by the way isn't an issue at all). If you are at a point where you want to understand what patterns are and/or understand more of them, this book is a great starting point mostly for the simplicity of presentation and clear examples.

This book contains nuggets of pure gold for anyone looking to design better software faster.

Don't be put off by the title "Enterprise Solution Patterns" - this book is not targeted solely at technical architects working on massive projects. The insights, analysis and examples are highly relevant to developers designing and building any non-trivial software.

The association with .NET needn't put you off reading this book, either, because the design patterns it contains are firstly described in the abstract and then applied using .NET - the patterns themselves are equally valid for Java developers, for example.

What makes this book outstanding are its structure and the clarity of its language.

Microsoft has created a framework in which its design patterns (and those of others) can be seen in a broader context - in the way they relate to each other and in the way they relate to the various software development roles (DBA, Developer, Operations Staff, etc) and the various tasks they perform (eg analyse, design, deploy, operate).

The clarity of thinking behind the book is matched by the clarity of expression within it. If you've struggled over the complexities of substantial design patterns, then this book will cut through the fog and give you much greater understanding into some of the best design patterns in use today.

Why would you read it? To make you a better professional, add to your armoury of proven solutions to common software design problems and steal a march over colleagues who still rely on personal experience and intuition rather than tapping into the combined experience of hundreds of successful developers distilled into a powerful, readable, practical book.