Skip to main content

C# 5: Caller Info Attributes

One of the new features that will be available in C# 5 are the Caller Info Attributes.
So what is this animal? If you are/were a C++ developer you probably know the __FILE__ and __LINE__ macros, which expand when compiled to produce a string containing the name of the current source file, and the current line, respectively. Of course C# 5.0 doesn’t support macro’s but the C# team used a different trick to introduce the CallerFilePath, CallerLineNumber and CallerMemberName attributes.
A simple sample:
public static class Trace
{
 public static void WriteLine(string message,
  [CallerFilePath] string file = "",
  [CallerLineNumber] in line = 0,
  [CallerMemberName] string member = "")
 {
  var s = string.Format("{0}:{1} - {2}: {3}", file, line, member, message);

  Console.WriteLine(s);
 }
}
 

If you call the WriteLine method only specifying the message property the compiler would automatically fill out the optional parameters in the WriteLine method with details of where you made the call from.

How can this be useful?

Think about the INotifyPropertyChanged which typically requires the use of magic strings.  Instead of relying on expression trees to get some type safety, we’ll be able to do the following:

protected void RaisePropertyChanged([CallerMemberName] string member = "")
{
    var propertyChanged= PropertyChanged;
    if(propertyChanged != null)
    {
        propertyChanged(new PropertyChangedEventArgs(this, member));
    }
}

and now when you call this method from a property setter, leaving out the optional parameter:

public string ProductName
{
    get
    {
        return _productName;
    }
    set
    {
        _productName=value;
        RaisePropertyChanged();
    }
}

the compiler will fill out the parameter for you, passing “ProductName” to the RaisePropertyChanged method(at least that’s what I hope that it will do, as the feature is not available yet in the current Developer Preview).

Goodbye magic strings!

Popular posts from this blog

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.

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...

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         ...