Question: Breeze with .NET Core, EF Core #178

Davidvlv · 2016-12-12T03:36:42Z

Hi,

I'm trying to use Breeze with ASP.NET Core and Entity Framework Core, is this supported?
Or can I use Breeze with .NET Core and EF 6?

Thanks

steveschmitt · 2017-02-06T18:11:42Z

.NET Core + EF6 support is in progress (should be in beta by end of February). EF Core will come later, as it is still missing a few features.

badre429 · 2017-02-22T10:02:15Z

any time line

senseiweb · 2017-03-08T04:12:52Z

Doing a pulse check...any update on the beta

jtraband · 2017-03-08T04:43:51Z

I will be putting out a beta later this week of ASP .NET Core + EF6. Got it working now, just packaging it into nugets.

nigel-dewar · 2017-03-09T01:12:41Z

Im super excited to have a play with the beta. Awesome work

badre429 · 2017-03-09T01:26:34Z

@nigel-dewar where is it
i can't find a build on nuget ?

jtraband · 2017-03-09T01:37:48Z

I haven't released it yet. Working on it now.

steveschmitt · 2017-03-09T01:39:40Z

Not on nuget yet. If you want to try it right now, you will need to download and build it yourself.

jtraband · 2017-03-09T19:57:51Z

Ok, new nugets to support ASP.NET core and EF6 are now available. I am still working on samples to show how this all works but if you want to try without them... The nugets are Breeze.Server.Core, Breeze.Server.Persistence, Breeze.Server.Persistence.EF6 and Breeze.Server.AspNetCore.NetFramework as well as a composite nuget ( which is the easiest to use) called Breeze.Composite.AspNetCore.EF6. If you want to see an example solution , take a look at the Breeze.AspNetCore,InternalTest.sln in the breeze.server.net repo. (This solution is really only intended for internal use and has a number of specific dependencies that may not be obvious so I would just use this to look at the asp.net core setup.)

All of our internals tests work with these new dlls, the only caveat is that you will need to configure the breeze client to use the 'json' uri builder.

breeze.core.config.initializeAdapterInstance("uriBuilder", "json");

These new assemblies no longer have any dependencies on OData ( but still provide all of the same functionality) and there is no need for any client side OData javascript libraries either, assuming you set the adapter as shown above.

Hope this helps.

nigel-dewar · 2017-03-09T21:25:47Z

Awesome work mate I'm going to give this a crack today! Thanks for all your work!

senseiweb · 2017-03-09T21:43:55Z

I definitely second that -- thanks for the hard work guys!!

badre429 · 2017-03-10T20:56:06Z

Finaly its on nuget
thank you and can't wait for ef.core support

jtraband · 2017-03-10T21:00:06Z

We would be willing to do EF core now, if it wasn't currently so constrained. Many of the most useful parts of EF6 are not yet available in EF Core. We do plan to add support once many of these are in place. MS has a roadmap of these improvements, but no definite timetable yet. And they have even said that for most scenarios that you should probably stick with EF6 until these are released.

khuzemakanore · 2017-03-21T18:09:34Z

When I install Breeze.Composite.AspNetCore.NetFramework in .NetCore WebApi project. Its gives me error Package EntityFramework 6.0.0 is not compatible with netcoreapp1.1.

Any solution ?

Thanks

jtraband · 2017-03-21T18:17:01Z

Note sure if this is the issue, but there are two versions of 'ASP.NET core'. One based on the full .NET Framework and the other based just on .NET core. The 'Breeze.Composite.AspNetCore.NetFramework' needs the version that is based on the full .NET Framework. (Hence the .NetFramework suffix). We will be doing a 'Breeze.Composite.AspNetCore.NetCore' lib once MS makes more progress on EF Core, which does not yet support many of the features that Breeze supports. MS has committed to these changes but no timetable yet.

badre429 · 2017-03-21T18:18:20Z

@khuzemakanore your project is targeting dotnet core 1.1 you have to torget the full framework in order to user EF 6
therefore you have to change *.csproj
you have to replace

 <PropertyGroup>
     <TargetFramework>netcoreapp1.1</TargetFramework> 
  </PropertyGroup>

by

 <PropertyGroup>
     <TargetFramework>net461</TargetFramework>
    <RuntimeIdentifier>win7-x64</RuntimeIdentifier>
  </PropertyGroup>

khuzemakanore · 2017-03-21T18:19:40Z

