-
Notifications
You must be signed in to change notification settings - Fork 28
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
HierarchyId support #30
Comments
Hello @roamel , Thank you for reporting. We will look at it and merge this pull as well. I believe it should be available for next Monday. Best Regards, Jonathan |
Hello @roamel , The v7.0.39 has been released. Could you try it and let us know if everything is working for |
Hello @JonathanMagnan, I will look into this in few days Regards, |
Hello @JonathanMagnan I have tested the next versions: 7.0.39, 7.0.40 and 7.1.1 However, there is an issue with Bulk operations:
Stack Trace:
If we use
Model is the next (simplified):
Additionally, not sure is it related to the issue or not, we still use standard EF in parallel, because of Microsoft.AspNet.Identity.EntityFramework package. Standard EF and Z.Classic both uses the same assembly with models and each load dynamically created assembly with the same full qualified name: EntityFrameworkDynamicProxies-{assembly name here},1.0.0.0. This may be a cause of the issue, may be not, but 2 assemblies, with the same name, conflict each other during deserialization of proxies. I may suggest to use different assembly name for EntityFrameworkDynamicProxies in Z.Classic, like this: So, we have some progress with migarting to the library, but it still has some issue that would be good to resolve. Regards, |
Hello @roamel , You are right, we forget to add it in our EF Extensions library. I believe this request will be very easy (probably very similar to how we did it with SqlGeometry and SqlGeography). We also added a task with your suggestion for Dynamic Proxy. We will look at it and should be released this week as well if that's simple to implement. Best Regards, Jonathan |
Hello @roamel , The v7.1.2 has been released.
We will start to check about Dynamic Proxy very soon. |
Hello @JonathanMagnan
Regards, |
Hello @JonathanMagnan FYI: I have found that Update-Database powershel cmdlet does not work if EF context is based on Z.EntityFramework.Classic
To fix this static constructor of migration Configuration class can be used :
I know, that initially, Z.EntityFramework.Classic was positioned as replacement for standard EF6 and parallel usage of both libraries was not supported. But now, it looks possible and may help developers to use benefits of this approach. For instance, with packages that cannot be recompiled with Z.EntityFramework.Classic, like Microsoft.AspNet.Identity.EntityFramework. Best Regards, |
Yup it will for sure eventually be added in the doc, thank for sharing ;) |
Any news about Dynamic Proxy assembly name change? Regards, |
Hello @roamel , I modified the priority on this request. It seems the priority was very low so was keeping being delayed by other requests. I will contact you next Monday to give you an update about it. This request should be checked during the weekend and completed if possible. Best Regards, Jonathan |
Hello @roamel , The v7.1.3 has been released. We renamed the proxy class as you proposed. Let me know if some request is still remaining or we can close this issue. Best Regards, Jonathan |
Hello @roamel , We will close this issue, If there is anything else, feel free to comment it here or open a new issue. Best Regards, Jonathan |
Hello @JonathanMagnan |
Hello @JonathanMagnan the problem is that both of them used EF, and I cant use DbContext of Microsoft.AspNet.Identity.EntityFramework |
Hello @mshojaei , Please read the following page, it should help you: https://entityframework-classic.net/using-ef-classic-with-ef-6 |
Hello,
We have a license for EF Classic, but cannot migrate our code to it because of absent HierarchyId support.
It would be very helpful if HierachyId will be introduced. We used EF beta nightly build and everything is OK. More details here: dotnet/ef6@f905073.
Thanks, Roman
The text was updated successfully, but these errors were encountered: