Book Image

.NET Design Patterns

By : Praseed Pai, Shine Xavier
Book Image

.NET Design Patterns

By: Praseed Pai, Shine Xavier

Overview of this book

Knowing about design patterns enables developers to improve their code base, promoting code reuse and making their design more robust. This book focuses on the practical aspects of programming in .NET. You will learn about some of the relevant design patterns (and their application) that are most widely used. We start with classic object-oriented programming (OOP) techniques, evaluate parallel programming and concurrency models, enhance implementations by mixing OOP and functional programming, and finally to the reactive programming model where functional programming and OOP are used in synergy to write better code. Throughout this book, we’ll show you how to deal with architecture/design techniques, GoF patterns, relevant patterns from other catalogs, functional programming, and reactive programming techniques. After reading this book, you will be able to convincingly leverage these design patterns (factory pattern, builder pattern, prototype pattern, adapter pattern, facade pattern, decorator pattern, observer pattern and so on) for your programs. You will also be able to write fluid functional code in .NET that would leverage concurrency and parallelism!
Table of Contents (22 chapters)
.NET Design Patterns
Credits
Foreword
About the Authors
About the Reviewers
www.PacktPub.com
Customer Feedback
Preface

Solutions approach


Before writing the code, let us step back a bit to enumerate the details of the requirements. The library which we are planning to write should have the following:

  • Support for various output formats like HTML, PDF, and so on
  • An object model for storing the contents of the table
  • A unified programming model and API for developers
  • Separate content and it's processing
  • The ability to write new pluggable output processors (drivers)

We will start by creating a hierarchy of elements for storing document contents. A simple hierarchy which has been conceived is as follows:

We will encode our content in a tree-structured document model. For the sake of simplicity, we have reduced the number of document elements. In an industrial strength implementation of this library, we will have many more elements. We can create tables within tables in this scheme, as we allow nested tables. Before we get into the implementation of the aforementioned hierarchy, we will look into the specifics of the...