Kasbolat Kumakhov

Unfortunately `InvokeAsync` won't help here since in the end it is also not awaited hence not observed. I guess I'll move it all to effects then. Thanks.

Thanks, but it doesn't make any difference regarding exception handling. If it's not awaited in the end then exceptions are not handled. For example: ```c# private void Test() { _...

I was going to )) Just need to find some time to make it right.

@massimotomasi in your case I would just make something like `FinishedEvent` that is triggered by an effect of `Action` when it's finished. And in razor pages I would `SubscribeToAction` to...

@nblumhardt actually we are using MEL and `Serilog` is configured like this: ```c# public static IServiceCollection AddConfigurableSerilog(this IServiceCollection services, IConfiguration configuration) => services .AddSerilog(new LoggerConfiguration() .ReadFrom.Configuration(configuration) .CreateLogger(), true) ; ```...

It's not just the components that use logging but other services too. And not all of them are `IAsyncDisposable`. Do you think if we could simply `async`/`void` in this case?...

We are using `app.RunAsync()` and more then that we dispose `WebAssemblyHost` manually through `await host.DisposeAsync()` but that doesn't make any difference since exceptions are thrown not at the end of...

Good catch. After your comment I did some digging and found there were some pieces of code that created an `ILoggerFactory`, an `ILogger` from it, output some logs and then...