What's new in XAML?
I've spend the large part of this morning threatening my persistently bleeding nose. Occasionally this pops up. Left over from years of cycling. I made it on time for the XAML talk.
XAML lets you say what you want without saying how to do it. This is also referred to as declaring your intent. XAML can be used to create declarative models a simple file format for object-based systems.
Benefits of designing for XAML:
- XML reading/writing
- Markup==OM
- Consistency with .NET
- Human readable XML
- Easier to tool
- Even-based programming model
- Ride the XAML wave
Microsoft is investing in XAML in many place. Oslo is a great example with it's importing and exporting XAML capabilities in the repository.
State of XAML in 2008
- UI
- Workflow
- Electronic paper
- Runtime: .NET 3.0 & 3.5; silverlight1 & 2
- Tools: VS 2008 (WPF + WF designer and XAML editor), expression blend
- XAML specifications published
Customers need more language evolution, make it faster, fundamentals of XAML/BAML need continued investment (compilation, debugging, obfuscation, localization, FxCop, VS integration, and more). There also the need to model more domains in XAML.
What's new in XAML 2009
In .NET 4.0 XAML will be easier to author application declaratively and feature a more rich vocabulary.
- Better name references (<Label target="firstNameBox">First Name<Label>)
- Build in types (Most of the CLR types have an XAML equivalent.)
- Support for generic types directly in XAML
- Arbitrary dictionary key types
- Beyond method names (Button Click="{DelegateCreatingME Foo}" />
- Better declarative type offering
- Use non-default constructors
- Use static factory methods
System.Xaml.dll in .NET 4.0 and will hit the street in the November 2008 CTP.