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.

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

Add .NET Core support for Diagnostics package #175

Closed
adamsitnik opened this issue May 11, 2016 · 4 comments
Closed

Add .NET Core support for Diagnostics package #175

adamsitnik opened this issue May 11, 2016 · 4 comments

Comments

@adamsitnik
Copy link
Member

Currently we are blocked by the fact that TraceEvent is not available on CoreCLR. As soon as it gets fixed by Microsoft I will implement that.

@adamsitnik adamsitnik self-assigned this May 11, 2016
@mattwarren
Copy link
Contributor

More fundamentally they need to port ETW events (or something equivalent) to other OSes first. See this doc for a discussion of where they are headed.

@adamsitnik adamsitnik added this to the v0.10.x milestone May 26, 2016
@adamsitnik
Copy link
Member Author

TraceEvent has been ported to .NET Core.

I am waiting for the NuGet package now.

@brianrob
Copy link
Member

This should be unblocked now. This package supports .NET Core: https://www.nuget.org/packages/Microsoft.Diagnostics.Tracing.TraceEvent/2.0.4

@adamsitnik adamsitnik changed the title [blocked] Add .NET Core support for Diagnostics package Add .NET Core support for Diagnostics package Mar 22, 2018
@adamsitnik adamsitnik modified the milestones: v0.11.x, v0.11.0 Mar 22, 2018
@adamsitnik
Copy link
Member Author

Fixed with this commit, but needs to wait for v0.11.0 release (it will be one big release with some breaking changes)

This was referenced Apr 10, 2018
Merged
adamsitnik added a commit that referenced this issue Apr 10, 2018
alinasmirnova pushed a commit to alinasmirnova/BenchmarkDotNet that referenced this issue Sep 22, 2018
alinasmirnova pushed a commit to alinasmirnova/BenchmarkDotNet that referenced this issue Sep 22, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants