Skip to main content

Make your ASP.NET Core application always running on IIS

By default when running an ASP.NET Core application in IIS, the application will not be started until the first user hits your ASP.NET Core application. This of course saves some resources(CPU, memory,...) when no one is accessing your site, but comes with a performance penalty when the first request arrives.

A related feature exists where the application pool is shutdown after some idle time.

Although I think this is a good default it is not what we want when we have one or more background tasks running in our ASP.NET Core application. In these situations you want to have your ASP.NET Core application always running.

Let me walk you through the steps how to get this done.

Install IIS features

First check if you have the Application Initialization Module installed in IIS. If you are doing this on your local development machine, have a look at the list of Windows Features:

Otherwise you can install it through Server Manager:

  • Open the Add Roles and Features Wizard.
  • In the Select role services panel, open the Application Development node.
  • Select the checkbox for Application Initialization.

Configure IIS

Now we need to configure IIS. Start by opening the IIS Manager.

We start by configuring the Application pool:

  • Select Application Pools in the Connections panel.
  • Right-click the app's app pool in the list and select Advanced Settings.
  • The default Start Mode is OnDemand. Set the Start Mode to AlwaysRunning.
  • Also update the Idle Time-Out (minutes) to 0.
  • Select OK.

Now we need to also update the website to activate the preload feature:

  • Open the Sites node in the Connections panel.
  • Right-click the app and select Manage Website > Advanced Settings.
  • The default Preload Enabled setting is False. Set Preload Enabled to True.
  • Select OK.

    Configure your ASP.NET Core app

    There is not much you need to do at the level of your ASP.NET Core application. The only thing that is required is that your are using the In-Process hosting model which is the default.

    More information can be found at:

    Labels:

    Popular posts from this blog

    .NET 8–Keyed/Named Services

    A feature that a lot of IoC container libraries support but that was missing in the default DI container provided by Microsoft is the support for Keyed or Named Services. This feature allows you to register the same type multiple times using different names, allowing you to resolve a specific instance based on the circumstances. Although there is some controversy if supporting this feature is a good idea or not, it certainly can be handy. To support this feature a new interface IKeyedServiceProvider got introduced in .NET 8 providing 2 new methods on our ServiceProvider instance: object? GetKeyedService(Type serviceType, object? serviceKey); object GetRequiredKeyedService(Type serviceType, object? serviceKey); To use it, we need to register our service using one of the new extension methods: Resolving the service can be done either through the FromKeyedServices attribute: or by injecting the IKeyedServiceProvider interface and calling the GetRequiredKeyedServic...
    Read more

    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.
    Read more

    Kubernetes–Limit your environmental impact

    Reducing the carbon footprint and CO2 emission of our (cloud) workloads, is a responsibility of all of us. If you are running a Kubernetes cluster, have a look at Kube-Green . kube-green is a simple Kubernetes operator that automatically shuts down (some of) your pods when you don't need them. A single pod produces about 11 Kg CO2eq per year( here the calculation). Reason enough to give it a try! Installing kube-green in your cluster The easiest way to install the operator in your cluster is through kubectl. We first need to install a cert-manager: kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.5/cert-manager.yaml Remark: Wait a minute before you continue as it can take some time before the cert-manager is up & running inside your cluster. Now we can install the kube-green operator: kubectl apply -f https://github.com/kube-green/kube-green/releases/latest/download/kube-green.yaml Now in the namespace where we want t...
    Read more