Simon Cropp

so, as i understand this, the intent is to add a new `IObserver` that handles `Microsoft.AspNetCore` Diagnostics events?

ok looking into this more. isnt this what `AspNetCoreExceptionProcessor` does? ``` internal class AspNetCoreExceptionProcessor : ISentryEventExceptionProcessor { public void Process(Exception exception, SentryEvent @event) { // Mark events collected from the...

@lucas-zimerman the repro could perhaps use a similar approach to https://github.com/getsentry/sentry-dotnet/blob/main/test/Sentry.AspNetCore.Tests/VersioningTests.cs#L22

@lucas-zimerman can u share your controller code?

@lucas-zimerman i put s=together what i think should be a repro: https://github.com/getsentry/sentry-dotnet/pull/1859/files and `TheTransaction` does show up in the payload. is my repro incorrect?

@lucas-zimerman > Maybe we should ignore Pre-flighted requests to not cause confusion? i would still like to be able to repro, and debug into it, before we make that call....

while we look into this. a workaround is to set `SentryOptions.Release` to a custom value.

@bruno-garcia can u share an example how u expect the api usage to look if we use the hint approach

officially yes. in reality no * https://github.com/dotnet/standard/issues/404 * https://andrewlock.net/stop-lying-about-netstandard-2-support/ * https://github.com/dotnet/roslyn/issues/22903 the caveat is here https://docs.microsoft.com/en-us/dotnet/standard/net-standard?tabs=net-standard-2-0#select-net-standard-version  > 2 The versions listed here represent the rules that NuGet uses to...

@vlaterz after taking a close look at this, i am having trouble reproducing it. Can you capture the full "Failed envelope" text and share it? perhaps by piping the console...