Welcome to WindowsClient.net | Sign in | Join

Rob Relyea - XAMLified

WPF, Silverlight and Xaml

DomBox

Yesterday we did an API / conceptual model review with Mike Hillberg and John Gossman from WPF/Silverlight and Chris Anderson and Don Box from WCF/WF/etc…

We got a bunch of great feedback…and we’ve only made it through half the deck we had prepared.

To say thanks, I really should take them to lunch after the PDC.  Until then, to recognize the value of their feedback, I’m renaming a control in my PDC demo code from XamlNodeBox to DomBox.  :-)

Published Wednesday, October 08, 2008 4:25 AM by Rob_Relyea
Filed under:

Comments

# re: DomBox@ Wednesday, October 08, 2008 3:32 PM

I hope one of the things you are adding support in the new xaml API is conditional compilation.  Right now I am porting my WPF application to Silverlight.  I basically has to chuck away my whole xaml file and start again for Silverlight.  This is extraordinarily frustrating.  Obviously as Silverlight improves this will become less of a concern, but it appears to me there will still be pieces of the xaml that will not be compatible.

It seems to me to be very helpful if I could specify a #if SILVERLIGHT section in the xaml.  I could then use this to exclude attributes like SnapsToDevicePixels (goodness knows why they decided to create an entirely different way of specifying the same thing for Silverlight).

...Stefan

by Stefan Olson

# re: DomBox@ Wednesday, October 08, 2008 11:45 PM

Stefan-

Look at the markup compatiblity namespace. SL only support mc:Ignorable part of it so far, but it may help you.  the trick is to use an xmlns that silverlight doesn't support to refer to things they can't do.

With mc:Ignorable and mc:AlternateContent, you should be able to get this going...

Thanks, Rob

by Rob_Relyea

Leave a Comment

(required) 
(required) 
(optional)
(required) 
Page view counter