←back to thread

.NET 10

(devblogs.microsoft.com)
489 points runesoerensen | 6 comments | 11 Nov 25 15:44 UTC | HN request time: 0.64s | source | bottom
1. catapart ◴[12 Nov 25 14:48 UTC] No.45900914[source]▶
Literally just started building a game engine with .NET 9, so naturally there's an update within a week. -_-

Seems like a good update, though! And I'm glad it's early enough that updating the framework probably shouldn't break anything. Really as long as there's no issues with the DearImGUI dependency (would be a surprise!), I'm pretty happy about the update.

replies(3): >>45900950 #>>45903664 #>>45907230 #
2. sumnole ◴[12 Nov 25 14:52 UTC] No.45900950[source]▶
I wouldn't worry. Updating .NET rarely breaks anything.
3. pixl97 ◴[12 Nov 25 18:16 UTC] No.45903664[source]▶
9 isn't an LTS version... always go with an LTS version.
replies(1): >>45905459 #
4. orphea ◴[12 Nov 25 19:53 UTC] No.45905459[source]▶
That's... a strong statement. There is absolutely nothing wrong with going with a non-LTS version. You just have to update a little bit sooner, and that's it.
replies(1): >>45905914 #
5. htgb ◴[12 Nov 25 20:19 UTC] No.45905914{3}[source]▶
Especially with the recent extension of STS release support from 18 to 24 months [1]. Previously, upgrading from an LTS version to the next major (STS) version meant the support window decreased by half a year, while now it would stay the same.

[1] https://devblogs.microsoft.com/dotnet/dotnet-sts-releases-su...

6. Kwpolska ◴[12 Nov 25 21:47 UTC] No.45907230[source]▶
For most projects, upgrading between .NET version is quick and painless, usually just updating the TargetFramework and NuGet packages in your .csproj file.