3 ms·
The main pain points for me regarding .NET Core has been the lack of third party libraries, hard to understand sometimes which project can run on .NET Core and
by staticelf 8y ago
The main pain points for me regarding .NET Core has been the lack of third party libraries, hard to understand sometimes which project can run on .NET Core and several cases that I had to switch back for smaller projects in order to use a specific library.
.NET Core is great, but I would continue to run it on .NET Framework for now.
- hoffs 8y agoWhat kind of libraries are you missing?
- junto 8y agoMost of the key Nuget packages we regularly use do target .NetStandard, so can be used in .Net Core: - Autofac - Automapper - EntityFramework Core - MassTransit - MediatR - Moq - Newtonsoft.Json - NodaTime - NUnit - Quartz.Net - RabbitMq.Client - RestSharp - Serilog The only thing we use .NET Framework applications for is Windows services through our use of TopShelf since it does all the heavy lifting surrounding windows service's lifetime management. All our other apps are .NET Core though. We build a lot of CQRS / DDD style applications, and the above list covers us off pretty well for our architecture that uses RabbitMq for messaging. Would be interested to know which packages you are missing?
- pjmlp 8y agoOn my case, ODP.NET is the big show stopper. So far, Oracle only bothered to port a subset to their .NET Core managed driver. However there are some features like UDT, distributed transactions and specific cipher modes that are only available on the native driver. Due to this, I have already done a .NET => Java port of a server application, because the customer required migration to UNIX servers and the JDBC driver had 100% feature parity with what we required. Switching to other RDMS is not an option on Oracle heavy enterprise shops, it has plenty of nice features at scale and UI tooling.