Development with a Dot

Introduction This is post #2 on my series of posts on ASP.NET Core extensibility. The first one is this one , on the core extension points. This time, I'm going to focus on extensibility that is specific to MVC . I'm covering here: Controller factories and activators Action invokers, action invoker factories and action invoker providers Action constraints and action contraint factories Value providers and value provider factories Input and output formatters Output cache Controller Factories and Activators A controller factory is what creates a controller instance and also takes care of releasing (disposing of) it. A controller activator does similar things, even the methods they expose are very similar, as we can see it from the controller factory  IControllerFactory  and the controller activator  IControllerActivator  interfaces. As it is, the default controller factory class,  DefaultControllerFactory , receives a controller activator from Dependency Injection...

Introduction This will be a long series of post about some of the ASP.NET Core extensibility points. By this, I mean any feature of ASP.NET Core that can be replaced/augmented by adding custom code, or switching to a different existing option. I will mention each extension point, how to change it, and some of its typical use cases. This will be split into different posts, and the structure is likely to be: ASP.NET Core itself (this one) MVC  only MVC  and  Minimal APIs : things that are relevant to both MVC  and  Razor Pages : same here Razor Pages  only Let's start first with the basics, functionality that exists regardless of MVC or Minimal APIs or Razor Pages . I'm going to cover: Hosts and servers Dependency Injection Middleware and middleware factories JSON and XML serialisation File providers Data protection and data protection providers Cryptography Session store Hosts and Servers A host is what executes a server to, you know, serve HTTP reques...