I have done some work similar to defining interfaces using XML before, so I came to the question: How did Microsoft solve the problems I encountered?
The most important thing about WPF is The XAML language. The book is also centered on this (this is very important ). Soon after the beginning, I explained some key questions in XAML, such as property elements and Type converters. I have read some articles about WPF before, and I am amazed at the flexibility of XAML-Why can this definition be done. It is difficult to continue without solving these questions. I like the writing style of the author very much. It's not easy for you to take complicated things out. Just ask why, the author will give an explanation right away-as if you understand your mind, it's so cute.
XAML is not intended for users, but for the convenience of creation tools. Once you understand this, you will understand why the code can be implemented and must be written in XAML. With the same implementation, the author will first give the implementation of XAML, and then implement the C # code. The XAML is so powerful that we will find that the same effect is more concise and clear in the XAML writing. The use of data binding makes it possible to write a simple RSS reader completely in XAML.
After learning about WPF, you will have a deep understanding of Declarative Programming. However, in terms of implementation ideas, WPF also has a lot to learn from and play. Even if you have no chance to use it, it is worthwhile to learn how to broaden your thinking.
This book introduces all aspects of WPF, from basic concepts to advanced applications, over six hundred pages. It is unrealistic to read the last few chapters in one breath. You can read the previous chapters carefully to understand how WPF works and what it can do. Basic Development is enough. More advanced knowledge is needed.