.NET 9

53 points by runesoerensen 8 months ago | 26 comments
  • balencpp 8 months ago
    .NET has come to be a very solid, performant, cross-platform, productive runtime. I always come back to it for most projects. Thanks to everyone involved!
    • orra 8 months ago
      Not an LTS, but a tempting upgrade what with the performance fixes.

      EF 9 has some good fixes, and even better, the better, works on .NET 8.

      • mikece 8 months ago
        At only three years the "LTS" releases aren't exactly "long term" either.
        • orra 8 months ago
          True, for a corporation it's not that long. But as a developer it's nice for there to be momentum for platform updates.

          I discovered last week that .NET Framework v3.5 is still technically supported. Shudder.

          • mikece 8 months ago
            Why shudder? Sure, devops to VMs instead of .NET Core containers isn't as nifty but there is something to be said for code that can run for 5+ years without needing to be touched. Zero-maintenance is a big selling point but right now MSFT is requiring us to update ALL of our code just to rev the version every 36 months (not counting security issues -- we lost more than two weeks of productivity eradicating the Newtonsoft exploit at my last company).
      • zigzag312 8 months ago
        I love that NativeAOT is making slow but steady progress through C# ecosystem.
        • pjmlp 8 months ago
          Better later than never, I was disappointed with NGEN capabilities, given the Delphi influences on .NET.

          Microsoft research had Sing#, System C#, which never came to us, Mono AOT had its issues, and finally Windows 8.x MDIL/Bartok, UWP .NET Native, which were still special cases.

          I always vouched the opinion that had .NET supported AOT properly since the beggining, there would have been much less people reaching out to C and C++, as one of the reasons was getting real executables (same applies to Java, and the issue AOT until recently being a commercial JDK feature for deep pockets).

          • nodra 8 months ago
            Is no generics with AOT the only catch?
            • zigzag312 8 months ago
              Generics do work with AOT.

              You can't generate new code at runtime (Reflection.Emit) with AOT.

              • nodra 7 months ago
                My wording was incorrect. My apologies. I meant open generics (List<T>)
              • neonsunset 8 months ago
                Why would generics not work with AOT?
                • nodra 7 months ago
                  I meant open generics. My wording was incomplete.
            • cjblomqvist 8 months ago
              Anyone knows how to/if it's possible to setup c# 13 with the new semi-auto property (field) feature?

              I know it's not part of "standard" c# 13 out-of-the-box

              • klauserc 7 months ago
                You have to set the C# language version to 'preview'.

                    <PropertyGroup>
       <LangVersion>preview</LangVersion>
    </PropertyGroup>
                • zigzag312 8 months ago
                  I saw one comment saying you have to enable language preview features. I haven't tried it myself.
                • moogly 8 months ago
                  Imagine if you could actually download it too. Why is it taking so long?
                  • DASD 8 months ago
                    Finally available.
                  • 8 months ago