XAML in .NET 4 Update
Random news on the .NET4/XAML/BAML front…builds more info on top of last month’s XAML State of the Union
Localization
- Doing WPF Localization review internally today…
- Separately talking with Silverlight, Blend, Cider…on how WPF/Silverlight should both Localize. Any feedback on Silverlight’s Loc model…and what you’d like to see there???
- Met with Windows Build lab recently to discuss getting WPF localization working with Windows’ localization process. Currently it fails due to delay signed assemblies and “LocBamls” reliance on Assembly.Load().
BAML
- We are doing a bunch of Perf optimizations in Baml2006Reader which is making its XAML node stream much less useful for analysis… We aren’t sure if our first Beta will have a BamlReaderAsText mode enabled or not. Trying to make it happen… Want to see FxCop/etc… scenarios enabled early in release to get feedback.
Performance
- We are making steady progress getting Baml to Object scenarios on par with v3. Still not all the way there yet. We may even adapt the BAML format in v4 (or a known types table in PF.dll) a bit to get optimizations that we now need due to new features that Types can tap into. (The old parser used to hard code many things…now that we’ve made those opt in for any type, we currently have to check many types and properties to see if they have opted in.)
- Our tallest dev is looking to see how multithreading a BAML load could speed things up some more. We’ve been discussing this option for a while. Application.LoadComponent craziness won’t make it easy…
Compatibility