Application is running inside IIS process but is not configured to use IIS server .NET Core 3.0

Question

I have migrated our application from .NET Core 2.2 to version 3.0. Actually I created the new application in 3.0 from scratch and then copied source code files. Everything looks great but when I try to run the application within Visual Studio 2019 I get the exception:

Application is running inside IIS process but is not configured to use IIS server

Here is my Program.cs

public static class Program
{
    public static void Main(string[] args)
    {
        CreateHostBuilder(args).Build().Run();
    }

    public static IHostBuilder CreateHostBuilder(string[] args) =>
        Host.CreateDefaultBuilder(args)
            .ConfigureWebHostDefaults(webBuilder =>
            {
                webBuilder.UseContentRoot(Directory.GetCurrentDirectory());
                webBuilder.UseKestrel();
                webBuilder.UseIISIntegration();
                webBuilder.UseStartup<Startup>();
            });
}

The error occurs at the line: CreateHostBuilder(args).Build().Run(); It worked fine in .NET Core 2.2 but it doesn't want to run as 3.0. I cannot find anything else that should be done. Something new in the Startup.cs? I don't know.

Lions

Remove .UseKestrel(). The migration process is documented, in Migrate from ASP.NET Core 2.2 to 3.0. 3.0 is a major version with expected (and documented) breaking changes. The default hosting model now is in-process activation – Burnell

And what if they want to use kestrel? – Sumerology

Answer 1

I also came across this issue while following the documentation https://learn.microsoft.com/en-us/aspnet/core/migration/22-to-30?view=aspnetcore-3.0&tabs=visual-studio

For your case I have checked and the code below will work, with the call to webBuilder.UseKestrel() removed.

public static IHostBuilder CreateHostBuilder(string[] args) =>
       Host.CreateDefaultBuilder(args)
           .ConfigureWebHostDefaults(webBuilder =>
           {
               webBuilder.UseContentRoot(Directory.GetCurrentDirectory());
               webBuilder.UseIISIntegration();
               webBuilder.UseStartup<Startup>();
           });

Antrorse

Yes, leaving out UseKestrel() did the job. Thanks a lot! – Lions

BTW, it works, because ConfigureWebHostDefaults does both: UseKestrel and UseIIS internally. Those methods bind IServer to Kestrel or IIS. ServiceProvider works in "last wins" manner. So, if you write UseKestrel - it's last, if you leave it out UseIIS is last. – Hospitable

Also, UseIISIntegration is also called inside ConfigureWebHostDefaults. – Hospitable

Is it possible to create a "binary" that is compatible to both, IIS and Kestrel? It would be a pity, to create different deployments, just because of these two lines of code... – Transferor

This answer works on my end. Thank you! – Channing

is there anything that would work for all servers? this is not working on my end – Upgrowth

also I'm trying to remove server header which is available only in useKestrel middleware – Upgrowth

Answer 2

I had the same error then to fix my problem I needed to change webBuilder.UseKestrel(); to ConfigureKestrel(serverOptions => {})

My Program.cs before:

public static IHostBuilder CreateHostBuilder(string[] args) =>
    Host.CreateDefaultBuilder(args)
        .ConfigureWebHostDefaults(webBuilder =>
        {
            webBuilder.UseKestrel();
            webBuilder.UseStartup<Startup>();
        });

My Program.cs fixed:

public static IHostBuilder CreateHostBuilder(string[] args) =>
    Host.CreateDefaultBuilder(args)
        .ConfigureWebHostDefaults(webBuilder =>
        {
            webBuilder.ConfigureKestrel(serverOptions =>
            {
            })
            .UseStartup<Startup>();
        });

Josejosee

Answer 3

In my case I ran wrong profile (IIS Express) in Visual Studio by carelessness.

Crumby

Answer 4

As @flam3 suggested, you need to select a profile with correct command.

Open Solution Explorer -> Your Project Name -> Properties -> launchSettings.json file.

The value of the key commandName should be 'Project' instead of 'IIS Express'

So select profile with the name Elsa.Samples.UserRegistration.Web(in my case). See below. Or you may try changing IISExpress to Project on line no 19

Aalborg

Answer 5

For Visual Studio 2019 and 2022

Go to API project properties: Debug Tab -> General -> Hit "Open Debug launch profiles UI"

Scroll Down to Hosting Model and Select "Out Of process"

Then, you will be able to run your application with no Issues.

Windmill