This is the best way that I've discovered to implement INotifyPropertyChanged in a XAML based MVVM app without downloading any extra supporting code.It relies on the ref keyword to allow a method in the base class to modify the property that you wish to raise a property changed event for. The code is fairly concise and it doesn't add any unseen overhead.

In your view model all you need to do is:

namespace Nogginbox.MyApp.ViewModels;

public class MyViewModel : ObservableViewModelBase

{

public string Name

{

get => _name;

set => SetProperty(ref _name, value);

} …

The Hitchhiker’s Guide to the Galaxy is perhaps the most remarkable, certainly the most successful book ever to come out of the great publishing corporations of Ursa Minor. It is an indispensable companion to any weary traveller roaming the celestial highways. While providing a huge amount of vital galactic information, it is well known to have a hugely popular word search section to help pass the hours while waiting for the next passing spaceship.Till now this section has never been published or even seen on the mostly harmless planet Earth. So, I was very excited to find a battered and …

Should we write code SOLID? I’ve always liked a bit of single responsibility principal and dependency injection, but don’t often find myself using interface segregation.

Dan North argues that the SOLID Principals are not the be all and end all of good software. On a recent .NET Rocks 1745 he explains what’s wrong with SOLID and puts forward his own set of CUPID Properties. Properties are less strict than principals, but if you write code that has more of these properties then it will be better.

Dan North seems to have plans to write a series of detailed blog posts about the CUPID properties, …