Design patterns are basically an experience summary and policy selection process. Developers summarize repeatable design techniques during the development process, forming them, and then apply them in applicable occasions. As a new language, C # draws a lot of advantages that have both technology. And formed some of its own characteristics. Have a form advantage when implementing some modes. Design some class libraries (usually this will be used in a large number of modes), and there are several things that make me satisfied: 1. The visible level in the namespace can be defined. In actual work, I use INTERNAL. Levels and structure, effectively guarantee the level of protection of code; 2, class members can choose a variety of visible levels, and the complete visible hierarchy is very useful when designing the class library It is difficult to imagine if there is no private and protection level constructor, I define strict single-case and factory models; 3, some of the feature grammar can indeed reduce coding, improve development and operation efficiency, such as delegate (it is said to be implemented After compiling, only two lines of IL code, very high efficiency, properties, attribute information (Atribute, this honesty, I haven't used it yet, but I feel very useful when designing the frame) ... we can be in the future. The discussion involves these contents; Master the .NET framework, or can bring a lot of convenience for our work; 5, C # has convenient and practical abnormal protection structure, this may be important in class design (have a complete exception definition ability is more important Let's know that you can use an abnormal technology after you can get effective management. Other technical points have some, here is not explained here, and there is a discussion in discussions. After all, the model itself is a language-independent technology. We discussed only that it is specific in C # applications.
