Skip to main content

ASP.NET Core MVC–The TypeFilterAttribute

If you have ever created your own Action Filter in ASP.NET Core, you are probably aware of the existance of the ServiceFilterAttribute. But did you know that there exists also a TypeFilterAttribute? In this post, I'll explain both types and show you the differences between the two.

Action Filters that are implemented as attributes and added directly to controller classes or action methods cannot have constructor dependencies provided by dependency injection (DI).  This is because attributes must have their constructor parameters supplied where they're applied.

Therefore ASP.NET Core provides two out-of-the-box attributes that can make your action filters DI enabled:

The ServiceFilterAttribute

The ServiceFilter attribute allows us to specify the type of our action filter and have it automatically resolve the class from the built-in DI container. This means that we can implement our action filter to accept dependencies directly via the constructor:

You should register the filter with the correct lifetime in the DI container:

On your controller classes or action methods you can now add the ServiceFilter attribute:

The TypeFilterAttribute

OK, we’ve seen the ServiceFilterAttribute, but what is then the TypeFilterAttribute and in what ways are they different?

The TypeFilterAttribute is very similar to the ServiceFilterAttribute (and also implements IFilterFactory), but its type is not resolved directly from the DI container. Instead, it instantiates the type by using Microsoft.Extensions.DependencyInjection.ObjectFactory.

Because of this difference, types that are referenced using the TypeFilterAttribute do not need to be registered with the container first. This means that when using a TypeFilter, it is possible to provide the constructor parameters yourself (through the Arguments parameter).

Here is an example (that inspired me for this post) I encountered during a code review:

In the example above, an inherited class is created from the TypeFilterAttribute. This is not necessary, and you can also use it directly(I had to change the filter implementation a little bit):

Popular posts from this blog

DevToys–A swiss army knife for developers

As a developer there are a lot of small tasks you need to do as part of your coding, debugging and testing activities.  DevToys is an offline windows app that tries to help you with these tasks. Instead of using different websites you get a fully offline experience offering help for a large list of tasks. Many tools are available. Here is the current list: Converters JSON <> YAML Timestamp Number Base Cron Parser Encoders / Decoders HTML URL Base64 Text & Image GZip JWT Decoder Formatters JSON SQL XML Generators Hash (MD5, SHA1, SHA256, SHA512) UUID 1 and 4 Lorem Ipsum Checksum Text Escape / Unescape Inspector & Case Converter Regex Tester Text Comparer XML Validator Markdown Preview Graphic Color B

Help! I accidently enabled HSTS–on localhost

I ran into an issue after accidently enabling HSTS for a website on localhost. This was not an issue for the original website that was running in IIS and had a certificate configured. But when I tried to run an Angular app a little bit later on http://localhost:4200 the browser redirected me immediately to https://localhost . Whoops! That was not what I wanted in this case. To fix it, you need to go the network settings of your browser, there are available at: chrome://net-internals/#hsts edge://net-internals/#hsts brave://net-internals/#hsts Enter ‘localhost’ in the domain textbox under the Delete domain security policies section and hit Delete . That should do the trick…

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.