• TheCee@programming.dev
    2·
    1 year ago

    For me either:

    • Versioning and naming. Framework 4.8.0 -> works down to Windows Server 2012; Framework 4.8.1 -> whoops you need Server 2021. Why.
    • Bugs and regressions in its APIs and tools. Most are related to UI and accessibility as you probably guessed.
    • VS. It has been slow and bug-ridden for a long time now, but just recently I hit that bug where searching text doesn’t find all places. I might have hit it before, but how would you know. It also feels like its tools are sometimes worse than in its previous versions. Suggestions got worse, for sure. But that might come down to my other points.
    • Rather ad hoc, unfocussed language design and the problems that result. Better than many others, but still. Not learning (enough) from the past seems to be a common theme in PL design, but it sure doesn’t help that it isn’t an exact science.
    • Anything UI.
    • douglasg14b@programming.dev
      1·
      1 year ago

      TBH I wouldn’t recommend you be building applications in .Net Framework… Most complaints about it have been a solved problem for years with .Net Core/.Net 5+. And there are upgrade paths, at least if you aren’t maintaining WPF/Winforms

      Bugs and regressions? I wonder if that’s for different things than I touch, I’ve had almost no disruptions for the last 9 years. But I’ve mostly worked on console apps and backends. Almost no UI work aside from some WPF and Winforms side projects ages ago.

      • TheCee@programming.dev
        1·
        1 year ago

        Well, a migration wasn’t an option for our project. But I’ve been trying Windows Forms with .Net 6, but the experience wasn’t that great, either. And it was basic, first-five-minutes stuff like the form designer not opening.

        Microsoft might have announced the end of their own UI story just recently, but to me, it felt always half-assed.