"Professional ASP.NET Design Patterns" is all about showing you how to use the power of design patterns and core design principles in real ASP.NET applications. The goal of this book is to educate developers on the fundamentals of object oriented programming, design patterns, principles, and methodologies that can help you become a better programmer. Design patterns and principles enable loosely coupled and highly cohesive code, which will improve your code's readability, flexibility, and maintenance. Each chapter addresses a layer in an enterprise ASP.NET application and shows how proven patterns, principles, and best practices can be leveraged to solve problems and improve the design of your code. In addition, a professional-level, end-to-end case study is used to show how to use best practice design patterns and principles in a real website."Professional ASP.NET Design Patterns" is for ASP.NET developers who are comfortable with the .NET framework but are looking to improve how they code and understand why design patterns, design principles, and best practices will make their code more maintainable and adaptable. Readers who have had experience with design patterns before may wish to skip Part 1 of the book, which acts as an introduction to the Gang of Four design patterns and common design principles, including the S.O.L.I.D. principles and Martin Fowler's enterprise patterns. All code samples are written in C# but the concepts can be applied very easily to VB.NET.This book covers well-known patterns and best practices for developing enterprise-level ASP.NET applications. The patterns used can be applied to any version of ASP.NET from 1.0 to 4.0. The patterns themselves are language agnostic and can be applied to any object oriented programming language.Professional ASP.NET Design Patterns can be used both as a step-by-step guide and as a continuous source of reference to dip into at your leisure. The book is broken into three distinct sections. Part 1 is an introduction to patterns and design principles. Part 2 examines how patterns and principles can be used in the various layers of an ASP.NET application. Part 3 represents an end-to-end case study showcasing many of the patterns covered in the book. You may find it useful to work through the chapters before reading the case study, or you may find it easier to see the patterns in action by reading the case study section first and referring back to Part 2 for a more detailed view on the patterns and principles used.Within those parts the coverage The origins of the Gang of Four design patterns, their relevance in today's world, and their decoupling from specific programming languages. An overview of some common design principles and the S.O.L.I.D. design principles follows, and the chapter ends with a description of Fowler's enterprise patterns.Layering Your Application and Separating Your ConcernsA description of the Transaction Script pattern followed by the Active Record, with an exercise to demonstrate the pattern using the Castle Windsor project. The Domain Model pattern demonstrated in an exercise with NHibernate and a review of the domain-driven design (DDD) methodologyPatterns and principles that can be used construct your objects and how to make sure that you are building your application for scalability and Factory, Decorator, Template, State, Strategy, Composite, Specification and Layer Supertype. Design principles that can improve your code's maintainability and flexibility; these include Dependency Injection, Interface Segregation, and Liskov Substitution PrincipleService Oriented Architecture, the Facade design pattern, messaging patterns such as Document Message, Request-Response, Reservation, and the Idempotent patternThe Data Access Two data access strategies are
Book introduces design patterns such as Null object pattern, state pattern, singleton, adaptor pattern, factory method, decorator, template method, strategy pattern, etc. that you can use in data access layer, business layer, and presentation layer. There are also sample codes.
Definetely the best tech book i ve ever read. He explains lots of best practices from great ppl like Martin Fawler, Robert C. Martin and Eric Evans in a manner that is very easy to understand.Most importantly its in C# and also the book was written in early 2010, so its pretty new stuff. It explains concepts using things like EF, ASP.NET MVC and also mentions lots of open source tools we can use. Maybe little bit too overwhelming if you are new, but i read most of the other concepts from books like Patterns of Enterprise Application Architecture so that they made sense to me.
(Reading dates are approximate, as is often the case with my reviews, this time because I was reading two other programming books concurrently, and I got a bit hazy as to where one began and the other ended.)
This is a straightforward tutorial on ASP.NET WebForms development. Example code is in C#. When I bought this book, nearly a decade ago, .NET 4.0 was the most recent version, and the code assumes that version. (So any version of Visual Studio from 2010 on up should work fine.) Like a handful of my other quite-useful-but-tragically-concealed-until-recently books, it was stored in a warehouse until just over a month ago. Undoubtedly there are more current resources available today, but you can't beat WROX for depth, and if you're gonna start somewhere, this is a better spot than most.
I'd recommend this as Prong Three of a three-pronged course in modern Web development. The O'Reilly publication RESTful Web Services will get you started with REST and programmable-Web concepts, and then RESTful .NET will apply them to the .NET realm. That should cover the programmable Web fairly nicely, after which you'll want to use this one to cover the human-readable Web. You'll get a very thorough treatment of design patterns, which are not really touched on in the other two. Plus, you know, all that UI stuff, which falls outside the purview of Webservices.
These three books should cover the back end and programmable aspects of Web development tolerably well, and this one will bring some UI design to bear, especially if you download the complete source code library from the WROX side (to complete the case study project, Agatha's Clothing). But to be perfectly rounded, you'll want to additionally pursue some instruction in HTML5 and the various Javascript libraries currently in vogue. There is very little in the way of HTML design in this book, although you will learn some Silverlight, which utilizes XAML, the same technology underlying Windows Presentation Foundation.
One thing I value about this book is that it provides a pretty decent overview of design patterns in general at the start, and then dives deeply into how to implement the more Web-centric ones. As a developer, you should at least be familiar with the 23 Gang of Four patterns, and those are all touched on here, but there are many others that are useful in the context of Web development, particularly Model-View-Presenter and Model-View-Controller, which is highly demanded right now. Work through the examples (I'm still doing this, although I finished "reading" the book a couple weeks back) and then update your resume to reflect MVC. Then maybe spend some time designing new UIs to hang on the codebase you developed through the sample code, and build yourself a nice portfolio.
A must read for any asp.net software developer. If you are a junior programmer who has just started programming, you might have a little bit of difficulty absorbing everything, but you will definitely get better after reading this. This book serves as a solid foundation for better designing. The explanations in this book are simple and easy-to-understand yet pretty comprehensive.
Really great, practical application of design patterns. I started reading this right after completing Fowler's Patterns of Enterprise Application Architecture, so this really cemented some of those concepts.
this books summarizes all OOD theory and practice I had gathered left end right in one comprehensive overview. I'm sure it will help me in building more robust applications.