Basically, I remember that there was a time when you could use the following: <?Mapping ... >(it looks like it no longer works - maybe outdated?)
I know that I can map my XML namespaces like this ...
xmlns:xyzcon="clr-namespace:XYZ.Wpf.Controls"
xmlns:xyzcom="clr-namespace:XYZ.Wpf.Commands"
But I also know that I can map my XML namespaces this way (much cleaner)
[assembly: XmlnsPrefix("http://schemas.mycompany.com/netfx/xaml/presentation", "xyz")]
[assembly: XmlnsDefinition("http://schemas.mycompany.com/netfx/xaml/presentation", "XYZ.Wpf.Controls")]
[assembly: XmlnsDefinition("http://schemas.mycompany.com/netfx/xaml/presentation", "XYZ.Wpf.Commands")]
which makes it very easy to use, because instead of it there is a prefix l, lv, etc., I can have all my spaces in CLR names in one XML namespace ...
xmlns:xyz="http://schemas.mycompany.com/netfx/xaml/presentation"
This line gives me access to XYZ.Wpf.Controls and XYZ.Wpf.Commands. The problem is that this only works if the assembly is already compiled. I can not use this trick when working in the same assembly.
, CLR SAME XML ( , XML). ?