Design Patterns: Solidify Your C # Application Arch

Design Patterns: Solidify Your C # Application Architecture with Design Patterns Chinese edition (Part 1) optimizer)

Keyword Design Pattern singleton strategy decorator composite state

Source http://msdn.microsoft.com/library/default.asp? Url =/library/en-us/dnmag01/html/PATTERNS. asp

Design Patterns: Solidify Your C # Application Architecture with Design Patterns Chinese edition (Part 1)
Author: Samir Bajaj
Translator: glory
[Translation: C # advanced article. The translator simply sorts out the C # examples provided by Samir (some of the Code provided by the author cannot be compiled in the translator's environment) and compiles the corresponding C ++ example, put them in comments for readers to compare. All C # And C ++ debugging environments are Microsoft Visual Studio. NET 7.0 Beta2]
[Summary: by providing a framework, design patterns can solve many problems in application development. The pattern makes the design process clearer and more efficient. It is especially suitable for C # program development because C # is an object-oriented language. Because the origin and starting point of the design model is to describe object-oriented (reusable) software design.] The existing design model provides an excellent template for your own class design, the usage mode can shorten the software development cycle. This article describes several popular design patterns, including singleton, strategy, decorator, composite, and state. You can use them in your own applications to improve application scalability, and makes the class easier to reuse.]
As any sophisticated object-oriented software developer knows, it is incredible to discuss the software design architecture without a minimum understanding of the design patterns. If not all, most software applications, tools, and systems use at least one or more design patterns. The design pattern is a description of a set of interacting classes that provide a framework for solving general problems in a specific context. In other words, the pattern provides a solution for specific problems in object-oriented software development. In addition, patterns generally focus on constraints and other factors that limit their adaptation to solutions. The connection and communication between classes and context details define a mode, it provides a solution for any problem that matches the characteristics and necessary conditions in the object-oriented software design.
I must admit that I am an enthusiastic supporter of design patterns. Since I have read the Creative Book Design Patterns co-authored by Gamma, Helm, Johnson, and Vlissides, I have rarely designed software without any patterns. In fact, I spent a considerable amount of time in the early stages of software design to determine a pattern that would naturally fit the future architecture. After all, the model is a solution to some problems that have been tested by time and application fields. Those problems have been solved by experienced designers, developers, and language experts. It is wise for anyone who is performing software design to make good use of the knowledge and expert experience that can be used. It is often a good idea to use a solution that has been proven to be successful over and over again, rather than creating a new one from the hair.