3 ms·
One problem with the c#/dotnet ecosystem is there are too many answers online for different versions c#, records, EF6, EF core, EF7, net4.8, net standard, net
by guilhas 4y ago
One problem with the c#/dotnet ecosystem is there are too many answers online for different versions
c#, records, EF6, EF core, EF7, net4.8, net standard, net core, net6, webforms, blazor, web api, web mvc, razor, identity core, legacy, UI, dotnet cli, visual studio, vscode, nuget, CMD, powershell...
- rjh29 4y agoWhat is better, too many options or barely any?
- guilhas 4y agoFor an experienced c#/.net it is OK, but new developers might get confused and go learn another language Nim looks very clean. But I am not sure it is ready for complex production work
- koenvdb 4y agoMost of the time the answers are interchangable. There are a few exceptions but then you just look for "Specific problem .Net6" for example.
- jackmott42 4y agoyou listed 3 versions of C# in that list, and they are all as similar as versions of any other language are.
- sebazzz 4y agoI bet you I'll love any library in Node.js or the ecosystem itself. That's significantly worse.