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

Port TraceEvent to .NET Core #165

Closed
vancem opened this Issue Mar 2, 2017 · 8 comments

Comments

Projects
None yet
5 participants
@vancem
Member

vancem commented Mar 2, 2017

This is transferring the following bug that was in the corefx repo dotnet/corefx#4864

Basically we want the Microsoft.Diagnostics.Tracing.TraceEvent nuget package to work on .NET Core.

@adamsitnik

This comment has been minimized.

Show comment
Hide comment
@adamsitnik

adamsitnik Mar 13, 2017

Member

@vancem I just want to let you know that BenchmarkDotNet would love to have Microsoft.Diagnostics.Tracing.TraceEvent ported to .NET Core. We are currently using the existing version, and would like to give our .NET Core users great experience.

Member

adamsitnik commented Mar 13, 2017

@vancem I just want to let you know that BenchmarkDotNet would love to have Microsoft.Diagnostics.Tracing.TraceEvent ported to .NET Core. We are currently using the existing version, and would like to give our .NET Core users great experience.

@ViktorHofer

This comment has been minimized.

Show comment
Hide comment
@ViktorHofer

ViktorHofer Apr 14, 2017

Member

@vancem Is there any progress on that matter or are you still investigating? We have some disabled tests in corefx which rely on that feature.

Member

ViktorHofer commented Apr 14, 2017

@vancem Is there any progress on that matter or are you still investigating? We have some disabled tests in corefx which rely on that feature.

@vancem

This comment has been minimized.

Show comment
Hide comment
@vancem

vancem Apr 14, 2017

Member

I have not made progress. It should be a straightforward exercise (at least to make SOME progress), I just have not had time. I will raise its priority a bit, but I still offer no promises.

Member

vancem commented Apr 14, 2017

I have not made progress. It should be a straightforward exercise (at least to make SOME progress), I just have not had time. I will raise its priority a bit, but I still offer no promises.

@vancem

This comment has been minimized.

Show comment
Hide comment
@vancem

vancem Aug 23, 2017

Member

This has been fixed by PR #360.

Member

vancem commented Aug 23, 2017

This has been fixed by PR #360.

@vancem vancem closed this Aug 23, 2017

@adamsitnik

This comment has been minimized.

Show comment
Hide comment
@adamsitnik

adamsitnik Aug 25, 2017

Member

@vancem When do you plan to release the new NuGet package?

Member

adamsitnik commented Aug 25, 2017

@vancem When do you plan to release the new NuGet package?

@vancem

This comment has been minimized.

Show comment
Hide comment
@vancem

vancem Aug 25, 2017

Member

When do you plan to release the new NuGet package

There is some work to do before I can release the package on Nuget. In particular it needs to be signed, and some testing has to be added. Also it has to be tested on the scenarios we have for that package (e.g. there are samples). This is not my top priority right now so it is hard to give a deadline, but it will be at least another week or so (the wildcard is how much time I can give it)

Member

vancem commented Aug 25, 2017

When do you plan to release the new NuGet package

There is some work to do before I can release the package on Nuget. In particular it needs to be signed, and some testing has to be added. Also it has to be tested on the scenarios we have for that package (e.g. there are samples). This is not my top priority right now so it is hard to give a deadline, but it will be at least another week or so (the wildcard is how much time I can give it)

@TyOverby

This comment has been minimized.

Show comment
Hide comment
@TyOverby

TyOverby Sep 15, 2017

Hi @vancem, it looks like this package has not made its way to nuget yet. Is there anything I can do to help publish it? I'm just down the hall from you if you want to chat!

TyOverby commented Sep 15, 2017

Hi @vancem, it looks like this package has not made its way to nuget yet. Is there anything I can do to help publish it? I'm just down the hall from you if you want to chat!

@benaadams

This comment has been minimized.

Show comment
Hide comment
@benaadams

benaadams Dec 30, 2017

Was trying to listen to some kernel events with .NET Core to detect blocking calls; but alas...

Would be great when the packages are shipped! 😉

benaadams commented Dec 30, 2017

Was trying to listen to some kernel events with .NET Core to detect blocking calls; but alas...

Would be great when the packages are shipped! 😉

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