book

Professional ASP.NET Design Patterns

Name: Professional ASP.NET Design Patterns
Author: Scott Millett
ISBN: 9780470292785

by Scott Millett

July 2010

Intermediate to advanced

720 pages

16h 48m

English

Wrox

Read now

Unlock full access

Copyright
ABOUT THE AUTHOR
CREDITS
ACKNOWLEDGMENTS
FOREWORD
INTRODUCTION
WHO THIS BOOK IS FORWHAT THIS BOOK COVERSHOW THIS BOOK IS STRUCTUREDPart 1: Introducing Patterns and PrinciplesChapter 1: The Pattern for Successful ApplicationsChapter 2: Dissecting the Pattern's PatternPart 2: The Anatomy of an ASP.NET Application: Learning and Applying PatternsChapter 3: Layering Your Application and Separating Your ConcernsChapter 4: The Business Logic Layer: OrganizationChapter 5: The Business Logic Layer: PatternsChapter 6: The Service LayerChapter 7: The Data Access LayerChapter 8: The Presentation LayerChapter 9: The User Experience LayerPart 3: Case Study: The Online E-Commerce StoreChapter 10: Requirements and InfrastructureChapter 11: Creating the Product CatalogChapter 12: Implementing the Shopping BasketChapter 13: Customer MembershipChapter 14: Ordering and PaymentCONVENTIONSSOURCE CODEERRATAP2P.WROX.COM
I. Introducing Patterns and Principles
1. The Pattern for Successful Applications
1.1. DESIGN PATTERNS EXPLAINED1.1.1. Origins1.1.2. Necessity1.1.3. Usefulness1.1.4. What They Are Not1.2. DESIGN PRINCIPLES1.2.1. Common Design Principles1.2.1.1. Keep It Simple Stupid (KISS)1.2.1.2. Don't Repeat Yourself (DRY)1.2.1.3. Tell, Don't Ask1.2.1.4. You Ain't Gonna Need It (YAGNI)1.2.1.5. Separation of Concerns (SoC)1.2.2. The S.O.L.I.D. Design Principles1.2.2.1. Single Responsibility Principle (SRP)1.2.2.2. Open-Closed Principle (OCP)1.2.2.3. Liskov Substitution Principle (LSP)1.2.2.4. Interface Segregation Principle (ISP)1.2.2.5. Dependency Inversion Principle (DIP)1.2.2.6. Dependency Injection (DI) and Inversion of Control (IoC)1.3. FOWLER'S ENTERPRISE DESIGN PATTERNS1.3.1. Layering1.3.2. Domain Logic Patterns1.3.2.1. Transaction Script1.3.2.2. Active Record1.3.2.3. Domain Model1.3.3. Object Relational Mapping1.3.3.1. Unit of Work1.3.3.2. Repository1.3.3.3. Data Mapper1.3.3.4. Identity Map1.3.3.5. Lazy Loading1.3.3.6. Query Object1.3.4. Web Presentation Patterns1.3.5. Base, Behavioral, and Structural Patterns1.3.5.1. Null Object Pattern1.3.5.2. Separated Interface1.3.5.3. Gateway1.4. OTHER DESIGN PRACTICES OF NOTE1.4.1. Test-driven Development (TDD)1.4.2. Domain-driven Design (DDD)1.4.3. Behavior-driven Design (BDD)1.5. SUMMARY
2. Dissecting the Pattern's Pattern
2.1. HOW TO READ DESIGN PATTERNS2.1.1. Gang of Four Pattern Template2.1.2. Simplified Template2.1.2.1. Name and Intent2.1.2.2. UML Diagram2.1.2.3. Code Example2.2. DESIGN PATTERN GROUPS2.2.1. Creational2.2.2. Structural2.2.3. Behavioral2.3. HOW TO CHOOSE AND APPLY A DESIGN PATTERN2.4. A QUICK PATTERN EXAMPLE2.4.1. Refactoring to Principles2.4.1.1. The Dependency Inversion Principle2.4.1.2. The Dependency Injection Principle2.4.2. Refactoring to the Adapter Pattern2.4.3. Leveraging Enterprise Patterns2.4.3.1. Null Object Pattern2.5. SUMMARY
II. The Anatomy of an ASP.NET Application: Learning and Applying Patterns

3. Layering Your Application and Separating Your Concerns
3.1. APPLICATION ARCHITECTURE AND DESIGN3.1.1. Antipattern — Smart UI3.1.2. Separating Your Concerns3.1.2.1. Business Layer3.1.2.2. Service Layer3.1.2.3. Data Access Layer3.1.2.4. Presentation Layer3.1.2.5. User Experience Layer3.2. SUMMARY
4. The Business Logic Layer: Organization
4.1. UNDERSTANDING BUSINESS ORGANIZATIONAL PATTERNS4.1.1. Transaction Script4.1.2. Active Record4.1.3. Domain Model4.1.3.1. POCO and PI4.1.3.2. Code Example4.1.4. Anemic Domain Model4.1.5. Domain-Driven Design4.1.5.1. The Ubiquitous Language4.1.5.2. Entities4.1.5.3. Value Objects4.1.5.4. Aggregates and Aggregate Roots4.1.5.5. Domain Services4.1.5.6. Application Services4.1.5.7. Repository4.1.5.8. Layering4.2. SUMMARY
5. The Business Logic Layer: Patterns
5.1. LEVERAGING DESIGN PATTERNS5.1.1. Factory Method5.1.1.1. Intent5.1.1.2. UML5.1.1.3. Code Example5.1.2. Decorator5.1.2.1. Intent5.1.2.2. UML5.1.2.3. Code Example5.1.3. Template Method5.1.3.1. Intent5.1.3.2. UML5.1.3.3. Code Example5.1.4. State Pattern5.1.4.1. Intent5.1.4.2. UML5.1.4.3. Code Example5.1.5. Strategy5.1.5.1. Intent5.1.5.2. UML5.1.5.3. Code Example5.2. LEVERAGING ENTERPRISE PATTERNS5.2.1. Specification Pattern5.2.1.1. Intent5.2.1.2. Code Example5.2.2. Composite Pattern5.2.2.1. Intent5.2.2.2. UML5.2.2.3. Code Example5.2.3. Layer Supertype Pattern5.2.3.1. Intent5.2.3.2. Code Example5.3. APPLYING DESIGN PRINCIPLES5.3.1. Dependency Inversion Principle and the Dependency Injection Pattern5.3.1.1. Intent5.3.1.2. Code Example5.3.2. Interface Segregation Principle5.3.2.1. Intent5.3.2.2. Code Example5.3.3. Liskov Substitution Principle5.3.3.1. Intent5.3.3.2. Code Example5.4. SUMMARY
6. The Service Layer
6.1. DESCRIBING THE SERVICE LAYER6.1.1. Service Oriented Architecture6.1.2. Four Tenets of SOA6.1.2.1. Boundaries Are Explicit6.1.2.2. Services Are Autonomous6.1.2.3. Services Share Schema and Contract, Not Class6.1.2.4. Service Compatibility Is Based on Policy6.1.3. The Facade Design Pattern6.1.3.1. Intent6.1.3.2. UML6.2. LEVERAGING MESSAGING PATTERNS6.2.1. The Document Message and the Request-Response Patterns6.2.2. The Reservation Pattern6.2.3. The Idempotent Pattern6.3. AN SOA EXAMPLE6.3.1. Domain Model and Repository6.3.2. Service Layer6.3.3. Client Proxy6.3.4. Client6.4. SUMMARY
7. The Data Access Layer
7.1. DESCRIBING THE DAL7.2. DATA ACCESS STRATEGIES7.2.1. The Repository Pattern7.2.2. Data Access Objects Pattern7.3. PATTERNS IN DATA ACCESS7.3.1. Unit of Work7.3.2. Data Concurrency Control7.3.3. Lazy Loading and the Proxy Pattern7.3.3.1. Intent7.3.3.2. UML7.3.3.3. Code Example7.3.4. Identity Map7.3.5. Query Object Pattern7.4. USING AN OBJECT RELATIONAL MAPPER7.4.1. NHibernate7.4.2. MS Entity Framework7.4.3. ORM Code Example7.4.3.1. Library Domain Model7.4.3.2. The Service Layer7.4.3.3. Database7.4.3.4. NHibernate Repository7.4.3.5. Entity Framework Repository7.4.3.6. Presentation7.4.3.7. Raw ADO.NET Repository7.5. SUMMARY
8. The Presentation Layer
8.1. INVERSION OF CONTROL8.1.1. Factory Design Pattern8.1.2. Service Locator8.1.3. IoC Containers8.1.3.1. StructureMap8.2. MODEL-VIEW-PRESENTER8.2.1. ASP.NET Web Forms with MVP8.3. FRONT CONTROLLER8.3.1. Command Pattern8.3.1.1. Intent8.3.1.2. UML8.3.1.3. Code Example8.3.2. Chain of Responsibility Pattern8.3.2.1. Intent8.3.2.2. UML8.3.2.3. Code Example8.4. MODEL-VIEW-CONTROLLER8.4.1. ViewModel Pattern8.4.2. The ASP.NET MVC Framework8.4.2.1. Mapping ViewModels with AutoMapper8.4.3. Castle MonoRail8.5. PAGE CONTROLLER8.6. SUMMARY
9. The User Experience Layer
9.1. WHAT IS AJAX?9.2. USING JAVASCRIPT LIBRARIES9.3. UNDERSTANDING AJAX PATTERNS9.3.1. Periodic Refresh and Timeout9.3.1.1. Periodic Refresh and Timeout Pattern Code Example9.3.1.2. Periodic Refresh Implementation Script9.3.1.3. Timeout Pattern Implementation Script9.3.1.4. Using Firefox and Firebug for Web Development9.3.2. Unique URL9.3.3. Databinding with JavaScript Templates9.3.3.1. History and Templates Code Example9.3.4. Predictive Fetch9.3.4.1. Predictive Fetch Code Example9.4. SUMMARY
III. Case Study: The Online E-Commerce Store
10. Requirements and Infrastructure
10.1. AGATHA'S CLOTHING STORE REQUIREMENTS10.1.1. Product Catalog and Basket Screens10.1.2. Customer Account Screens10.1.3. Checkout Screens10.1.4. Caching and Logging10.2. ARCHITECTURE10.2.1. Setting Up the Supporting Infrastructure10.2.1.1. Domain Layer Supertype10.2.1.2. Unit of Work Pattern10.2.1.3. Query Object Pattern10.2.1.4. Application Configuration Settings10.2.1.5. Logging10.2.1.6. E-Mail Service10.2.1.7. Helper Classes10.3. SUMMARY
11. Creating The Product Catalog
11.1. CREATING THE PRODUCT CATALOG11.1.1. Product Catalog Model11.1.2. Product Catalog Data Tables11.1.3. Product Catalog Repositories11.1.4. Product Services11.1.4.1. Product Views11.1.4.2. ProductCatalogService11.1.5. Controllers11.1.6. Product Catalog Views11.1.7. Setting Up IoC11.2. SUMMARY
12. Implementing the Shopping Basket
12.1. IMPLEMENTING THE BASKET12.1.1. Basket Domain Model12.1.2. Create the Basket Tables12.1.3. NHibernate Mapping12.1.4. Basket Service12.1.5. Basket Controller and Basket Views12.2. SUMMARY
13. Customer Membership
13.1. CUSTOMER MEMBERSHIP13.1.1. Customer Model13.1.2. Customer Data Tables13.1.3. Customer NHibernate Mappings13.1.4. Customer Service13.1.5. Authentication Service13.1.5.1. Local Authentication with ASP.NET Membership13.1.5.2. Web-Based Authentication with Janrain13.1.5.3. Authentication Cookie13.1.6. Customer Controller13.1.7. Account Controllers13.1.8. Customer Membership Views13.1.9. Authentication Views13.2. SUMMARY
14. Ordering and Payment
14.1. CHECKOUT14.1.1. Order Model14.1.2. Order Data Tables14.1.3. Order NHibernate Mappings14.1.4. Order Service14.1.5. Taking Payment with PayPal14.1.6. Order, Payment, and Checkout Controllers14.1.7. Order and Checkout Views14.2. SUMMARY

