Skip to main content

Improving type safety for INotifyPropertyChanged without expressions

Type safety is important. Isn’t it one of the reasons why you should use a static typed language like C#?  But if you’re using the INotifyPropertyChanged interface, you allready have left that type safety. Why? Because it expects you to pass on the propertyname. Easiest way to do this is just using a string parameter. 

   1:  public event PropertyChangedEventHandler PropertyChanged;
   2:   
   3:      private void NotifyPropertyChanged(String propertyName)
   4:      {
   5:          if (PropertyChanged != null)
   6:          {
   7:              PropertyChanged(this, new PropertyChangedEventArgs(propertyName));
   8:          }
   9:      }


But what if you refactor your code and change the name of the property? The string value will remain the same and the compiler will not warn you. But your code will no longer work.

A solution could be the use of expression to pass on the propertyname in a type safe way. 


   1:  protected void NotifyPropertyChanged(Expression<Func<T,object>> x)   
   2:  {   
   3:          var body = x.Body as MemberExpression;   
   4:          string propertyName =  body.Member.Name;   
   5:             
   6:          if this.PropertyChanged;   != null)   
   7:          {     
   8:              this.PropertyChanged;   (this, new PropertyChangedEventArgs(propertyName));   
   9:          }   
  10:  }



There is, however, an alternative that works on previous versions of .NET and doesn’t involve expression trees. It essentially involves creating a delegate of the target method, and using the delegate properties to get to the corresponding MethodInfo as mentioned on Daniel Cazzulino’s  blog. I didn’t tried it out yet, but as soon as I created an example, I’ll update this post.

Popular posts from this blog

.NET 8–Keyed/Named Services

A feature that a lot of IoC container libraries support but that was missing in the default DI container provided by Microsoft is the support for Keyed or Named Services. This feature allows you to register the same type multiple times using different names, allowing you to resolve a specific instance based on the circumstances. Although there is some controversy if supporting this feature is a good idea or not, it certainly can be handy. To support this feature a new interface IKeyedServiceProvider got introduced in .NET 8 providing 2 new methods on our ServiceProvider instance: object? GetKeyedService(Type serviceType, object? serviceKey); object GetRequiredKeyedService(Type serviceType, object? serviceKey); To use it, we need to register our service using one of the new extension methods: Resolving the service can be done either through the FromKeyedServices attribute: or by injecting the IKeyedServiceProvider interface and calling the GetRequiredKeyedServic...
Read more

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.
Read more

Kubernetes–Limit your environmental impact

Reducing the carbon footprint and CO2 emission of our (cloud) workloads, is a responsibility of all of us. If you are running a Kubernetes cluster, have a look at Kube-Green . kube-green is a simple Kubernetes operator that automatically shuts down (some of) your pods when you don't need them. A single pod produces about 11 Kg CO2eq per year( here the calculation). Reason enough to give it a try! Installing kube-green in your cluster The easiest way to install the operator in your cluster is through kubectl. We first need to install a cert-manager: kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.5/cert-manager.yaml Remark: Wait a minute before you continue as it can take some time before the cert-manager is up & running inside your cluster. Now we can install the kube-green operator: kubectl apply -f https://github.com/kube-green/kube-green/releases/latest/download/kube-green.yaml Now in the namespace where we want t...
Read more