Skip to main content

.NET 7 - The StringSyntaxAttribute

With the release of .NET 7, a new attribute was introduced; the StringSyntaxAttribute.

What does the StringSyntaxAttribute do?

The StringSyntaxAttribute allows you to tag strings. It can be applied to fields, properties, and parameters and provides tools like Visual Studio with information about the nature of the string.

The compiler will use this information to provide the correct syntax highlighting:

In this release following string formats can be used out of the box (and it is possible to create custom ones):

  • CompositeFormat: The syntax identifier for strings containing composite formats for string formatting.
  • DateOnlyFormat: The syntax identifier for strings containing date format specifiers.
  • DateTimeFormat: The syntax identifier for strings containing date and time format specifiers.
  • EnumFormat: The syntax identifier for strings containing Enum format specifiers.
  • GuidFormat: The syntax identifier for strings containing Guid format specifiers.
  • Json: The syntax identifier for strings containing JavaScript Object Notation (JSON).
  • NumericFormat: The syntax identifier for strings containing numeric format specifiers.
  • Regex: The syntax identifier for strings containing regular expressions.
  • TimeOnlyFormat: The syntax identifier for strings containing time format specifiers.
  • TimeSpanFormat: The syntax identifier for strings containing TimeSpan format specifiers.
  • Uri: The syntax identifier for strings containing URIs.
  • Xml: The syntax identifier for strings containing XML.

Remark: Not all of the above formats are recognized by Visual Studio at the moment of writing.

Labels:

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

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