Chapter II How to Compile the LONGHORN Program
For classic Make files, I have never tried to understand - too ancient syntax. Of course, the monsters and difficulties for Make syntax are finally standing, that is, Ant - simple structure using XML is easy to make various relationships. Because ANT was originally based on Java development, some people have developed a .NET version of NANT. However, according to Microsoft's consistent style, it is certainly not a collection, but also to engage in it, not only completely imitated, but also a little innovation (manufacturing your own advantages and standards).
Ok, Microsoft's stuff is MSBuild. Since it is similar to Ant, there is nothing to introduce. Let's continue reading.
Chapter III Control and XAML
You can take XAML to the HTML, but XAML goes more step by step. First, using XAML's object with the program language, if the object used by C # is exactly the same, even the name is the same. This way you don't have to learn two sets of libraries, and the previous use of HTML and ordinary Win32 functions are completely different. This is also because the benefits brought by the .NET platform.
Use XAML this marker language to type, and can be integrated with different tools, and the results of your generated are expressed in XAML, and interoperability has greatly improved.
Using XAML can not only generate normal controls, but even generate simple points, lines, and faces, but also control the brush, painting brush, and coordinate transform ---- It has been possible to complete the work that must be completed by the code before. Here, we have also seen the traces of the W3C SVG and SMIL, but Microsoft is implemented with its own set.
I remember that I have seen the introduction of Microsoft New Interface Programming Interface Avalon, which is completely new, not the old way. Previously, because of the limitations of the memory, in order to complete the rendering, the application had to update the part of the brush down each time the WM_PAIN message. When there is a lot of levels to refresh, it is very troublesome. To achieve a half translucent, the effects such as the irregular window are very troublesome - people who have done this work must have a deep feelings. Ok, now the computer memory has not been, if you don't play games, most of the memory is idle. Now Avalon changes this situation, there is a new way of doing things under the new situation. We can reserve the entire memory for the application, store different levels, and can save (using XAML objects) without bitmap, so that the Siki is not in response to the WM_PAIN message - as long as Generate the entire object model (XAML object model) at the beginning, and the rest is to complete the system automatically! For example, you want to display a web page, generate the entire web page at once, not a different part of the window - there is a lot of people!
There is also a document showing, the text on the window can be adapted according to the resolution, font and window size, etc., the application does not need to intervene. If the text needs to display multiple pages, you don't want to scroll through the scroll bar, allow the system to automatically make paging, then the top of the book page is like a book.
It can be sure that the future application must be as beautiful as the magazine, and the interactive is strong, and it is not much better than Flash.
