EntityWorker.Core – An alternative to Entity Framworke
https://www.codeproject.com/Tips/1222424/EntityWorker-Core-An-Alternative-to-Entity-Framewo
https://www.codeproject.com/Tips/1222424/EntityWorker-Core-An-Alternative-to-Entity-Framewo
I rant, therefore I am.
EntityWorker.Core – An alternative to Entity Framworke
https://www.codeproject.com/Tips/1222424/EntityWorker-Core-An-Alternative-to-Entity-Framewo
https://www.codeproject.com/Tips/1222424/EntityWorker-Core-An-Alternative-to-Entity-Framewo
I know from LLBLGen and NHibernate how much effort goes into writing a really good .NET ORM layer, so I cannot really believe a just one year old library is so much better than Entity Framework.
Jeroen Wiert Pluimers I tend to agree, but older libs tend to balloon away from the original lean and mean. Sometimes less is more.
We use NHibernate for Continua CI, but use dapper for read only views where performance is critical. I wouldn’t use an orm again for another project. It was great at first, got the first 80% done very quickly, then spent a lot of time on that last 20% working around quirks, lack of doco on how things work, poor error messages, unfathomable sql etc. I’m working on a new product (dotnetcore based) and using dapper. Yes I have to write sql (for sqlserver and postgres) but life is so much simpler, and I know what sql is being run.