Is the main benefit of using LLBLGEN with EF is that you get all of the extensive tooling that comes with LLBLGEN? Or in other words, LLBLGEN makes using EF more palatable?
Basically for using the full power of the LLBLGen Pro Designer.
So you can easily work on your entity model, reverse-engineering functionality (Database first) or Model first tools, or doing both at the same time. Also you can easily synchronize your entity model with the database schemas, define and validate your entity model or create derived models on top of them.
That's in a nutshell, but in general there is much more capabilities, that I suggest you start getting your hands dirty with it.
Is the main benefit of using LLBLGEN with EF is that you get all of the extensive tooling that comes with LLBLGEN? Or in other words, LLBLGEN makes using EF more palatable?
We believe there is much into LLBLGen Pro Framework than the other Frameworks.
Please check this out: https://www.llblgen.com/Pages/LLBLGenProRTF.aspx
And it's worth mentioning the performance benefits.
Please check some benchmarking findings here:
https://weblogs.asp.net/fbouma/net-micro-orm-fetch-benchmark-results-and-the-fine-details