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

Provide an Out-of-Process Control Mechanism for EventPipe that is usable by external customers #191

Closed
tommcdon opened this issue Apr 24, 2019 · 1 comment
Assignees
Milestone

Comments

@tommcdon
Copy link
Member

[Copied from dotnet/coreclr#23780]

This is the same as dotnet/coreclr#18658 with the explicit requirement that external customers can use the control mechanism. This means it has to have a public and documented API.

The primary effort here should be around API review (amongst our team, not official BCL review) and deciding what we want to support for customers. This is a higher bar than we'd hold for internal APIs because we want to maintain compat across versions and make sure we are using best practices for naming and design. Its likely there will be implementation adjustments that fall out from the API review. We also need to get the library published on NuGet.

@tommcdon tommcdon added this to the 3.0 milestone Apr 24, 2019
@tommcdon tommcdon assigned josalem and unassigned jorive Jun 5, 2019
@noahfalk noahfalk assigned sywhang and unassigned josalem Nov 6, 2019
@noahfalk
Copy link
Member

noahfalk commented Nov 6, 2019

This work is included in #343, closing as dupe.

@noahfalk noahfalk closed this as completed Nov 6, 2019
@ghost ghost locked as resolved and limited conversation to collaborators Jun 27, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants