Question

I have a user control where the XAML of the control can bind to the appropriate properties from the parent’s data context like normal (the data context propagates in xaml).

For example, I have a window whose DataContext I am setting to ObjectA for example. My user control within the window is then try to access the properties within the dataContext

So my window’s xaml and code behind can both see a non-null DataContext.

My control that DataContext propagates to can see a non-null DataContext in the Xaml but not in the code behind.

What is the proper way of handling this?

Answer 1

failing that if you need to check whether the DataContext is being set you can use the DataContextChanged

public partial class UserControl1 : UserControl {     public UserControl1()     {         InitializeComponent();          DataContextChanged += new DependencyPropertyChangedEventHandler(UserControl1_DataContextChanged);     }      void UserControl1_DataContextChanged(object sender, DependencyPropertyChangedEventArgs e)     {         // You can also validate the data going into the DataContext using the event args     } } 

Note it wont enter UserControl1_DataContextChanged until DataContext is changed from null to a different value.

Not sure if this answers your question but can be quite handy to use in debugging issues.