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

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...

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.

VS Code Planning mode

After the introduction of Plan mode in Visual Studio , it now also found its way into VS Code. Planning mode, or as I like to call it 'Hannibal mode', extends GitHub Copilot's Agent Mode capabilities to handle larger, multi-step coding tasks with a structured approach. Instead of jumping straight into code generation, Planning mode creates a detailed execution plan. If you want more details, have a look at my previous post . Putting plan mode into action VS Code takes a different approach compared to Visual Studio when using plan mode. Instead of a configuration setting that you can activate but have limited control over, planning is available as a separate chat mode/agent: I like this approach better than how Visual Studio does it as you have explicit control when plan mode is activated. Instead of immediately diving into execution, the plan agent creates a plan and asks some follow up questions: You can further edit the plan by clicking on ‘Open in Editor’: ...