Author: natan

• Controller type inherits from ControllerBase and have Views support
• ControllerBase type is better suited for APIs

Further read:

https://learn.microsoft.com/en-us/aspnet/core/web-api/?view=aspnetcore-6.0

• default application server for .net
• cross platform
• best performance and memory utilization
• may not have some advanced features of HTTP.sys on Windows
• may be used with proxy server or as internet facing server

Further read:

https://learn.microsoft.com/en-us/aspnet/core/fundamentals/servers/kestrel?view=aspnetcore-6.0

To handle exceptions on Controller/Action level Exception Filters are used.

[TypeFilter(typeof(SampleExceptionFilter))]
public class ExceptionController : Controller

Exception Filters are implemented using IExceptionFilter with OnExcetion method override to handle exceptions.

Exception Filters can be applied to Controller and Action level.

Further read:

https://learn.microsoft.com/en-us/aspnet/core/mvc/controllers/filters?view=aspnetcore-7.0#exception-filters

https://learn.microsoft.com/en-us/dotnet/api/microsoft.aspnetcore.mvc.filters.iexceptionfilter?view=aspnetcore-7.0

To add global exception handling in ASP.NET Core just use configuration method:

app.UseExceptionHandler

https://learn.microsoft.com/en-us/aspnet/core/fundamentals/error-handling?view=aspnetcore-6.0#exception-handler-lambda

Pretty much everything. Default ASP.NET Core request handling pipeline is consisting of bunch of middlewares:

• Authentication
• Authorization
• CORS
• HTTP Logging
• MVC
• Static Files
• other

Whole list of built-in middlewares can be found here:

https://learn.microsoft.com/en-us/aspnet/core/fundamentals/middleware/?view=aspnetcore-7.0#built-in-middleware

There is possibility to write custom middleware too.