Replies: 2 comments 6 replies
-
This client is very widely used and it cannot afford to require .NET 8 — that's been out for less than two months — immediately. At some point it will, just like the rest of the ecosystem. That can easily be a year or two away. |
Beta Was this translation helpful? Give feedback.
1 reply
-
@nimanikoo it is unlikely this project will ever support C# language version greater than |
Beta Was this translation helpful? Give feedback.
5 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Is your feature request related to a problem? Please describe.
Hi 👋
I hope you are doing well.
I was reviewing the project and noticed that .NET 7 is being used for the latest version.
I also noticed some areas in the code where accessor modifiers could be applied, which might be helpful during code review.
I wanted to ask if you have any plans to upgrade to C# 12 and .NET 8?
If you are agreeable, I would be happy to help with the upgrade and submit a pull request for the changes.
I believe that upgrading to C# 12 and .NET 8 would be a positive step for the project and would make it more efficient, scalable, and future-proof.
Please let me know your thoughts on this proposal.
Thank you
Describe the solution you'd like
Step 1: I will update all existing modules and projects to .NET 8.
Step 2: I will fix the namespaces and utilize the new features of .NET 8.
Step 3: I will perform a code review file by file to improve readability and refactor the code with references.
I am open to suggestions and feedback.
I will refactor the code to make it more modular and reusable.
I am confident that this upgrade will be a positive step for the project and I look forward to working with you on it.
Thank you for your time and consideration
Describe alternatives you've considered
No response
Additional context
No response
Beta Was this translation helpful? Give feedback.
All reactions