The 'Breeze.Composite.AspNetCore.NetFramework' needs the version that is based on the full .NET Framework. (Hence the .NetFramework suffix).

Thanks. Yes its works with the full .Net Framework version.

bnemetchek · 2017-04-10T16:52:12Z

With this new implementation, where oData is not longer required, would it be possible to configure that regular queries are sent with a POST instead of a GET?

marcelgood · 2017-04-10T17:19:16Z

@bnemetchek That's been possible all along. The support for POST is not part of Breeze out of the box, but can be added via breeze.ajaxpost.js from Breeze Labs. Play the script after Breeze or import it and see the comments at the top for how to send a query with a POST.

https://github.com/Breeze/breeze.js.labs/blob/master/breeze.ajaxpost.js

bnemetchek · 2017-04-10T17:25:29Z

marcelgood, thanks, I'm familiar with that and use it for several custom queries. However, what I'm asking about is whether breeze filter queries can be sent with POST vs GET. i.e., oData filter queries

marcelgood · 2017-04-10T17:29:23Z

@bnemetchek The same mechanism should work for any query. Breeze won't put the query arguments in the body, though, they will still be part of the URL.

bnemetchek · 2017-04-10T18:20:41Z

@marcelgood. I understand that. My dilemma is that I occasionally have very long URL's. My solution is likely to refactor. It would be convenient, perhaps in the future, to have some mechanism whereby they queries were send as POST parms and interpreted on the server as an oData filter.

I apologize for hijacking this thread. I'll stop now. :)

WisdomCorp · 2017-04-15T14:13:59Z

Can we have a sample project or skeleton project to start with Asp.Net Core

Thanks

nigel-dewar · 2017-04-23T02:36:39Z

Really do need a basic asp.net core sample please. Even if just very very basic. And even if using the full .net framework is fine, just need something to see how the bits fit together.

Had another look in tests, and just too much stuff in there to know where to start.

Please.

marcelgood · 2017-04-23T03:11:24Z

I'm getting started on adding an asp.net core back-end to the temphire.angular sample, but I can't give you a timeframe yet.

nigel-dewar · 2017-04-23T06:04:46Z

Oh sweet Marcel, cheers mate looking forward to it. Really appreciate it, i know you guys are real busy with alot on.

nebffa · 2017-04-29T13:18:13Z

I'd like to add my voice to those requesting an ASP.NET core sample - Breeze is great and I'd like to use it with a couple of ASP.NET core projects at work.

nigel-dewar · 2017-05-19T05:42:49Z

Yo YO, just pinging to see if any movement on this?

Cheers.

marcelgood · 2017-05-19T06:32:17Z

Unfortunately, we've been busy with consulting projects. I'm still trying to get to it.

nigel-dewar · 2017-05-20T23:31:50Z

No worries mate, understand. Ill have another dig in the tests folder in the core repo and see if I can dig out the specifics I need. Cheers Nige

…

