Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

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

Support for non-LTS .NET releases #214

Closed
alanssitis opened this issue Jan 19, 2024 · 1 comment
Closed

Support for non-LTS .NET releases #214

alanssitis opened this issue Jan 19, 2024 · 1 comment

Comments

@alanssitis
Copy link

Hi dotNext maintainers!

I am a new-ish C# developer looking to integrate this library into my company's code base. One issue I've found is that you only support LTS versions at the moment, we migrate to the next version yearly, which makes us less likely to use dotNext. Would you be open to contributions to support non-LTS versions, and if so, show me the ropes?

@sakno
Copy link
Collaborator

sakno commented Jan 19, 2024

Hi @alanssitis , what the goal you trying to achieve? For instance, .NET 6 dependency can be used without any problem from .NET 7 project. Currently, dotNext 5.x supports .NET 8 natively. In the time of .NET 5 I tried to produce multi-target release (3.1 and 5) but the experience was not good for many reasons:

  • Hard to maintain and test code for both targets because of multiple #if .. #endif
  • Dependency hell when you trying to consume 3.1 target from .net 5 project (MSBuild automatically selects the latest target version)

@dotnet dotnet locked and limited conversation to collaborators Jan 19, 2024
@sakno sakno converted this issue into discussion #215 Jan 19, 2024

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants