3 ms·

Not sure why you're being downvoted, as these are real pain points. As other comments have pointed out, .NET rebranding sucks and is confusing (like .NET Core,

Not sure why you're being downvoted, as these are real pain points. As other comments have pointed out, .NET rebranding sucks and is confusing (like .NET Core, .NET Standard, etc.). And the questions around the GUI toolkits don't help. WinForms is the only thing that is (still) consistently developed - kind of.

smcl 5y ago
I do not think it is an issue about (re)branding. Each of those things that people refer to as confusing (.NET Framework, .NET Core, .NET Standard and now standalone .NET) are distinct and separate parts. I think it's more that .NET spent the best part of its existence Windows-only and to transition to being cross-platform requires some hefty changes that necessitated clearly defined stages (windows-only .NET Framework, then early-stage-cross-platform .NET Core 1/2/3 and then end-result .NET 5/6+) and a clear way to write library code targetted such that it can be used by certain cross-sections of those stages (.NET Standard). They've managed the transition well on the technical side of things - as you can see there are plenty of people who are happy with the end result. But it's clear from comments that pop up here that they've really missed the mark when it comes to actually describing the intent behind the whole project, because a surprising number regard it as just an unnecessary exercise in rebranding.
foepys 5y ago
The WinForms repo is actually also quite dead. There are fixes here and there are but no major things in the horizon. Apparently they want to focus their efforts on MAUI and WinUI, both of which are not even close to production ready.
- bartwe 5y ago
  That has been a consistent pattern in .net, where the liked current tech withers on the vine to make place for the new thing. Instead of the new thing proving itself organically.
ozim 5y ago
I don't agree that these are real pain points. Try to build desktop app in Ruby or in Python, no one cares about desktop apps. If you want to build native desktop apps you go with QT or something C++ based. .NET branding being confusing is a theoretical problem. When you work day to day with the code you don't care and it does not affect anything I work on. It is not like it somehow affects compilation or some of my code stops working. I use .NET 4.8, .NET standard and .NET Core and now .NET 6 in projects and no problems there.
- DeathArrow 5y ago
  >no one cares about desktop apps I take it you never used Photoshop, 3D Max, Autocad, Word, Excel, Visual Studio, Paint or Notepad.
  - ozim 5y ago
    Word and Excel already moved to browser editions not to mention Google productivity tools. Check out web.autocad.com There are more and more painting tools available online. Cloud based IDEs are popping up more frequently. Not to forget about all web based note apps. That is the trend and no one cares about creating next Photoshop or Autocad competition on desktop. Let alone that I mentioned that if someone cares about building desktop app he goes with C++ and QT or something like that and not .NET or Ruby or Python.
DeathArrow 5y ago
> .NET rebranding sucks and is confusing (like .NET Core, .NET Standard We have no more CORE, just .NET. >And the questions around the GUI toolkits don't help. WinForms is the only thing that is (still) consistently developed - kind of. MAUI is going to be released soon.

smcl 5y ago

I do not think it is an issue about (re)branding. Each of those things that people refer to as confusing (.NET Framework, .NET Core, .NET Standard and now standalone .NET) are distinct and separate parts. I think it's more that .NET spent the best part of its existence Windows-only and to transition to being cross-platform requires some hefty changes that necessitated clearly defined stages (windows-only .NET Framework, then early-stage-cross-platform .NET Core 1/2/3 and then end-result .NET 5/6+) and a clear way to write library code targetted such that it can be used by certain cross-sections of those stages (.NET Standard). They've managed the transition well on the technical side of things - as you can see there are plenty of people who are happy with the end result. But it's clear from comments that pop up here that they've really missed the mark when it comes to actually describing the intent behind the whole project, because a surprising number regard it as just an unnecessary exercise in rebranding.

foepys 5y ago

The WinForms repo is actually also quite dead. There are fixes here and there are but no major things in the horizon. Apparently they want to focus their efforts on MAUI and WinUI, both of which are not even close to production ready.

bartwe 5y ago
That has been a consistent pattern in .net, where the liked current tech withers on the vine to make place for the new thing. Instead of the new thing proving itself organically.

ozim 5y ago

I don't agree that these are real pain points. Try to build desktop app in Ruby or in Python, no one cares about desktop apps. If you want to build native desktop apps you go with QT or something C++ based. .NET branding being confusing is a theoretical problem. When you work day to day with the code you don't care and it does not affect anything I work on. It is not like it somehow affects compilation or some of my code stops working. I use .NET 4.8, .NET standard and .NET Core and now .NET 6 in projects and no problems there.

DeathArrow 5y ago
>no one cares about desktop apps I take it you never used Photoshop, 3D Max, Autocad, Word, Excel, Visual Studio, Paint or Notepad.
- ozim 5y ago
  Word and Excel already moved to browser editions not to mention Google productivity tools. Check out web.autocad.com There are more and more painting tools available online. Cloud based IDEs are popping up more frequently. Not to forget about all web based note apps. That is the trend and no one cares about creating next Photoshop or Autocad competition on desktop. Let alone that I mentioned that if someone cares about building desktop app he goes with C++ and QT or something like that and not .NET or Ruby or Python.

DeathArrow 5y ago

> .NET rebranding sucks and is confusing (like .NET Core, .NET Standard We have no more CORE, just .NET. >And the questions around the GUI toolkits don't help. WinForms is the only thing that is (still) consistently developed - kind of. MAUI is going to be released soon.