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

An asynchronous logger


Logging and Audit trail is an important cross-cutting or horizontal concern in the day-to-day application that we create. There are various third-party tools that we leverage; and we have seen how to write one ourselves in depth in Chapter 3, A Logging Library. Here, we will see how to impart reactive behavior to a custom-logging component.

We will use the same spell checker example in the preceding section and see how to integrate logging capability into the existing code base.

We will start off by initializing the log collection as a BindingList, the same way we got the corrections/suggestions initialized:

    class SpellCheckerViewModel : INotifyPropertyChanged 
    { 
        private BindingList<string> _logs;

        private ISubject<string> _logChanged; 
        public BindingList<string> Logs 
        { 
          get 
          { 
             return this._logs; 
          } 
 
        ...