IHostBuilder not working while IWebHostBuilder in Linux in aspnet core 3.1 web api application

I have .net core web api project. I am running my application in both Windows and Linux

Problem is My application get starts and works in both linux and windows with IWebHostBuilder while equivalent(what i think so) code for using IHostBuilder didn’t start my application in linux.

Please somebody give idea what wrong i am doing

Following currently works

   public static IWebHostBuilder BuildWebHost(string[] args) => WebHost.CreateDefaultBuilder(args).
           ConfigureKestrel(serverOptions =>
           {
           }).UseIISIntegration()
           .UseStartup<StartupShutdownHandler>(); 

Following doesn’t works in linux but works in windows

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

I have to run my app on both windows and linux

[Tratcher]

“server.urls” is considered obsolete and replaced by “urls”. We transitioned to “urls” quite a while ago, but I don’t see the associated annoucement. WebHost checked both for backcompat. https://github.com/dotnet/aspnetcore/blob/d4a2fa1ceb3b9c10054da8a7c6a4bd61801aea18/src/Hosting/Hosting/src/Internal/WebHost.cs#L303 GenericHost does not. https://github.com/dotnet/aspnetcore/blob/e3d3da3546aa2085aa39520f3c302d0672e5bab8/src/Hosting/Hosting/src/GenericHost/GenericWebHostedService.cs#L71

[KamranShahid]

“server.urls” is considered obsolete and replaced by “urls”. We transitioned to “urls” quite a while ago, but I don’t see the associated annoucement. WebHost checked both for backcompat. https://github.com/dotnet/aspnetcore/blob/d4a2fa1ceb3b9c10054da8a7c6a4bd61801aea18/src/Hosting/Hosting/src/Internal/WebHost.cs#L303

GenericHost does not. https://github.com/dotnet/aspnetcore/blob/e3d3da3546aa2085aa39520f3c302d0672e5bab8/src/Hosting/Hosting/src/GenericHost/GenericWebHostedService.cs#L71

Your are correct. looks like we were using some initial way assigning service which isn’t available even in documents. I will try to update this in my service. Any way thanks for this precious information. Will try to edit my service file tomorrow and run it