Welcome to WindowsClient.net | Sign in | Join

Rob Relyea - XAMLified

WPF, Silverlight and XAML

Cider/Blend/Other tools – Please don’t hardcode knowledge of “WindowsBase.dll” for XAML component model attributes, etc…

In the Beta2 of .NET 4, we’re working on type forwarding several types from WindowsBase.dll to System.Xaml.dll. WindowsBase will have a dependency on System.Xaml.  System.Xaml will no longer depend on WindowsBase.

On Friday we discovered some issues with Cider/Blend that we’ll have to work with those teams to resolve.

My guess is that these 2 tools have needed to differentiate between Silverlight and .NET’s ContentPropertyAttribute…and have probably moved to use the full name of the type.

Unfortunately, full name comparisons don’t respect TypeForwardedToAttributes.

Published Saturday, May 30, 2009 8:15 AM by Rob_Relyea
Filed under:

Comments

# Dew Drop - May 31, 2009 | Alvin Ashcraft's Morning Dew@ Sunday, May 31, 2009 8:34 AM

Pingback from  Dew Drop - May 31, 2009 | Alvin Ashcraft's Morning Dew

# re: Cider/Blend/Other tools – Please don’t hardcode knowledge of “WindowsBase.dll” for XAML component model attributes, etc…@ Tuesday, July 21, 2009 10:39 AM

Turns out this whole change has been made now. There were several "lists" of framework assemblies that System.Xaml.dll needed to be added to in Cider/Blend/elsewhere and many other changes as well.

Leave a Comment

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