Breeze offers several NuGet packages for the .NET developer.
Breeze is fundamentally a library for easing development of HTML/JavaScript client applications that fetch and store remote data. BreezeJs doesn’t dictate the server technology. It doesn’t dictate the remote service API. Although you can write a Breeze application entirely on the client with mock data, ultimately the app will communicate through a web-facing service API to a server and a database.
The package (or packages) you need depend on your development scenario.
Breeze ships with out-of-the-box support for the ASP.NET Web API and Entity Framework. The easy route to a Breeze application is shown in the following repo: Getting Started with Breeze
See Breeze Steps for a step by step review on how to build a .NET Server.
The Breeze sample applications are applications with a Web API controller, a C# entity model, and the Entity Framework mediating between the model and a SQL Server database.
We also recommend that you look at Brian Noyes “Building Data-Centric Single Page Apps with Breeze” and at John Papa’s two courses, “Building Apps with AngularJS and Breeze” and “Single Page Apps JumpStart with Durandal, Knockout and Breeze”. Please note that the .NET versions of the Breeze Server have undergone a great deal of change over the past 3 years as new versions of .NET, the Entity Framework and ASP.NET have been released. As a result many of the samples above are outdated from the standpoint of the server side code. However the client side code in these examples is still completely compatible with current Breeze implementations and the server side code while out of date is still very similar to what is required for the newer .NET frameworks.
Note: Version 7.1+ of each package is for .NET 5, 6, 7, and 8, whereas Version 3.x is for .NET Core 3.1 and Version 1.x is for .NET Core 2. Please note that only the Version 3 and later packages will be upgraded in the future. No further support for the .NET Core 2 packages will occur.
These packages are no longer being maintained. Please migrate to .NET Core versions.
These packages are no longer being maintained. Please migrate to .NET Core versions.
Free & open source
