Stride is support newest NET or not?

[ghost]

The problem is that by default visual studio loads both NET 8 and NET 9 to newer versions but stride itself does not allow it to start because there is no SDK NO 8 version 100 at the moment if I am not mistaken how can I get rid of this so to speak and will there be an update of the engine as a whole for newer NET

[Doprez]

The goal was to only use the LTS versions of .NET. There were some plans to have a "for fun" branch of .NET 9 but it was never meant to be released and with .NET 10 around the corner it will be changed this year.

With VS automatically installing the latest STS version of .NET this has become a bit frustrating however and will probably need to be looked into.
Some changes that could be made:

• The builder should use the latest installed version of .NET on the users machine to build.
• The builder should look for the version Stride supports and use that as its context to avoid problems with untested .NET versions.

[Kryptos-FR]

It's not something that we have to deal with in my opinion. Developers that use .NET should know they must install the right SDK. We don't do anything special in Stride it is the same as for any other development in modern .NET.

Edit: I'm not sure what you mean by "the builder".

[Doprez]

By builder I think I mean the PackageSessionPublicHelper.cs (Its been a while since I messed with it so I might be forgetting which one is the blocker here).

The problem is that in my opinion it should not fail the build if a newer valid version is available by default. Ill mess with it to double check but I think it was a problem even when both were available that it would cause an issue since the defaulted version for dotnet was above current LTS.

[Kryptos-FR]

I see. I was thinking of something else.