I\'ve started using the XmlnsDefinition attribute to tie together some CLR namespaces into a single xmlns for convenience in XAML.
Unfortunately, it seems that this
Unfortunately, no. The XAML file must be parsed before the assembly is built in order to generate the code implied by the XAML to be included in the assembly. The XAML compiler produces code behind files (the files ending in, for example, .g.cs) and these file then become part of the assembly the XAML file is contained in. Since the assembly hasn't been built yet, the XAML compiler cannot load it to determine XmlnsDeclaration attributes have been specified.
Use clr-namespace
instead. For example:
xmlns:controls="clr-namespace:Rhapsody.UI.Main.Controls