MyXaml Is Not A Microsoft XAML Clone
Just to be clear, Marc Clifton’s MyXaml framework for adding a declarative UI mark-up language to today’s .NET framework is not a clone/sub-set of Microsoft’s XAML or Avalon targeted at Longhorn. In other words, while MyXaml provides a number of the benefits of declarative UI mark-up for building smart/rich clients today, MyXaml is not a way to write WinForms code today that will seamlessly turn into Avalon code tomorrow.
The reason I mention this is because I’ve seen some folks get a bit confused by the use of “Xaml” in the name (Marc is using XAML as the generic Extensible Application Mark-up Language and not as related to Microsoft’s XAML).
On the other hand, there are two other projects that are aiming to clone/sub-set XAML/Avalon on .NET today: Xamlon and Mobiform’s XAML products. I can’t claim that either of these will actually help you transition to Longhorn when it comes along, but I know that Xamlon’s XAML samples work with minor tweaks on their parser and on the WinHEC build of Longhorn.