- Paperback: 384 pages
- Publisher: Microsoft Press; 1 edition (September 10, 2003)
- Language: English
- ISBN-10: 0735618399
- ISBN-13: 978-0735618398
- Product Dimensions: 7.4 x 0.9 x 9 inches
- Shipping Weight: 1.6 pounds
- Average Customer Review: 13 customer reviews
- Amazon Best Sellers Rank: #4,242,835 in Books (See Top 100 in Books)
Enter your mobile number or email address below and we'll send you a link to download the free Kindle App. Then you can start reading Kindle books on your smartphone, tablet, or computer - no Kindle device required.
To get the free app, enter your mobile phone number.
Enterprise Solution Patterns Using Microsoft® .NET 1st Edition
Use the Amazon App to scan ISBNs and compare prices.
Fulfillment by Amazon (FBA) is a service we offer sellers that lets them store their products in Amazon's fulfillment centers, and we directly pack, ship, and provide customer service for these products. Something we hope you'll especially enjoy: FBA items qualify for FREE Shipping and Amazon Prime.
If you're a seller, Fulfillment by Amazon can help you increase your sales. We invite you to learn more about Fulfillment by Amazon .
Get expert guidance on patternsâsimple, proven mechanisms by which software professionals can share important architectural tradeoffs and design decisionsâand help reduce the complexity of building high-performance, enterprise-class business solutions. Focusing on architectural, design, and implementation patterns for Microsoft .NET, this guide captures the knowledge of seasoned developers and shares their time-tested patterns and best practices. Developers and architects learn how to use individual patterns for specific technical scenarios, as well as how to combine patterns to build more complex solutions. All PATTERNS & PRACTICES guides are reviewed and approved by Microsoft engineering teams, consultants, partners, and customersâdelivering accurate, real-world information thatâs been technically validated and tested.
Showing 1-8 of 13 reviews
There was a problem filtering reviews right now. Please try again later.
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 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.,
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. ;)
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.
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.
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.
Maybe my expectations were incorrect, but I had expected a more hands-on than philosophical (almost-marketing) work.
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.