logging – { Think Rethink }

Hosting services in .NET Core console application

In .NET Core, the IHost interface is used to configure and run applications, particularly when implementing background services or hosting long-running processes. By using IHostedService, developers can easily manage these services with built-in support for dependency injection, logging, and graceful shutdown.

Key Concepts:

IHost: Initializes and configures services for the application.
IHostedService: Represents background services with lifecycle management.
Graceful Shutdown: Handling cleanup tasks when the application stops.

Log4Net troubleshooting, debug your configuration

See some common log4net problems and learn how to debug/solve then.

Log4net is a fail-stop logging system. Fail stop means that it stops logging on an internal exception and by design does not interact with the program flow. Knowing this explains you troubleshooting log4net isn’t so easy. If logging fails, your program does not notice. You see a lot of questions about: why is my log4net logging not working? This article explains the basic troubleshooting and most common solutions.

Continue reading “Log4Net troubleshooting, debug your configuration”

Application Shutdown in ASP.NET Core 6/8

In .NET 6 and 8, gracefully handling application shutdown is crucial for releasing resources or completing ongoing tasks before the application ends. The IApplicationLifetime interface was deprecated in favor of IHostApplicationLifetime in ASP.NET Core 3.0, and this approach continues in .NET 6/8.

1. Add IHostApplicationLifetime to your service

In modern ASP.NET Core applications, IHostApplicationLifetime is injected into services, such as controllers or services where you need to handle shutdown events.