Seperate out EFContextProvider
I would like to start out by saying nice job on breeze. You guys have a breeze mvc webapi dll for those people doing .net. I really like the EFContextProvider, but I think it would be cool if it was a seperate project. This would allow users to use it in different class libraries to create repositories and a unit of work for the different models that you create and have one place to manage it. Keep it breezy, thanks
Completed in Breeze 1.4.2.
When will the Breeze.EFModel package be available.
Cant make the workaround work I get a 'Breeze' could not be found error
I've tried to add the Breeze.WebApi2.dll to a seperate project
Rick van Lieshout commented
I'd suggest the documentation gets updated so it reflects this.
Vernon Laskey commented
Great idea!!! For now I am simply referencing Breeze.WebAPI.dll in a separate project. Keep up the good work
yes, would be nice when setting up your repository / uow projects to just be able to add in the EFContextProvider.
If the EFContextProvider and the other EF pieces are separated out, i'll feel much better about using this library. Today, I don't see a clean way to use breeze in a tiered architecture.
Ward Bell commented
I like that idea too. It's bundled into Breeze.WebAPI.dll today because we wanted to limit the number of libraries in play. It's kind of scary when there are many components to worry about. But as this space matures, it makes sense to do the right thing. We'll definitely look into this.