Breeze offers several NuGet packages for the .NET developer.
Breeze.AspNetCore.NetCore - Base support for ASP.NET
Breeze.Persistence.EFCore - If you manage data access with Entity Framework.
Breeze.Persistence.NH - If you manage data access with NHibernate.
Breeze.Persistence - If you manage data access by some means other than Entity Framework or NHibernate. The EF and NH packages depend upon this one.
Breeze.Server.WebApi2 - Base support for Web API 2 (aka v.5)
Breeze.Server.ContextProvider.EF6 - If you manage data access with Entity Framework 6.
Breeze.Server.ContextProvider.NH - If you manage data access with NHibernate.
Breeze.Server.ContextProvider - If you manage data access by some means other than Entity Framework or NHibernate. The EF and NH packages depend upon this one.
Note that these server side nugets are actually EXACTLY the same nugets used by the Breeze.Js (javascript) client. Any Breeze client (.NET or JavaScript) should be able to talk to any Breeze server, regardless of technology.
A Breeze.sharp application will often have separate projects for separate concerns within your application. One possible organization is shown below:
Breeze.Server.ContextProvider.EF6 - If you manage data access with Entity Framework 6.
Breeze.Server.ContextProvider.NH - If you manage data access with NHibernate.
Breeze.Server.ContextProvider - If you manage data access by some means other than Entity Framework or NHibernate. The EF and NH packages depend upon this one.
The Basic Breeze series guides you toward a more sustainable application structure with greater attention to modularity and separation of concerns while introducing fundamental Breeze concepts and techniques.