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

Downgrade dotnet to latest lts. #205

Closed
Shadowblitz16 opened this issue Dec 30, 2024 · 4 comments
Closed

Downgrade dotnet to latest lts. #205

Shadowblitz16 opened this issue Dec 30, 2024 · 4 comments

Comments

@Shadowblitz16
Copy link

Is your feature request related to a problem? Please describe.
LTS version of dotnet should be used, since it will be the most stable and supported the longest.

Describe the solution you'd like
Downgrade project to dotnet 8.0 lts

Describe alternatives you've considered
Na

Additional context
Na

@sjoerdev
Copy link

sjoerdev commented Jan 8, 2025

whats wrong with dotnet 9?

@PaperPrototype
Copy link
Contributor

nothing? @Shadowblitz16 is there any specific bugs/problems for why you want to downgrade to .NET 9.0?
As far as I'm aware the only thing that broke with the upgrade was the console window because .net 9 changed the way it formats logs/errors?. I think that may have already been fixed tho I'm not sure.

@sinnwrig
Copy link
Contributor

sinnwrig commented Jan 9, 2025

Maybe the switch back to 8.0 should be considered? the .net 9 image is not currently fully out on github-actions, and it would likely fix issue #203 and #194.

@michaelsakharov
Copy link
Contributor

Maybe the switch back to 8.0 should be considered? the .net 9 image is not currently fully out on github-actions, and it would likely fix issue #203 and #194.

#203 has already been fixed by newer windows patch's
It was some specific windows update that broke it, not really .net 9's fault.
And #194 seems to be working just fine, I'm unable to reproduce any issue with the console, it parses fine and lets me navigate to line numbers, Maybe a related problem to #203?

Also staying on .net 9 also looks good for marketing haha, makes us look modern and fancy.
So I think for the time being its fine to stay on .net 9, If a confirmed problem arises that isn't easily fixed then maybe there's a reason to consider moving back to .net 8.

So for now I'm gonna close this issue.

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

No branches or pull requests

5 participants