This post originated from an RSS feed registered with .NET Buzz by Sam Gentile. Original Post: WPF and Two APIs Feed Title: Sam Gentile's Blog Feed URL: http://samgentile.com/blog/Rss.aspx Feed Description: .NET and Software Development from an experienced perspective - .NET/CLR, Rotor, Interop, MC+/C++, COM+, ES, Mac OS X, Extreme Programming and More! Latest .NET Buzz Posts Latest .NET Buzz Posts by Sam Gentile Latest Posts From Sam Gentile's Blog

The master Petzold hits it on the head on what it's been like for me: “The reason? It has two APIs. WPF has a relatively normal object-oriented procedural API for coding with C#, VB, etc, but it also has a parallel XML-based API known as XAML, the Extensible Application Markup Language....One of the things I like about Windows Forms is that everything is done in code, including menus and dialog box layout. You can do a short program — or a whole dialog box in a larger program — entirely in one C# file. This seemed to me a massive improvement over the old Windows API approach of splitting the program between code and resource script...At first I was a little hesitant about embracing a new API that went back to that split between code and script. But the power built into XAML is truly amazing and ultimately converted me. (In the article on Avalon I wrote for MSDN Magazine, I almost wrote that XAML was "a resource script on crystal meth" with the knowledge that the editors would probably change it to "steroids" but I decided that any comparison with the resource script was insulting.) For larger software house and larger applications, it can allow application development to be split effectively between designers and programs.”

All I can say is Amen Brother as this 100% reflects my experiences and growing fondness with XAML.