Hello,
For a simple try to get a data for dashboard, I always got this error with EF 3.1.
A simple stored procedure called from Dapper is ok.
Do you think there is an issue to use Dapper inside ServerMethodsController ?
By the way, I had my csproj file overwritten by Radzen despite the ignore list. What I did is inserting the System.SqlClient reference directly to the XML file of csproj for it to be kept.
Regards!
Do you think there is an issue to use Dapper inside ServerMethodsController ?
No. The ServerMethodsController is a normal ASP.NET Core MVC controller. Nothing Radzen related there.
By the way, I had my csproj file overwritten by Radzen despite the ignore list.
Check if the path specified in the ignore list is correct.
It's a problem in EF 3.1
This is a known limitation in EF Core, that stems from the very different concepts between LINQs GroupBy() and SQLs GROUP BY .
See Group By on MSDN for further details.
If this worked in 2.2, it is because EF Core 2.2 implicitly uses client evaluation as a fallback mechanism, if it cannot generate an appropriate query, while EF Core 3.0 does not.