Provide more immediate feedback when an ASP.NET Core app is running

When you create a new ASP.NET Core app in the command line and run it with dotnet run, it can take a few seconds before any feedback is provided to the user (sometimes much longer if it’s the first run). In user studies, we saw first-time .NET users get confused about whether the app is running when there initially isn’t any output. Consider providing more immediate feedback that the app is building and running. Also, consider improving the app startup performance.

Repro steps:

1. dotnet new webapp -o WebApp1
2. cd WebApp1
3. dotnet run

Expected: Near immediate feedback that the app is building and running

Actual: It takes anywhere between 3-30 seconds before any output is displayed.

[RehanSaeed]

Is there any documentation around what the new dotnetRunMessages setting actually does?

I’m trying to understand whether I need to enable it when I configure other launch settings in launchSettings.json like dotnet watch, WSL2, Docker etc.

[lonix1]

There is an explanation for dotnetRunMessages on StackOverflow.