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

XUnit - Assert.Collection

A colleague asked me to take a look at the following code inside a test project: My first guess would be that this code checks that the specified condition(the contains) is true for every element in the list.  This turns out not to be the case. The Assert.Collection expects a list of element inspectors, one for every item in the list. The first inspector is used to check the first item, the second inspector the second item and so on. The number of inspectors should match the number of elements in the list. An example: The behavior I expected could be achieved using the Assert.All method:
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

Angular --deploy-url and --base-href

As long you are running your Angular application at a root URL (e.g. www.myangularapp.com ) you don’t need to worry that much about either the ‘--deploy-url’ and ‘--base-href’ parameters. But once you want to serve your Angular application from a server sub folder(e.g. www.mywebsite.com/angularapp ) these parameters become important. --base-href If you deploy your Angular app to a subfolder, the ‘--base-href’ is important to generate the correct routes. This parameter will update the <base href> tag inside the index.html. For example, if the index.html is on the server at /angularapp/index.html , the base href should be set to <base href="/angularapp/"> . More information: https://angular.io/guide/deployment --deploy-url A second parameter that is important is ‘--deploy-url’. This parameter will update the generated url’s for our assets(scripts, css) inside the index.html. To make your assets available at /angularapp/, the deploy url should
Read more