Design Pattern in. NET Framework

I have read the design model since I did not study it for the first time. But at that time, the design model was just a fantasy. I don't know why I want to use these models, but I think it is more troublesome, after two years of work, I feel a little bit new, but I am stuck in endless scenarios. I want to imagine that I am in a scenario, and then I have various requirements. Then I can implement it in a certain mode, 2/3 of the time is wandering around these assumptions. I accidentally saw this article on msdn.ArticleDiscover the design patterns you're already using in. net Framework. net has a design pattern, and some are even familiar with it, but we are a customer and do not need to understand its implementation, we suddenly think that this way of learning design patterns can jump out of the imagination of the scene, we are too familiar with these scenes.

I searched the internet, and many netizens found this and wrote many blogs ([Called]. the design patterns in the basic class libraries of Net Framework, the common design patterns in dot net frameworks, design & pattern). I will not list them one by one, however, it seems that you haven't written any more after just listing or writing a few articles. Therefore, I want to write some simple understandings of myself on this idea, because there will certainly be many mistakes soon, I hope you will give me more advice.

 

Application policy mode: List <t> sorting