Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Update EventPipe Default configuration to try enable both provider name and guid for CLR 2.1 #8

Closed
xiaomi7732 opened this issue Mar 31, 2018 · 1 comment
Closed

Update EventPipe Default configuration to try enable both provider name and guid for CLR 2.1 #8

xiaomi7732 opened this issue Mar 31, 2018 · 1 comment
Assignees
@xiaomi7732
Labels
enhancement New feature or request fix available Fix is checked into source control, ready to be released
Milestone
1.1.2-beta1

Comments

@xiaomi7732
Copy link
Member

xiaomi7732 commented Mar 31, 2018 •
edited

When CLR 2.1 arrives, the enablement requires provider name than guid. Try to enable both for backward compatibility. Expect either name or guid will be hit but not both.
@xiaomi7732 xiaomi7732 self-assigned this Mar 31, 2018
@xiaomi7732 xiaomi7732 added the enhancement New feature or request label Apr 3, 2018
@xiaomi7732 xiaomi7732 added this to the vNext milestone Apr 3, 2018
@xiaomi7732 xiaomi7732 added the fix available Fix is checked into source control, ready to be released label Apr 16, 2018
@xiaomi7732
Copy link
Member Author

Fixed in 1.1.2-beta1: https://www.nuget.org/packages/Microsoft.ApplicationInsights.Profiler.AspNetCore/1.1.2-beta1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@xiaomi7732 xiaomi7732

Labels
enhancement New feature or request fix available Fix is checked into source control, ready to be released
Projects
None yet
Milestone
1.1.2-beta1
Development

No branches or pull requests
1 participant
@xiaomi7732