IsSavable, INotifyPropertyChanged and WPF binding

I fully understand about introducing unknowns into your app. But if you are even trying to use CSLA behind WPF, I really think you want the experimental CSLA .NET 3.0 stuff.

CslaDataProvider: a data provider control that works with CSLA objects

ValidationPanel: provides ErrorProvider-like behaviors in your WPF form

AuthorizationPanel: provides ReadWriteAuthorization-like behaviors in your WPF form

ObjectStatusPanel: exposes the Is___ properties for binding in your form

Without these new controls you won’t be able to get validation or authorization behaviors, or to use the Is___ properties. WPF simply doesn’t offer the capabilities of Windows Forms in terms of validation or bindingsource events, so there are no simple workarounds to do what these new Csla.Wpf controls are doing. (I’ve no doubt that a future version of WPF will at least include an ErrorProvider equivalent – that’s too important for them to ignore for WPF 2.0 – but in the intervening months or years, we need something…)

The CslaDataProvider is purely optional, as you can always set the DataContext through code. But it does offer async loading of data without you having to mess with threading yourself, and that can be nice.

Rocky