2.7.1 and 2.8.0-beta1 throws NullReferenceException when used together with AspNetCore 3.0 preview8 about applicationinsights-aspnetcore HOT 6 CLOSED

@magnuskarlssonhm sdk with fix for this issue is released now.
https://github.com/microsoft/ApplicationInsights-aspnetcore/releases/tag/2.8.0-beta2
(https://www.nuget.org/packages/Microsoft.ApplicationInsights.AspNetCore/2.8.0-beta2)

from applicationinsights-aspnetcore.

Thanks for reporting it and providing stack trace. This is most likely the same as #936 - we'll address it in the next stable release (early October) and we'll do our best to include the fix in the next beta

from applicationinsights-aspnetcore.

Even if sdk does not quite well support 3.0, it should not have crashed/errored user app under any circumstances.
The listener code was wrapper in try..catch to catch all these potential unknowns in the following PR.
https://github.com/microsoft/ApplicationInsights-aspnetcore/pull/869/files#diff-127c7a3a6227c377b206b4904744707c

However, the above was accidentally overwritten in the perf fixes PR :(
https://github.com/microsoft/ApplicationInsights-aspnetcore/pull/907/files#diff-127c7a3a6227c377b206b4904744707c

1. Need to ensure all code is try.catch ed. (P1)
2. Actual fix for 3.0 listener changes

from applicationinsights-aspnetcore.

Is there a workaround for this? I'm setting up a new project with aspnet core preview8.

from applicationinsights-aspnetcore.

@magnuskarlssonhm No workaround unfortunately. This is being fixed in https://github.com/microsoft/ApplicationInsights-aspnetcore/pull/959/files. It will be part of next beta.

from applicationinsights-aspnetcore.

@cijothomas Thanks!

from applicationinsights-aspnetcore.