BamlParser does not correctly handle attached properties with namespace prefix (?)


I have an element in my XAML with an attached property defined in my own code:
<SomeElement l:Attached.Property="foo"/>
The namespace prefix "l" is of course mapped to the .NET namespace where the attached property is defined.
When i try to parse the BAML stored in the assembly resource (using BamlTranslator), the result is
<SomeElement Property="foo"/>
that is, the namespace prefix and the part on the left-hand side of the dot is missing.


sisnaz wrote Apr 22, 2010 at 6:04 PM

Yeah, the Baml Viewer is jacked for the 3.5 and 4.0 framework. It doesn't appear to have been updated for a few years now. It does ok for the most part, but the namespaces are all over the place. The template bindings is another problem I'm finding. It's a great tool, hopefully they will update it soon.

wrote Apr 22, 2010 at 6:13 PM

OzgurDunyam wrote Jul 24, 2010 at 7:37 PM

<a title='Sesli Sohbet' href='http://www.ozgurdunyam.com'>Sesli Sohbet</a>

wrote Oct 27, 2010 at 12:41 PM

wrote Feb 22, 2013 at 12:03 AM