XAML Syntax to Declare Instance of Private Class

  • Thread starter Thread starter Jules Winfield
  • Start date Start date
J

Jules Winfield

I'm designing a WPF user control. Within the C# portion of the class is a
private conversion class:

private class MyConverter:IValueConverter{
....
}

Within the XAML portion of the class I'd like to create an instance of this
class:

<UserControl.Resources>
<ResourceDictionary>
....
<aia:MyConverter x:Key="Cvt"/>
</ResourceDictionary>
</UserControl.Resources>

(The namespace "aia", referenced above, is properly defined in myXAML class
definition)

The problem is that somehow my declaration syntax is wrong. I can't seem to
declare an instance of my private MyConverter class in XAML. If I move
MyConverter out of the user control and make it it's own top-level class in
the "aia" namespace, everything compiles properly. So how do I declare an
instance of a private class within XAML?

Jules
 
Hi Jules,

An XAML tag must be the top-level class in a namespace. That's to say, WPF
doesn't support the function you want so far.

The only workaround is to move the MyConverter class out of the user
control and make it a top-level class in the namespace.

If you have any concern, please feel free to let me know.

Sincerely,
Linda Liu
Microsoft Online Community Support

==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications.

Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.
==================================================

This posting is provided "AS IS" with no warranties, and confers no rights.
 
Back
Top