Content preview from Professional ASP.NET Design Patterns

INTRODUCTION

THIS BOOK 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.

WHO THIS BOOK IS FOR

This book 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.

WHAT THIS BOOK COVERS

This book covers ...

Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.

Read now

Unlock full access

More than 5,000 organizations count on O’Reilly

O’Reilly covers everything we've got, with content to help us build a world-class technology community, upgrade the capabilities and competencies of our teams, and improve overall team performance as well as their engagement.

Julian F.

Head of Cybersecurity

I wanted to learn C and C++, but it didn't click for me until I picked up an O'Reilly book. When I went on the O’Reilly platform, I was astonished to find all the books there, plus live events and sandboxes so you could play around with the technology.

Addison B.

Field Engineer

I’ve been on the O’Reilly platform for more than eight years. I use a couple of learning platforms, but I'm on O'Reilly more than anybody else. When you're there, you start learning. I'm never disappointed.

Amir M.

Data Platform Tech Lead

I'm always learning. So when I got on to O'Reilly, I was like a kid in a candy store. There are playlists. There are answers. There's on-demand training. It's worth its weight in gold, in terms of what it allows me to do.

Mark W.

Embedded Software Engineer

Beginning SOLID Principles and Design Patterns for ASP.NET Developers

Publisher Resources

ISBN: 9780470292785Purchase book

Cloud Computing

Data Engineering

Data Science

AI & ML

Programming Languages

Software Architecture

IT/Ops

Security

Design