inotifypropertychanged

Do folks have any guidance on when a simple .NET property that fires INotifyPropertyChanged.PropertyChanged is sufficient in a view model? Then when do you want to move up to a full blown dependency property? Or are the DPs intended primarily for views? Lukasz Madon There are a few approaches: 1. The dependency property While you using the dependency property it makes the most sense in elements-classes that have a visual appearance ( UIElement s). Pros: WPF do the logic stuff for you Some mechanism like animation use only dependency property 'Fits' ViewModel style Cons: You need to derive form

Does anyone know if BindableBase is still a viable or should we stick with INotifyChanged events? It seems like BindableBase has lost its luster quickly. Thanks for any info you can provide. Rohit INotifyPropertyChanged The ViewModel should implement the INotifyPropertyChanged interface and should raise it whenever the propertychanges public class MyViewModel : INotifyPropertyChanged { private string _firstName; public event PropertyChangedEventHandler PropertyChanged; public string FirstName { get { return _firstName; } set { if (_firstName == value) return; _firstName = value;

Possible Duplicate: typesafe NotifyPropertyChanged using linq expressions I'm working on a large team application which is suffering from heavy use of magic strings in the form of NotifyPropertyChanged("PropertyName") , - the standard implementation when consulting Microsoft. We're also suffering from a great number of misnamed properties (working with an object model for a computation module that has hundreds of stored calculated properties) - all of which are bound to the UI. My team experiences many bugs related to property name changes leading to incorrect magic strings and breaking

I'm looking for a clean and elegant solution to handle the INotifyPropertyChanged event of nested (child) objects. Example code: public class Person : INotifyPropertyChanged { private string _firstName; private int _age; private Person _bestFriend; public string FirstName { get { return _firstName; } set { // Short implementation for simplicity reasons _firstName = value; RaisePropertyChanged("FirstName"); } } public int Age { get { return _age; } set { // Short implementation for simplicity reasons _age = value; RaisePropertyChanged("Age"); } } public Person BestFriend { get { return

I know that there are solutions out there for implementing INotifyPropertyChanged, but none of them are as simple as: reference this library, create/add this attribute, done (I'm thinking Aspect-Oriented Programming here). Does anyone know of a really simple way to do this? Bonus points if the solution is free. Here are some relevant links (none of which provide a simple enough answer): Aspect Examples (INotifyPropertyChanged via aspects) LinFu INotifyPropertyChanged auto wiring or how to get rid of redundant code INotifyPropertyChanged With Unity Interception AOP Try this https://github.com

Form Build your own MVVM I have the following code that lets us have typesafe NotifyOfPropertyChange calls: public void NotifyOfPropertyChange<TProperty>(Expression<Func<TProperty>> property) { var lambda = (LambdaExpression)property; MemberExpression memberExpression; if (lambda.Body is UnaryExpression) { var unaryExpression = (UnaryExpression)lambda.Body; memberExpression = (MemberExpression)unaryExpression.Operand; } else memberExpression = (MemberExpression)lambda.Body; NotifyOfPropertyChange(memberExpression.Member.Name); } How does this approach compare to standard simple strings