-
Notifications
You must be signed in to change notification settings - Fork 3.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Exception using LazyLoading When sharing same .Net Type among multiple owned types #11972
Labels
Comments
ajcvickers
added a commit
that referenced
this issue
May 12, 2018
Fixes #11972 The fix is to allow proxies (derived types) in the optimization check.
@amilarox1 Thanks for filing this. Turns out it was a duplicate of the same root cause, so closing this as a duplicate of the original issue (but using your title for that one!) |
ajcvickers
added a commit
that referenced
this issue
May 12, 2018
Fixes #11972 The fix is to allow proxies (derived types) in the optimization check.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Steps to reproduce
Please take a look at the solution in the following repo.
https://github.com/amilarox1/OwnedTypes
The solution has two projects. OwnedTypes & OwnedTypes.NotWorking
OwnedTypes.NotWorking project is using
Microsoft.EntityFrameworkCore.Proxies 2.1.0-rc1
and all the navigation properties are virtual (including owned types) and this causes the above exception when queriying data from the database.Please check the ReadMe.md in the repo for more information
Further technical details
EF Core version: 2.1.0-rc1
Database Provider: SqlServer 2.1.0-rc1
Operating system: Win10
IDE: Visual Studio 2017 15.6.6
The text was updated successfully, but these errors were encountered: