3 ms·

Would you be able to share any pointers to an introduction to .NET Framework, that is fairly recent, but is still "boring"? The official docs seem to push Razor

by ttymck 3y ago

Would you be able to share any pointers to an introduction to .NET Framework, that is fairly recent, but is still "boring"? The official docs seem to push Razor/Blazor and that feels too cutting edge for my interest. In my opinion, it's hard to identify the best entrypoint to modern "boring" C# because of all the different subsystems: Core, Framework, ASP, etc

neonsunset 3y ago
.NET Framework should not be used for new projects unless absolutely necessary (IIRC MS Office Add-ins use it) because it is legacy, has (relatively) poor performance and will not receive any new features. C# and .NET (6/7/8) is what you may be looking for. The entrypoint for that would be the basics[0] (just pick in the left column whatever strikes your fancy, the official docs are good) and then if you are interested in back-end dev - ASP.NET Core[1]. [0] https://learn.microsoft.com/en-us/dotnet/csharp/tour-of-csharp/ https://learn.microsoft.com/en-us/dotnet/csharp/tour-of-csha... [1] https://learn.microsoft.com/en-us/aspnet/core/fundamentals/minimal-apis/overview https://learn.microsoft.com/en-us/aspnet/core/fundamentals/m... The rough overview of terms you have mentioned is as follows: .NET (6+) - the platform almost everything runs on, like OpenJDK but encompasses the standard library and certain nuget packages as well ASP.NET Core - main .NET's web framework for developing web applications like LOB CRUDs, gRPC-based microservices, etc. Doesn't really have alternatives that offer comparable performance/features ratio EF Core - main .NET's ORM framework, its popular alternative is Dapper which is more hands-on and focused on writing SQL code directly Notable mention: .NET Core used to be the name for .NET Core 1.x, 2.x, and 3.x version but was later on rebranded to just .NET. The version 4 was skipped to avoid confusion with .NET Framework 4.x which will live on forever by the nature of being included with Windows.
- romanhn 3y ago
  Doh, you're absolutely correct. I started with .NET back in 2003, so there's still quite a bit of baggage mixed in with the .NET team's terrible naming history. I would personally recommend .NET for backend work, as MS track record of UI frameworks is rather suspect. For the main project I currently support, using .NET 6 API and a React frontend (+EF Core to access a Postgres database). Works beautifully.

by ttymck 3y ago

neonsunset 3y ago

.NET Framework should not be used for new projects unless absolutely necessary (IIRC MS Office Add-ins use it) because it is legacy, has (relatively) poor performance and will not receive any new features. C# and .NET (6/7/8) is what you may be looking for. The entrypoint for that would be the basics[0] (just pick in the left column whatever strikes your fancy, the official docs are good) and then if you are interested in back-end dev - ASP.NET Core[1]. [0] https://learn.microsoft.com/en-us/dotnet/csharp/tour-of-csharp/ https://learn.microsoft.com/en-us/dotnet/csharp/tour-of-csha... [1] https://learn.microsoft.com/en-us/aspnet/core/fundamentals/minimal-apis/overview https://learn.microsoft.com/en-us/aspnet/core/fundamentals/m... The rough overview of terms you have mentioned is as follows: .NET (6+) - the platform almost everything runs on, like OpenJDK but encompasses the standard library and certain nuget packages as well ASP.NET Core - main .NET's web framework for developing web applications like LOB CRUDs, gRPC-based microservices, etc. Doesn't really have alternatives that offer comparable performance/features ratio EF Core - main .NET's ORM framework, its popular alternative is Dapper which is more hands-on and focused on writing SQL code directly Notable mention: .NET Core used to be the name for .NET Core 1.x, 2.x, and 3.x version but was later on rebranded to just .NET. The version 4 was skipped to avoid confusion with .NET Framework 4.x which will live on forever by the nature of being included with Windows.

romanhn 3y ago
Doh, you're absolutely correct. I started with .NET back in 2003, so there's still quite a bit of baggage mixed in with the .NET team's terrible naming history. I would personally recommend .NET for backend work, as MS track record of UI frameworks is rather suspect. For the main project I currently support, using .NET 6 API and a React frontend (+EF Core to access a Postgres database). Works beautifully.