4 ms·

I agree with all of the above. I love C# as a language having used it in Unity in the past. I wanted to try to a server backend with it, but I was lost as to w

by syspec 5y ago

I agree with all of the above. I love C# as a language having used it in Unity in the past. I wanted to try to a server backend with it, but I was lost as to which framework to use (ASP.net / .NET Core / .Net 5) so I ended up choosing neither. Which is a shame, because I really really like the language

wvenable 5y ago
The framework you choose doesn't even matter that much. You're unlikely to even a notice a difference and changing from one to another is often as easily as selecting it from a drop-down (or editing a file) and recompiling. Yes, you can get into situations where something you're doing needs one or the other but it's very rare.
- syspec 5y ago
  I'm sure you're right, but as a beginner in a new programming language there is a real fear of "choosing the wrong thing" You know that it will not matter that much, because you're familiar enough with all three. A beginner doesn't have that information. Think about it like this: Is it better for beginners to have such a 'non-choice'? Or is it better for them to be presented 1 maybe 2 options and say pick from these 2 these are the differences?
  - wvenable 5y ago
    If you start a project in the IDE (or even the command line) there is already a default selected for you. Whatever that default is, would be fine. I don't think there's a single .NET tutorial out there that has you explicitly select the framework. The problem is you're informed enough to ask the question! If you had no idea about the different frameworks you wouldn't have a problem.
Hawxy 5y ago
> I wanted to try to a server backend with it, but I was lost as to which framework to use (ASP.net / .NET Core / .Net 5) so I ended up choosing neither. The new C# tutorials have solved a lot of this issue just by completely skipping over the legacy parts of .NET (.NET Framework & ASP.NET) and using the CLI to create a new project. 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.
- syspec 5y ago
  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.
  - Hawxy 5y ago
    > 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-aspnet-core?view=aspnetcore-5.0 https://docs.microsoft.com/en-us/aspnet/core/introduction-to..., which links to the relevant tutorials for your scenario.
    - syspec 5y ago
      That's clears up a lot actually! Thx
tester34 5y ago
Just install newest .NET 5 and type `dotnet new mvc` or `dotnet new webapi`

by syspec 5y ago

wvenable 5y ago

The framework you choose doesn't even matter that much. You're unlikely to even a notice a difference and changing from one to another is often as easily as selecting it from a drop-down (or editing a file) and recompiling. Yes, you can get into situations where something you're doing needs one or the other but it's very rare.

syspec 5y ago
I'm sure you're right, but as a beginner in a new programming language there is a real fear of "choosing the wrong thing" You know that it will not matter that much, because you're familiar enough with all three. A beginner doesn't have that information. Think about it like this: Is it better for beginners to have such a 'non-choice'? Or is it better for them to be presented 1 maybe 2 options and say pick from these 2 these are the differences?
- wvenable 5y ago
  If you start a project in the IDE (or even the command line) there is already a default selected for you. Whatever that default is, would be fine. I don't think there's a single .NET tutorial out there that has you explicitly select the framework. The problem is you're informed enough to ask the question! If you had no idea about the different frameworks you wouldn't have a problem.

Hawxy 5y ago

> I wanted to try to a server backend with it, but I was lost as to which framework to use (ASP.net / .NET Core / .Net 5) so I ended up choosing neither. The new C# tutorials have solved a lot of this issue just by completely skipping over the legacy parts of .NET (.NET Framework & ASP.NET) and using the CLI to create a new project. 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.

syspec 5y ago
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.
- Hawxy 5y ago
  > 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-aspnet-core?view=aspnetcore-5.0 https://docs.microsoft.com/en-us/aspnet/core/introduction-to..., which links to the relevant tutorials for your scenario.
  - syspec 5y ago
    That's clears up a lot actually! Thx

tester34 5y ago

Just install newest .NET 5 and type `dotnet new mvc` or `dotnet new webapi`