-
Notifications
You must be signed in to change notification settings - Fork 63
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
Project dead? #35
Comments
No, not dead. Yes, we plan to support ASP.NET Core. |
Out of curiosity, Do you have a timeline for supporting .NET core? |
No timeline as of this moment. |
any news? |
It is being worked on at this moment. Expect something in February. |
Working on it, should have full ASP.NET Core support within two weeks. Most of the code is complete, refactoring, packaging and final testing now. No longer has an OData dependency, but still offers all of the same capabilities. |
Two weeks are over :) I am desperately waiting for .net core release. |
I've tested the code in an AspNet Core aplication and works well, at least sorting and pagination, filtering has some issues but not from Breeze, its EntityFramework Core fault. I think its almost ready like @jtraband said, but if you are desperated like me, copy/paste the files :) |
@jtraband - I am trying to migrate a WebAPI 2/EF6 application which contains a breeze controller to .Net Core/Entity Framework core. Is there a version of breeze server which supports .Net Core (not requiring the full framework - I am using TargetFramework=netcoreapp1.1) and EF Core? If not do you have any suggestions on a migration plan? |
Any progress? How do I make Breeze work with ASP.NET Core 1.1 and EF6? |
It's all out there, just found it here You guys are awesome! |
What about EFCore 2.0 support? |
Is the project dead?
Are there any plans to support the new asp.net core?
The text was updated successfully, but these errors were encountered: