microsoft / microsoft/CLRInstrumentationEngine
Consider NuGet package deployment for Instrumentation Engine
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 102
- Forks
- 52
- Avg merge
- 13h 11m
- Merged PRs (30d)
- 6
Description
Providing Instrumentation Engine as a NuGet package would allow profilers to deploy with the app.
This model however would be difficult to cooperate on (if two profilers require different CLRIE versions, the user must resolve this). Consider providing guidance/documentation on how to use CLRIE NuGet in a cooperative manner.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named. Begin by reviewing how Instrumentation Engine deployment is currently handled and how profilers would consume a NuGet package; completion would require an agreed packaging approach plus guidance for coordinating different CLRIE versions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- documentation, release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100