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

Update to .Net 7 and modernize the code where possible #6

Open
SpaceOgre opened this issue Mar 6, 2023 · 2 comments · May be fixed by #7
Open

Update to .Net 7 and modernize the code where possible #6

SpaceOgre opened this issue Mar 6, 2023 · 2 comments · May be fixed by #7

Comments

@SpaceOgre
Copy link

Starting a new issue for this so we can keep it separate.

Which versions would you like to target, do you want to keep standard 1.0 and 4.6.1?
Otherwise it might be good to drop them and target:

  • standard2.0
  • net6
  • net7

What do you think?

@nullptre
Copy link
Owner

nullptre commented Mar 6, 2023

My current strategy is to keep backwards compatibility as much as possible. I don't work in .net stack for a while and may be wrong, but it seems I have no better choice than keeping the old version in LTS and make a new code base for net7. Does it make sense?

@SpaceOgre
Copy link
Author

I have started to look into it, but Net Framework 4.6.2 is the oldest version still supporten by Microsoft: https://learn.microsoft.com/en-us/lifecycle/products/microsoft-net-framework
And Net Standard 2.0 is compatible with that version.

So Net Standard 1 can be removed I think, and 4.6.1 replaced with 4.6.2.

If someone is stuck on folder versions than this and dont want or can upgrade can use the 1.0.3 version of this package.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants