Lambda the Ultimate

Worse, to do any actual event handling, they actually embed C# into XML, resulting in code like their example:

<Canvas ID="root" xmlns="http://schemas.microsoft.com/2003/xaml" xmlns:def="Definition"> <Button ID="button1" Click="Clicked">Click Me!</Button> <def:Code> <![CDATA void Clicked(object sender, ClickEventArgs args) { button1.Content = "Hello World"; } ]]> </def:Code> </Canvas>

How horrid.

You may want to use XAML without having to learn C#.

The approach seems reasonable. But the resulting language, XMAL, may be horrid. I didn't study it enough to be able to tell at this point if that's the case.

I am certain the integration with C# and assorted tools will be announced RSN...

most common complaint seen there, is the need for css styling for these elements. This also seems related to the complaint, which is mine, that whether or not this has embedded c# it is one ugly markup language, I don't know what it is, microsoft has some really good xml people working for them, but they have this in-house style for a lot of markup that comes out of there that just bugs the hell out of me.

One thing I hate in a markup language is variations in capitalization, because of course xml is case-sensitive.

This can make writing xaml difficult unless one has an editor specifically adapted to writing it, it can also make writing scripts etc. for working with one's xaml files more of a chore, consider the following xpath:

//xa:Canvas[@ID="root"]/xa:Button[following-sibling::def:Code]

now extrapolate to when you want to work with camel-cased objects from an xslt, sax parser, some script using the dom. just a lot of chances for misspellings it seems to me.