Based on discussion:
http://wpftoolkit.codeplex.com/discussions/403349
The user expressed its need to have a separate Dll that contains classes that could be used on the Business Model side of its code.
The projects containing the business object need to refer to the UI rich, Toolkit's Dll in order to add the "ExpandableAttribute", "ItemsSourceAttribute" and "PropertyOrderAttribute" attributes to it's business object.
Microsoft did such a separation with the System.ComponentObject namespace which is in the System.dll assembly and can be refereed by a "UI less" project (eg. server-side project).
Comments: ** Comment from web user: yourbuddypal **
http://wpftoolkit.codeplex.com/discussions/403349
The user expressed its need to have a separate Dll that contains classes that could be used on the Business Model side of its code.
The projects containing the business object need to refer to the UI rich, Toolkit's Dll in order to add the "ExpandableAttribute", "ItemsSourceAttribute" and "PropertyOrderAttribute" attributes to it's business object.
Microsoft did such a separation with the System.ComponentObject namespace which is in the System.dll assembly and can be refereed by a "UI less" project (eg. server-side project).
Comments: ** Comment from web user: yourbuddypal **
I also vote for this item so that my backing data class doesn't need WPF UI references.