Key Technical Analysis of WPF architecture (1)-Preface

The development of technology is actually traceable. no matter how advanced or mysterious the technology is, it is in practice-> experience-> theory-> practice->... in the process of development. The reason why I wrote this series of articles today is not to show off how many cows I have. Of course, it is not to pretend to be B. I still have the self-knowledge of "days outside, people out of the world. My purpose is actually very simple:
1) I have learned and applied Silverlight over the past two months to commemorate my youth;
2) I would like to share some experience with new and old comrades who are involved in or preparing to get involved in Silverlight and WPF development, through such communication, we can reduce the cost (time and energy) we spend on technical tracking, and spend more time doing more meaningful things, such as spending more time with family members;
3) If you are improving your communication skills, you can also take a look at the real ghosts and fake devils who like to use the concept of playing to fool us (I have always felt that our country's software is lagging behind, it is not because our coder's IQ is not enough, but because of information asymmetry, impetuous social reality and distribution system. Of course, this is a reality. I did not write this series to attack this, we still learn our technologies and earn more money to support our family );
Of course, it is also a very important purpose for us to improve our communication. Therefore, I also hope that you will give us some advice on what I have written, I will not sell books, so you don't have to worry that I will sell money with your wisdom.
This series mainly involves the XAML, reflection mechanism, class serialization, dependency attributes, additional attributes, behaviors, triggers, command and other features related to WPF, the implementation principles, mechanisms, and history of these features are discussed to gain a deeper understanding of the WPF, Silverlight, and mvvm modes. Of course, here is not a redo of WPF. I neither have this strength nor energy, nor need it. We can simply use these technologies through analysis of principles.

For better communication, you still need to have a basic understanding of XML, reflection, serialization, attributes, events, delegation, and other concepts when reading this series, if you have a better understanding of the command mode (some called the behavior mode) and observer mode (I have related content in the previous blog ). I would like to thank the comrades who have explored the road here for their great help in learning these technologies. I would also like to share this document with these road drivers.

In addition, since I have to write these articles in my spare time, I hope you will not demand my progress. I will do my best to complete this series.

Below is a rough outline:
1) serialization of classes and XAML of UI elements
2) page rendering and interaction logic
3) Dependency attributes and additional attributes
4) command Implementation Mechanism
5) behaviors, triggers Implementation Mechanism

Note: In the past, the question was a little big. I tried to write it and I never felt that I couldn't write what I was trying to express. So I gave up, but it was better to directly write the code.