Microsoft.Testing.Extensions.Telemetry blocked from upgrading to latest Microsoft.ApplicationInsights
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 1k
- Forks
- 312
- Avg merge
- 8h 30m
- Merged PRs (30d)
- 469
Description
I was looking into an issue where Microsoft.Testing.Extensions.Telemetry on .net 9 was still fetching System.Diagnostics.DiagnosticSource 5.0.0 due to Microsoft.ApplicationInsights dependency. I noticed that Microsoft.ApplicationInsights has released major version 3 which no longer has System.Diagnostics.DiagnosticSource however it no longer supports netStandard2.0 as part of microsoft/ApplicationInsights-dotnet#3091.
Microsoft.Testing.Extensions.Telemetry and Microsoft.Testing.Extensions.VSTestBridge will need to choose a route:
1. Drop netStandard2.0 in favor of .NETFramework 4.6.2 or higher
2. See if ApplicationInsights restores NetStandard2.0 (dropped due to difficulty with OpenTelemetry microsoft/ApplicationInsights-dotnet#3130)
3. Forever stay on Microsoft.ApplicationInsights 2.23.0
4. Drop ApplicationInsights support
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
Start by reviewing the Microsoft.Testing.Extensions.Telemetry and Microsoft.Testing.Extensions.VSTestBridge dependency declarations, then read the referenced Microsoft.ApplicationInsights issues. Done means selecting and implementing a supported route for the Microsoft.ApplicationInsights dependency while accounting for the netStandard2.0 compatibility constraint.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- testing-qa
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100