0
votes

I have this AspNetCore application that runs ok under VS2019. Listens correctly on 5001 and all.

But when I try to run it from bin\Debug\necoreapp3.1 folder from command line using

dotnet mywebapp.dll

it goes up normally (stating that it is correctly listening on 5000 and 5001 ports with the correct content path root) as if it was executed from VS2019:

info: WorkflowCore.Services.WorkflowHost[0]
      Starting background tasks
info: WorkflowCore.Services.BackgroundTasks.RunnablePoller[0]
      Polling for runnable workflows
info: Microsoft.Hosting.Lifetime[0]
      Now listening on: https://localhost:5001
info: Microsoft.Hosting.Lifetime[0]
      Now listening on: http://localhost:5000
info: Microsoft.Hosting.Lifetime[0]
      Application started. Press Ctrl+C to shut down.
info: Microsoft.Hosting.Lifetime[0]
      Hosting environment: Development
info: Microsoft.Hosting.Lifetime[0]
      Content root path: C:\work\mywebapp
info: WorkflowCore.Services.BackgroundTasks.RunnablePoller[0]

but when I try to connect to https://localhost:5001 via browser it is unable to connect.

after a while this log appears in the output:

warn: Microsoft.AspNetCore.Server.Kestrel[22]
      Heartbeat took longer than "00:00:01" at "09/01/2021 11:02:44 +00:00". This could be caused by thread pool starvation.

Anybody can help me?

Thanks in advance. P.

Just for ensure.. aren't you selecting the text in console? selecting a text in console cause the thread to stop/pause, and you need to hit enter to run againLeo
hi Leo, yes I'm sure. I do not click in the console output (ie. to select the url). It stays clear.Patrick Bateman
Is The behavior of running dotnet run from project folder, instead of bin, the same?Leo
same behavior for dotnet run. It seems working only by executing it under VS2019.Patrick Bateman
I suppose you tried connecting with http in stead of https?Svein Terje Gaup