Stefan Pölz

Thanks @KrzysztofFryzlewicz for reporting this issue. One aspect that catches my eye is that you mentioned using `v5.15.1` of the SDK, but the error contains `\5.14.1\`. Not sure if there...

Thanks for your rapid reply, @KrzysztofFryzlewicz. Which Visual Studio exactly? Although, doesn't really matter. _Visual Studio 16.11.nn_ supports/includes the _.NET SDK 5.0.4nn_, which supports _C# 9.0_ and the Compiler (Roslyn)...

In the meantime, I wonder if either of these workarounds could help you temporarily, until we provide proper multi-targeting: Not consuming the .NET Analyzer assets that we provide. ```XML analyzers...

> We can close this issue, we did a workaround and it will probably resolve itself in the future. Thanks! I'd like to keep it open, at least for now,...

#4569 is now reporting this issue in CI

Thanks @Alfieri for your scenarios. How could we move forward with this? E.g. first, add some scenarios about performance/transactions/tracing to our Blazor `samples`. And then either add to docs, or...

+1 through User Feedback via WASM docs. As a quick win, we could add a Guide in the docs, mirroring our current WASM Sample, until we got a dedicated package.

Another observation we made is that the flag `options.DisableSentryHttpMessageHandler = true;` is different from other "Disable-Integration" options which are methods rather than a property. Is this by design or accidental?...

This will also be helpful for `sentry-dotnet`, as we also "craft" (😉) our [CHANGELOG.md](https://github.com/getsentry/sentry-dotnet/blob/main/CHANGELOG.md) manually, but run into merge conflicts constantly.

With `Serilog` already integrated, and `Log4Net` covered here, we may follow-up with `NLog` to round things off.