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

.NET Standard 2.1 for Microsoft.Extensions.TimeProvider.Testing #5077

Open
neuecc opened this issue Apr 3, 2024 · 1 comment
Open

.NET Standard 2.1 for Microsoft.Extensions.TimeProvider.Testing #5077

neuecc opened this issue Apr 3, 2024 · 1 comment
Assignees
Labels
enhancement This issue represents an ask for new feature or an enhancement to an existing one
Milestone

Comments

@neuecc
Copy link

neuecc commented Apr 3, 2024

Currently, Microsoft.Extensions.TimeProvider.Testing targets .NET Framework 4.6.2, .NET 8, and .NET 9.
Would it be possible to add .NET Standard 2.1 as a target?
The code itself seems to be fine, so it's just a matter of policy whether to add it to the target or not.
Microsoft.Bcl.TimeProvider supports .NET Standard 2.0.

To provide some context for this request, I am developing a library called R3 that depends on TimeProvider.
https://github.com/Cysharp/R3
This library is very popular for Unity game engine, and when using Microsoft.Extensions.TimeProvider.Testing in Unity,
the lack of .NET Standard 2.1 support is causing issues.

@geeknoid geeknoid added enhancement This issue represents an ask for new feature or an enhancement to an existing one and removed untriaged labels May 31, 2024
@joperezr
Copy link
Member

@neuecc thanks for logging the issue and sorry for the delay in the reply. Yes we should do this as it will benefit library developers. Also this should be done across the board, as opposed to just for Microsoft.Extensions.TimeProvider.Testing, and I believe it is possbile to target netstandard2.0 in most places (as opposed to ns2.1) to match the pattern in the packages of dotnet/runtime.

@joperezr joperezr added this to the Backlog milestone May 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement This issue represents an ask for new feature or an enhancement to an existing one
Projects
None yet
Development

No branches or pull requests

3 participants