This repository has been archived by the owner on Jun 10, 2020. It is now read-only.
Cithomas/w3c aspnet30 #965
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
lmolkova
reviewed
Aug 29, 2019
test/Microsoft.ApplicationInsights.AspNetCore.Tests/HostingDiagnosticListenerTest.cs
Show resolved
Hide resolved
lmolkova
reviewed
Aug 29, 2019
test/Microsoft.ApplicationInsights.AspNetCore.Tests/HostingDiagnosticListenerTest.cs
Show resolved
Hide resolved
lmolkova
reviewed
Aug 29, 2019
src/Microsoft.ApplicationInsights.AspNetCore/RequestTrackingTelemetryModule.cs
Show resolved
Hide resolved
lmolkova
reviewed
Aug 29, 2019
test/Microsoft.ApplicationInsights.AspNetCore.Tests/HostingDiagnosticListenerTest.cs
Show resolved
Hide resolved
lmolkova
approved these changes
Aug 29, 2019
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Following #964, this PR takes asp.net core 3.0 changes in account.
Specifically, 3.0 hosting layer is w3c aware and it'll generate activity from traceparent headers if present, falling back to request-id. This PR accounts for hostinglayer 3.0 being w3c standard aware.
TODO: Functional Tests.