3 ms·
We use .NET core in production and are very happy. A mixture of EF Core (for ad-hoc queries) and Dapper (for stored procs) works just fine. Also, new in EF Core
by ajryan 8y ago
We use .NET core in production and are very happy. A mixture of EF Core (for ad-hoc queries) and Dapper (for stored procs) works just fine. Also, new in EF Core 2.1, you can map views and stored procs just fine: https://docs.microsoft.com/en-us/ef/core/modeling/query-types https://docs.microsoft.com/en-us/ef/core/modeling/query-type....
That's your only specific example - what other functionality are you missing?
You're not willing to commit to .NET core but you admit that NetFx is going into maintenance mode?
- wolfspider 8y agoYes, totally agree- I worked on a project that wasn't Core but regular MVC + EF and Dapper which surprisingly worked out well. Actually so well I started mentioning it as a feature but really was just too lazy to redo all the dapper stuff since it worked so well.
- thepp1983 8y agoBecause it is cross platform and isn't really used cross platform it is a pain in the arse. SQL Aliases don't work. So people have to put in registry hacks into C# code (YAY back to 2002). Loads of missing functionality (e.g. GeneratePassword is missing in aspnet core). It is just incomplete. .NET 1.0 was more together than ASP.NET core and that was in 2002. We've lost loads of functionality in the spurious benefit of it running on multiple platforms. I was developing ASP.NET on Linux 5 years ago. It is more churn and burn for the small amount of devs that use dotnet without Windows.