Hello, turbocode, you wrote: S>> But all for this purpose was. Then and WPF that only did the first steps. And WinMo was cut down OS. The same WinForms S>> But they decided to throw and create the new. A problem only in it. S>> if developed WPF for WinMo it it would be much more effective. S>> it is simple WPF for mobile devices much more effectively. T> at first GUI the operating system it was necessary to translate on DirectX, and then already to think about WPF. And what such GUI the operating system? Is WinForms which works over Win32 API Is WPF and XAML analogs use DirectX T> But also it I think would be not enough because all these message queues were the main brake in Windows always. T> Voobshchem MS got to a hole which itself when that and dug out (when multimedias (DirectX) and a desktop divided development (GDI) separately). WPF it just and multimedia and . Simply WinForms and WPF for exist and to this day. There the problem that WPF has been oriented on DirectX 11 while Adreno was DirectX 9.0c With an output of a. net Framework 3.0 Microsofts is faster let out new API for drawing of user interfaces: Windows Presentation Foundation which was based on DirectX 11 and declarative language of the description of interfaces XAML. However, even despite all it, Windows Forms and WPF still offer similar functionality and consequently Windows Forms has not been abolished in favor of WPF, and it continues to be used as alternative technology of creation of interfaces along with WPF. Answering questions at conference Build 2014, Microsoft explained that Windows Forms it will be supported, errors will be corrected, but new functions will not be added. Later, the refined support of high resolution for various elements of interface Windows Forms nevertheless has been announced in release of a. net Framework 4.5.