Further simplify empty project template

[halter73]

The await using was unnecessary since Run/RunAsync dispose internally.

I'm less sure about changing the await app.RunAsync() to app.Run() , but it is less verbose this way and it's equivalent as long as there's no other awaits in the top-level statement. We could add an analyzer to suggest RunAsync if an await is added as a top-level statement. Worst case is one extra blocked thread for the lifetime of the application.

#32003 Was the PR started using WebApplication in the empty template.

[JamesNK]

here's no other awaits in the top-level statement. We could add an analyzer to suggest RunAsync if an await is added as a top-level statement.

What happens if another await is added while the blocking Run is used? Is there any negative side effect?

Worst case is one extra blocked thread for the lifetime of the application.

Even with RunAsync, is a thread somewhere is blocked while the app is running? I don't know the mechanics of async+Main and async+top-level.

[halter73]

What happens if another await is added while the blocking Run is used? Is there any negative side effect?

I'm assuming that's the "worst case" where one extra blocked thread for the lifetime of the application.

[davidfowl]

I'm gonna make a fix to hosting to not block forever. Also I made a fix to avoid the wait if ctrl+c does fire. In general we're going to be attempting to fix the hang so don't worry about it

[Tratcher]

What's the total character count down to now?

[davidfowl]

/azp run aspnetcore-ci

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[davidfowl]

I thought these tests were quarantined/disabled @captainsafia @pranavkm