It takes about 5 minutes to set up the dotnet CLI tools and get a "Hello World".
If you don't even want to spend that you can install Visual Studio and .NET Core stuff will just work out of the box, as is customary for VS.
Versioning and documentation is a mess, but neither you nor the grandparent seem to have actually made the minimal time investment necessary to even encounter those problems.
> Versioning and documentation is a mess, but neither you nor the grandparent seem to have actually made the minimal time investment necessary to even encounter those problems.
This is Microsoft's fault, not these guys, and it has pissed me off so many times over the years.
I always use the analogy that Microsoft builds these gigantic, beautiful mansions, but then to get to them you have to find the secret path that's covered in weeds.
A slightly different topic, but very much along the same theme:
What a mess! I want SSMS, do I even have it installed anymore? How do I clean this up without spending 6 hours (because I know something's going to go wrong during the uninstall)?
Yeah the problem isn't "hello world." It never is, it's building something with the tooling that works cross platform or that can be deployed to the platforms I want to target. That's much more than "hello world" and the important part.
Perhaps you could make a useful comment next time instead of something plainly not?
Well, you literally said that it was useless and that you gave up before you began. Given that, I'd say that revelation's comment was pretty useful - explaining how you could quickly and easily get up and running with .NET. Perhaps you could tone down the hyperbole next time?
If you don't even want to spend that you can install Visual Studio and .NET Core stuff will just work out of the box, as is customary for VS.
Versioning and documentation is a mess, but neither you nor the grandparent seem to have actually made the minimal time investment necessary to even encounter those problems.