inotifypropertychanged

I'm coming from developing WPF solutions where to update all properties of the viewmodel was as simple as: OnPropertyChanged(String.Empty); In the Universal Windows Platform scenario, I just have the same method to update/refresh the properties. This works fine in most of cases but sometimes it raise an error something like this: COMException Error HRESULT E_FAIL has been returned from a call to a COM component. at System.ComponentModel.PropertyChangedEventHandler.Invoke(Object sender, PropertyChangedEventArgs e) at GeekyTool.Base.BindableBase.OnPropertyChanged(String propertyName) at Pooo.set

I'd like to implent the System.ComponentModel.INotifyPropertyChanged interface for a property on a base class, but I'm not quite sure how to hook it up. Here's the signature for the property I'd like to get notifications for: public abstract bool HasChanged(); And my code in the base class for handling the change: public event System.ComponentModel.PropertyChangedEventHandler PropertyChanged; private void OnPropertyChanged(String info) { PropertyChangedEventHandler handler = PropertyChanged; if (handler != null) { handler(this, new PropertyChangedEventArgs(info)); } } How do I handle the

I want to get rid of the space consuming and repetitive RaisePropertyChanged-Properties on my model classes. I want my model class... public class ProductWorkItem : NotificationObject { private string name; public string Name { get { return name; } set { if (value == name) return; name = value; RaisePropertyChanged(() => Name); } } private string description; public string Description { get { return description; } set { if (value == description) return; description = value; RaisePropertyChanged(() => Description); } } private string brand; public string Brand { get { return brand; } set { if

I'm writing an extension method for ObservableCollection and have read that the .Add function raises 3 property changed events per call, So that something like this is a bad idea: public static void AddRange<T>(this ObservableCollection<T> oc, IEnumerable<T> collection) { if (collection == null) { throw new ArgumentNullException("collection"); } foreach (var i in collection) { oc.Add(i); } } Are there any other solutions to this? Given that Concat<T> is an extension method it is almost certainly just calling .Add() under the covers, it can't have internal knowledge of the class. You could use

I have a WPF form with a combobox and a textbox (both are databound to an Object's property). Changing the combobox or textbox input updates the Object's property and the databinding kicks in and updates the UI. The problem is, I implemented a way to cancel the change, which works, but screws up the UI updating. If I make the change from the combobox and cancel it, the combobox does not revert the selectedvalue back to what it should be (bound by the object's value). If I make the change from the textbox and cancel it, both the textbox and the combobox show the proper data, but then focus is

I appear to be having serious problems getting my WPF UI to update when I update when I update the property it is bound to. Here is my view model class definition: namespace WpfModel { class AppModel : INotifyPropertyChanged { private int _count = 7; public int Count { get { return _count; } set { _count = value; OnPropertyChanged("Count"); } } public void Increment() { Count++; } public event PropertyChangedEventHandler PropertyChanged; private void OnPropertyChanged(string prop) { PropertyChangedEventHandler handler = this.PropertyChanged; if (handler != null) { var e = new