Live data from Hacker News

.NET for Beginners (2020)

dusted.codes

191–192 of 192 posts

Re: .NET for Beginners (2020)

#191
post #160
post #104

Earlier quoted context omitted.

I appreciate the reply, and I will try that. However this sentence made me inadvertently laugh, because it captures every bit of confusion I had. > You install .NET 5 (for context, it's just a newer version of .NET Core with the naming realigned), and then write `dotnet new webapi` which will create a new ASP.NET Core API project.

> However this sentence made me inadvertently laugh, because it captures every bit of confusion I had Haha, for further context, .NET 5 is the SDK + runtime. ASP.NET Core is the default Web framework that includes a ton of out of the box functionality. I'd highly recommend taking a read of https://docs.microsoft.com/en-us/aspnet/core/introduction-to... , which links to the relevant tutorials for your scenario.

That's clears up a lot actually! Thx

Re: .NET for Beginners (2020)

#192

Earlier quoted context omitted.

Depends on why they would be learning C# I do most of what I do with C# in WSL with VS Code (WSL Remote) ... because that's where I do most of my Programming. Where I work, pushing towards most of what we write to be able to deploy/operate in Linux/Docker environments. Doesn't make C# less of a language for the teams that have over a decade of experience with C#, but it is a mindset shift. The bigger issues I have ar…

Per the last versions of .net vs .net core that I worked with (4.....6.2(?) and .net core who even knows), I definitely agree with the frustrations. That's a major reason why, when I answered the top question, I was responding in a way to reference a new developer. I don't think they should be required to think of all of that hell, so I just wanted to point them to a particular library and to just live with it until…

I'm relatively familiar with .Net (been using it since late 2001), that said, it's changed dramatically, more so in the past 3 years than nearly a decade before that. The changes between Framework 4.x to Core 1, 2, 3 have been somewhat dramatic and painful trying to keep one application current (that needed portability, including rpi). Hopefully the move to .Net 5 will be less painful.

I'm mostly playing devils advocate as it's not been a smooth transition and the best way to do many things has changed since some things are in the box, that didn't used to be, but still rough around some edges.

Many libraries and patters for web api projects are a bit different, better but different.

Post reply on HN