Skip to main content

C# 11–Generic Attributes

C# 11 introduces a large list of new language features. One of the smaller features is the support for generic attributes.

Before C# 11, when you had to pass type information to an attribute, you had to use a type parameter.

Let’s use an example that always has annoyed me; the [ServiceFilterAttribute]. If you have ever used an ASP.NET MVC filter that needed dependencies, then you should know this attribute.

Here is an example I copied from the Microsoft documentation:

You see in the example above is that the type of the actual filter we want to invoke is passed as a parameter to the ServiceFilterAttribute.

The constructor looks something like this:

By not being able to use generics, I could pass anything I want as a parameter to the ServiceFilter no matter if it is actually a filter or not. The compiler will not help me to avoid passing an incorrect argument.

A type safe ServiceFilter

With the release of C# 11 and the introduction of Generic Attributes, we can create a type safe variant of the [ServiceFilterAttribute] as an example:

Now the compiler will warn me when I try to pass a type that isn’t a filter:

Remark: There are multiple interfaces that can be used to implement a filter. In the example above I only used the IActionFilter. So this is not a production ready solution for all use cases.

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:

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.

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