Support for .NET 10

[nunoguerreirorosa]

Is your feature request related to a problem? Please describe.
Currently, the library does not support .NET 10, which limits its usability in modern applications targeting the latest framework versions. As we upgrade our services and infrastructure to stay aligned with the latest .NET releases, this creates friction and prevents us from adopting the library in newer projects.

Describe the solution you'd like
Add official support for .NET 10 by updating the target frameworks and ensuring compatibility with the latest runtime and SDK. Ideally, this would include:

• Updating the project to target net10.0
• Verifying compatibility with existing features
• Publishing updated NuGet packages supporting .NET 10
• Ensuring CI pipelines validate against .NET 10

Describe alternatives you've considered

• Forking the repository and updating the target framework manually
• Using older .NET versions (not ideal due to missing improvements and long-term support concerns)
• Replacing the library with an alternative that supports newer frameworks

Additional context
.NET evolves quickly, and early support for new versions helps teams adopt improvements in performance, security, and language features. Adding .NET 10 support would make the library future-proof and more appealing for teams keeping up with the latest ecosystem.

[nunoguerreirorosa]

FYI @MichaConrad

[MichaConrad]

@nunoguerreirorosa why do you think this library does not support .NET 10?
Only because its not targeting .NET 10 doesn't mean its not supporting it ;)
There is currently no .NET 10 specific feature in this library which makes targeting .NET 10 not really necessary. And the existing .NET 8 target is compatible with .NET 10.

I will update that eventually / naturally with changes or so in the future. But its not critical.

I'll keep this open as a reminder and thanks anyways! :)

[nunoguerreirorosa]

@MichaConrad thanks for clarifying, makes sense 👍

I hadn’t tested it yet and assumed lack of explicit support might be an issue when I saw the .NET 8 target.
Good to know it’s compatible with .NET 10, that works for our use case then.