Building a Breeze server using ASP.NET Web API


Within the .NET community, ASP.NET and ASP.NET Core web applications are typically written using .NET’s Web API technology. This technology provides mechanisms for supporting a range of data services over HTTP. This section describes how specific Web API service implementations influence Breeze client development.

Breeze offers support for both legacy .NET 4.x ASP.NET applications as well as the new ASP.NET Core applications.

ASP.NET Core and ASP.NET info

The following sections also describe how to build these applications with a variety of ORM technologies such as Entity Framework, Entity Framework Core and NHibernate.

Building a Breeze-flavored ASP.NET Web API

A “Breeze-flavored” Web API is the quickest, most productive path to an HTTP service that a Breeze client can talk to with minimal configuration. You’ll use .NET components written specifically to support Breeze clients and you’ll write one (or a few) controllers in a style that minimizes your server-side coding and maintenance without compromising power, flexibility, security or performance.

The remaining topics in this section various aspects of this Breeze-flavored approach.


For technical questions, please go to StackOverflow with the tag “breeze”. StackOverflow is a fantastic site where thousands of developers help each other with their technical questions.

We monitor the [breeze] tag on the StackOverflow website and do our best to answer your questions. The advantage of StackOverflow over the GitHub Wiki is the sheer number of qualified developers able to help you with your questions, the visibility of the question itself, and the whole StackOverflow infrastructure (reputation, up- or down-vote, comments, etc).

For bug reports, please do use the GitHub Issues tab!

Please post your feature suggestions to our User Voice site

Learn about paid support.

Learn about IdeaBlade’s professional services from training through application development.

Have a non-technical question? Ask us at