Yes, the app was made with the Wpf template. Here's the SetUiAsBusy method: private void SetUiAsBusy() { MasterList.UiIsFree = false; NotifyPropertyChanged_All(); CommandManager.InvalidateRequerySuggested(); } The SetUiAsFree method is the same except it is set to true. The UiIsFree variable is bound to the IsEnabled property of many UI elements. In the method I posted earlier, MasterList.RemoveDirTreeNodeAndChildren(theDirTreeNodeToRemove, true); is where nearly everything happens. Several ObservableCollections are modified (safely as best as I can tell) that are bound to UI elements. No exceptions are getting swallowed and the VS output pane remains empty while the method runs.

How do I bind to Inlines? According to the docs it seems to be read-only. Do I need to switch to a Label or Textbox?

Have a look at Bea's site. This post has what you are looking for: http://www.beacosta.com/blog/?p=17[^] Bea's if the "First Lady" of WPF data binding with many great examples of using the platform. Cheers, Karl » CodeProject 2008 MVP » Microsoft MVP - Client App Dev My Blog | Mole's Home Page | MVP Profile Just a grain of sand on the worlds beaches.

artwallacex wrote: Are there any solutions to just hardcoding a bunch of these NotifyPropertyChanged in every editable field? Since you're using WPF then you'll be using C# 2.0 at least so you could do something like this (just made up an example since I haven't downloaded your files): private TimeSpan _TimeCode; private TimeSpan _TimeCodeCalc; public TimeSpan TimeCode { get { return _TimeCode; } set { _TimeCode = value; TimeCodeCalc = new TimeSpan(value.TotalMinutes); // Change another "readonly" property NotifyPropertyChanged("TimeCode"); } } public TimeSpan TimeCodeCalc { get { return _TimeCodeCalc; } private set { _TimeCodeCalc = value; NotifyPropertyChanged("TimeCodeCalc"); } } You'll notice the private modifier on the TimeCodeCalc property, what this does is that only your class will be able to change the value.  If you wrap your readonly properties like this then at least when you modify them you only have to set the wrapper property and the PropertyChanged event will be fired off.  That way you don't have to remember to fire notify about every property in every place where you set it.  Just use the new private set method rather than the field to modify the value. [edit] I've had a look at your simple solution and modified it to give you an example: http://www.pooredesign.com/downloads/wpf-databinding-calcupdate.zip[^] [/edit]

This means we are having a good day then. :cool: The homework business normally translates to, "please check Google, then post question." Just glad we got you on the right track. Cheers, Karl » CodeProject 2008 MVP » Microsoft MVP - Client App Dev My Blog | Mole's Home Page | MVP Profile Just a grain of sand on the worlds beaches.