Matt Johnson-Pint

FYI, it appear that the issue also appears in Visual Studio when doing a "Rebuild" - which makes sense as I believe it uses the same mechanism. https://github.com/manuelroemer/IsExternalInit/issues/13

@SimonCropp, I tried with latest with code similar to what I wrote in the troubleshooting docs, and it still fails. I don't think we fixed it.

Thinking through this more, combining async main with exceptions and using blocks is the issue. It's not about Sentry in particular, but rather a general issue with .NET development. It...

@lucas-zimerman - Any update on this one?

Thanks for the report and the repro. We'll look into this and get back to you asap. Thanks.

I can reproduce this using the code you provided. I'm still looking into the cause. Thanks for your patience.

Still investigating, but I have eliminated Serilog and can reproduce with just a generic worker host. ```xml net6.0 enable enable ``` ```csharp using MyWorkerService; var host = Host.CreateDefaultBuilder(args) .ConfigureServices(services =>...

Just to add a workaround, you can try/catch around the entire worker logic and manually capture the exception. If doing so, you'll want to flag it as "unhandled" like this:...

Since there's a viable workaround, I suggest using that for now until we can get a better fix in place. Thanks.

> isnt this what `AspNetCoreExceptionProcessor` does? It would appear so. Though I don't see any reference to `fatal`. We need a better repro of the problem to move this forward.