title: Specifically for a User Control, is there a place after the constructor, but before the Loaded event where you can access properties set in XAML?
body: <p>We have an issue where our user control is initialized based on what the user sets in XAML when utilizing our control.  Currently we were using the 'Loaded' event to act on what the user had set or not.</p>
  
  <p>However, the issue with using the Loaded event is another sibling of this control is using <em>their</em> loaded event to set something on ours, which isn't yet fully initialized since <em>our</em> Loaded event hasn't yet fired.  (It's a UI race condition if you will.)</p>
  
  <p>Again, we can't move our code to the constructor as the WPF system hasn't yet set the properties specified by the XAML of the consumer of our control.  We can't use the Loaded event for the reasons stated above.  Initialized doesn't seem to work either.</p>
  
  <p>I've also looked into ISupportsInitialize, but that's where <em>we</em> would be batch-setting the control's properties, not something externally, so that doesn't seem to be a fit either.</p>
  
  <p>Thoughts?</p>
  
  <h2>Update</h2>
  
  <p>I've since found out this is an anomaly specifically with UserControls.  They handle initialization differently.  You can find more details in my follow-up question here...</p>
  
  <ul>
  <li><a href="https://stackoverflow.com/questions/18583196/how-can-you-initialize-a-usercontrol-based-on-user-set-properties-and-before-loa">How can you access XAML-set properties of a UserControl during initialization?</a></li>
  </ul>
  
  <p>...but the short version is calling InitializeComponent in the constructor actually raises the Initialized event, but does so before the XAML-defined properties have actually been set.  Comment it out and the properties are now set when Initialized fires, but of course your control's UI isn't loaded! Kinda frustrating actually.</p>
  
  <p>Still looking for a solution.  Code examples and more details can be found there.</p>