One of the new features of ASP.NET Core 2.2 is support for hosting ASP.NET Core Web App with IIS using in-process or out-of-process hosting model.

This article covers pretty much all the important things about localization in ASP.NET Core and MVC Core.

This part is about a feature you can use to create background services to run tasks asynchronously inside your application. Actually I use this feature to regularly fetch data from a remote service in a small ASP.NET Core application.

How to use it and how to customize the configuration to use different ways to configure your app.

This will show you how to customize the logging. The default logging only writes to the console or to the debug window. This is quite good for the most cases, but maybe you need to log to a sink like a file or a database. Maybe you want to extend the logger with additional information. In that cases you need to know how to change the default logging.

In this post I 'm going to talk about a few gotchas with the .NET Core's built-in inversion of control (IoC) / service provider (SP)/dependency injection (DI) library.

The options pattern uses classes to represent groups of related settings.