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

netstandard2.0 dropped in 2.6.0 #1311

Closed
martonb opened this issue Jan 5, 2025 · 2 comments · Fixed by #1312
Closed

netstandard2.0 dropped in 2.6.0 #1311

martonb opened this issue Jan 5, 2025 · 2 comments · Fixed by #1312
Assignees
Labels
bug Something isn't working

Comments

@martonb
Copy link

martonb commented Jan 5, 2025

What happened?

The netstandard2.0 support was dropped in version 2.6.0, this causes any project based on any version of .Net Framework (eg: 4.8, still officially supported by MS) to not be able to use this library.
Not sure if this was intentional?

Code usage

No response

Log output

No response

@DaveSkender
Copy link
Owner

Let me look into this. As I've been working on v3 there's been significant limitations with the .NET Standard framework targeting, so am almost certainly removing at least 2.0 from that version. Let me see if I can reasonably add it back to v2 as I can see how that's going to be a problem for some users.

@DaveSkender DaveSkender self-assigned this Jan 5, 2025
@DaveSkender DaveSkender moved this from Maybe to Do Next in Stock Indicators for .NET Jan 5, 2025
@DaveSkender DaveSkender moved this from Do Next to In Progress in Stock Indicators for .NET Jan 5, 2025
DaveSkender added a commit that referenced this issue Jan 5, 2025
@DaveSkender DaveSkender linked a pull request Jan 5, 2025 that will close this issue
2 tasks
@github-project-automation github-project-automation bot moved this from In Progress to Done in Stock Indicators for .NET Jan 5, 2025
@DaveSkender
Copy link
Owner

this will be in v2.6.1 when released

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
Development

Successfully merging a pull request may close this issue.

2 participants