4 ms·
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'
by catapart 11mo ago
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.
- sumnole 11mo agoI wouldn't worry. Updating .NET rarely breaks anything.
- pixl97 11mo ago9 isn't an LTS version... always go with an LTS version.
- orphea 11mo agoThat'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.
- htgb 11mo agoEspecially 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-supported-for-24-months/ https://devblogs.microsoft.com/dotnet/dotnet-sts-releases-su...
- Kwpolska 11mo agoFor most projects, upgrading between .NET version is quick and painless, usually just updating the TargetFramework and NuGet packages in your .csproj file.