You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Suggested workaround is currently to not use classes for projections in LightQuery that derive from the class used in the DbContext. Best practice would be to completely separate classes used in EntityFramework and ViewModels or Data Transfer Objects (DTOs).
The text was updated successfully, but these errors were encountered:
See this issue in the EF Core repo: dotnet/efcore#18386
Suggested workaround is currently to not use classes for projections in LightQuery that derive from the class used in the
DbContext
. Best practice would be to completely separate classes used in EntityFramework and ViewModels or Data Transfer Objects (DTOs).The text was updated successfully, but these errors were encountered: