-
Notifications
You must be signed in to change notification settings - Fork 166
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
Is AsExpandable still necessary on EF Core? #100
Comments
Can you maybe create a example project to demonstrate this? |
I get this, too when I reference
|
I am running into the same problem with AsExpandable after converting to Net Core 3. As brunosantosrhsenso mentioned, removing AsExpandable works but want to make sure that's correct. |
If you want to use async. Then you need the LinqKit version which references EF or EFCore. See the table on main page from this project. Using Expandable on net core 3 : I have to check... |
@StefH |
@joshmouch and @206mph and @brunosantosrhsenso --> Please test. |
Preview works - Thanks @StefH |
|
Can confirm that preview 04 also works |
@StefH |
Same for me. Doesn't seem to be needed anymore... Is it? |
I can also confirm that PredicateBuilder is working without |
I can also confirm that PredicateBuilder is working without |
When trying to convert a Core 2.2 web app (EF 2.2) to Core 3 (EF 3.0), AsExpandable was throwing an exception "Could not load file System.Interactive.Async". I then removed AsExpandable and the query (using predicatebuilder) seemed to work just fine. I did the same with the Core 2.2 version, and it also seemed to have worked properly. So now I'm wondering if I'm missing some feature by removing AsExpandable or if it's just not necessary anymore.
The text was updated successfully, but these errors were encountered: