Should never use async void

[tebeco]

Should never use async void

I tried other scenario but that seems to endup in deadlock or the WebHostBuilder is not happy
I ended up avoiding

Not working so far:

public async Task Configure(IApplicationBuilder app, IHostingEnvironment env)
{
  await Electron.WindowManager.CreateWindowAsync()
}

public void Configure(IApplicationBuilder app, IHostingEnvironment env)
{
  Electron.WindowManager.CreateWindowAsync().Start()
}

public void Configure(IApplicationBuilder app, IHostingEnvironment env)
{
  Electron.WindowManager.CreateWindowAsync().RunSynchronously()
}

[yeskunall]

I'm just going to place this quote from this article here in case anyone is wondering why this is useful:

Async void methods have different error-handling semantics. When an exception is thrown out of an async Task or async Task method, that exception is captured and placed on the Task object. With async void methods, there is no Task object, so any exceptions thrown out of an async void method will be raised directly on the SynchronizationContext that was active when the async void method started.

... also because Electron.WindowManager.CreateWindowAsync seems to be a CPU-bound task, spawning the work off on another thread with Task.Run will ensure responsiveness.

[tebeco]

Well the question is
should/does AspnetCore support Async scenario while Configure()

[robertmuehsig]

The normal Configure() is not async as well, so it seems your suggestion is "better" with the Task.Run...