________________________________ From: Marcel Good <notifications@github.com> Sent: Friday, 19 May 2017 6:32 p.m. To: Breeze/breeze.js Cc: nigel-dewar; Mention Subject: Re: [Breeze/breeze.js] Question: Breeze with .NET Core, EF Core (#178) Unfortunately, we've been busy with consulting projects. I'm still trying to get to it. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub<#178 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AI94WBW5PkpmyGnPrbU4Bw9yet6HeuMtks5r7TdygaJpZM4LKJ-h>.

markarnolditpro · 2017-06-13T19:38:56Z

With the release of EF Core 2 Preview at Build does it look like you've got the features you need to begin work on EF Core support?

nigel-dewar · 2017-06-13T20:12:45Z

Yo Mark, breeze team already have it, we just waiting on a sample/starter repo. Sent from Samsung Mobile

…

-------- Original message -------- From: Mark Date:14/06/2017 05:39 (GMT+10:00) To: "Breeze/breeze.js" Cc: nigel-dewar , Mention Subject: Re: [Breeze/breeze.js] Question: Breeze with .NET Core, EF Core (#178) With the release of EF Core 2 Preview at Build does it look like you've got the features you need to begin work on EF Core support? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub<#178 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AI94WF9t23HAc-Wa0-uRV-SLME62Ui5Oks5sDuVTgaJpZM4LKJ-h>.

markarnolditpro · 2017-06-13T20:35:51Z

My understanding is that what's available now is support for ASP.Net Core compiled against .Net Framework and EF 6.

…

_____________________________ From: nigel-dewar <notifications@github.com<mailto:notifications@github.com>> Sent: Tuesday, June 13, 2017 4:12 PM Subject: Re: [Breeze/breeze.js] Question: Breeze with .NET Core, EF Core (#178) To: Breeze/breeze.js <breeze.js@noreply.github.com<mailto:breeze.js@noreply.github.com>> Cc: Mark <markarnolditpro@gmail.com<mailto:markarnolditpro@gmail.com>>, Comment <comment@noreply.github.com<mailto:comment@noreply.github.com>> Yo Mark, breeze team already have it, we just waiting on a sample/starter repo. Sent from Samsung Mobile

-------- Original message -------- From: Mark Date:14/06/2017 05:39 (GMT+10:00) To: "Breeze/breeze.js" Cc: nigel-dewar , Mention Subject: Re: [Breeze/breeze.js] Question: Breeze with .NET Core, EF Core (#178) With the release of EF Core 2 Preview at Build does it look like you've got the features you need to begin work on EF Core support? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub<#178 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AI94WF9t23HAc-Wa0-uRV-SLME62Ui5Oks5sDuVTgaJpZM4LKJ-h>. — You are receiving this because you commented. Reply to this email directly, view it on GitHub<#178 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AKdfKxgzmTZk6Bbg8EA2XrJbDdCx1sGtks5sDu1BgaJpZM4LKJ-h>.

nigel-dewar · 2017-06-13T20:37:49Z

Hahaha true that! Sent from Samsung Mobile

…

-------- Original message -------- From: Mark Date:14/06/2017 06:36 (GMT+10:00) To: "Breeze/breeze.js" Cc: nigel-dewar , Mention Subject: Re: [Breeze/breeze.js] Question: Breeze with .NET Core, EF Core (#178) My understanding is that what's available now is support for <http://as.net> <http://asp.net> <http://asp.net> <http://asp.net> <http://asp.net> <http://asp.net> A<http://asp.net>sp<http://asp.net><http://asp.net><http://asp.net><http://asp.net><http://asp.net><http://asp.net>.Net<http://asp.net> Core compiled against .Net Framework and EF 6.

_____________________________ From: nigel-dewar <notifications@github.com<mailto:notifications@github.com>> Sent: Tuesday, June 13, 2017 4:12 PM Subject: Re: [Breeze/breeze.js] Question: Breeze with .NET Core, EF Core (#178) To: Breeze/breeze.js <breeze.js@noreply.github.com<mailto:breeze.js@noreply.github.com>> Cc: Mark <markarnolditpro@gmail.com<mailto:markarnolditpro@gmail.com>>, Comment <comment@noreply.github.com<mailto:comment@noreply.github.com>> Yo Mark, breeze team already have it, we just waiting on a sample/starter repo. Sent from Samsung Mobile

-------- Original message -------- From: Mark Date:14/06/2017 05:39 (GMT+10:00) To: "Breeze/breeze.js" Cc: nigel-dewar , Mention Subject: Re: [Breeze/breeze.js] Question: Breeze with .NET Core, EF Core (#178) With the release of EF Core 2 Preview at Build does it look like you've got the features you need to begin work on EF Core support? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub<#178 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AI94WF9t23HAc-Wa0-uRV-SLME62Ui5Oks5sDuVTgaJpZM4LKJ-h>. — You are receiving this because you commented. Reply to this email directly, view it on GitHub<#178 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AKdfKxgzmTZk6Bbg8EA2XrJbDdCx1sGtks5sDu1BgaJpZM4LKJ-h>. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub<#178 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AI94WJUwo4xOZiauSH9oPsXUpJgj7CSwks5sDvKrgaJpZM4LKJ-h>.

bnemetchek · 2017-06-14T23:13:05Z

I am attempting to test this new functionality as per the instructions. It would seem that the where clause can no longer include oData functions as per [http://breeze.github.io/doc-js/api-docs/classes/EntityQuery.html#method_where]

christophwille · 2017-07-26T12:12:56Z

EF Core vs ASP.NET Core + EF6 is intermixed in this thread, but seems that the "no to EF Core" in the first reply by @steveschmitt was for 1.1, and the post on EF Core 2 Preview didn't garner any replies - so, would EF Core 2 be fit for Breeze Server? Or is it still not good enough?

ganySA · 2017-08-14T10:06:50Z

@marcelgood hope you are well...

Just a quick question is there a working version of Breeze + EF on .net core 1.1 the thread is a bit confusing... referring to .net 4.6

What packages need to be installed? or is it still WIP

Thanks.

nigel-dewar · 2017-08-17T02:57:18Z

Yo @ganySA ,

Im up and running with breeze and .net core. Just follow instructions found here Breeze/breeze.server.net#58 and you will be sweeeeeet!

josundt · 2017-11-24T09:06:47Z

Any news on EFCore 2.0 support?

mikemichaelis · 2018-02-22T18:59:40Z

I have all of this working in dotnet core 2.0.....ef core + webapi core + breezejs core + dotnet-cli + ef-cli

https://github.com/mikemichaelis/dnc

My persistence layer is SQL Server 2017 running in a Linux Docker container. See ya Windows........

plwade · 2018-11-27T15:25:56Z

@marcelgood Can you point me in the direction of the temphire angular sample working with the asp.net core back-end?
Any help appreciated

I'm getting started on adding an asp.net core back-end to the temphire.angular sample, but I can't give you a timeframe yet.

plwade · 2018-11-27T15:29:58Z

I have all of this working in dotnet core 2.0.....ef core + webapi core + breezejs core + dotnet-cli + ef-cli

https://github.com/mikemichaelis/dnc

My persistence layer is SQL Server 2017 running in a Linux Docker container. See ya Windows........

@mikemichaelis I can't seem to get your dnc backend working with my Angular/Breeze app. Have you got a sample app you could share?
Thank You

weitzhandler mentioned this issue Jun 28, 2017

Project dead? Breeze/breeze.server.net#35

Closed

tim-martens mentioned this issue Jul 19, 2017

Please help with brief steps to get ASP.Net Core breeze server up Breeze/breeze.server.net#58

Open

wijnsema mentioned this issue Aug 14, 2017

Using Breeze in Core web application targeting Full Framework Breeze/breeze.server.net#45

Closed

This was referenced Aug 30, 2017

Support for OData on ASP.Net Core #201

Closed

Support for OData on ASP.Net Core Breeze/breeze.server.net#60

Closed

Question: Breeze with .NET Core, EF Core #178

Question: Breeze with .NET Core, EF Core #178

Comments

Davidvlv commented Dec 12, 2016

steveschmitt commented Feb 6, 2017

badre429 commented Feb 22, 2017

senseiweb commented Mar 8, 2017

jtraband commented Mar 8, 2017

nigel-dewar commented Mar 9, 2017

badre429 commented Mar 9, 2017

jtraband commented Mar 9, 2017

steveschmitt commented Mar 9, 2017

jtraband commented Mar 9, 2017

nigel-dewar commented Mar 9, 2017

senseiweb commented Mar 9, 2017 • edited Loading

badre429 commented Mar 10, 2017

jtraband commented Mar 10, 2017

khuzemakanore commented Mar 21, 2017

jtraband commented Mar 21, 2017 • edited Loading

badre429 commented Mar 21, 2017 • edited Loading

khuzemakanore commented Mar 21, 2017

bnemetchek commented Apr 10, 2017

marcelgood commented Apr 10, 2017

bnemetchek commented Apr 10, 2017

marcelgood commented Apr 10, 2017

bnemetchek commented Apr 10, 2017

WisdomCorp commented Apr 15, 2017

nigel-dewar commented Apr 23, 2017 • edited Loading

marcelgood commented Apr 23, 2017

nigel-dewar commented Apr 23, 2017

nebffa commented Apr 29, 2017

nigel-dewar commented May 19, 2017

marcelgood commented May 19, 2017

nigel-dewar commented May 20, 2017 via email

markarnolditpro commented Jun 13, 2017

nigel-dewar commented Jun 13, 2017 via email

markarnolditpro commented Jun 13, 2017 via email • edited Loading

nigel-dewar commented Jun 13, 2017 via email

bnemetchek commented Jun 14, 2017 • edited Loading

christophwille commented Jul 26, 2017

ganySA commented Aug 14, 2017

nigel-dewar commented Aug 17, 2017

josundt commented Nov 24, 2017

mikemichaelis commented Feb 22, 2018

plwade commented Nov 27, 2018

plwade commented Nov 27, 2018

senseiweb commented Mar 9, 2017 •

edited

Loading

jtraband commented Mar 21, 2017 •

edited

Loading

badre429 commented Mar 21, 2017 •

edited

Loading

nigel-dewar commented Apr 23, 2017 •

edited

Loading

markarnolditpro commented Jun 13, 2017 via email •

edited

Loading

bnemetchek commented Jun 14, 2017 •

edited

Loading