Constructing a Hot Towel Breeze API

Question

I'm building a fairly basic CRUD app based on Hot Towel SPA.

My plan is to use an ASP.NET web API to expose data to Breeze.

Is that the correct architecture?

At present I have four projects:

• DomainClassLibrary which contains the model T4 file (*.tt) and the partial classes to extend my EF model
• a DataClassLibrary which has the rest of the model (all this is per Julie Lerman on Pluralsight)
• a Hot Towel SPA app
• an ASP.NET web application HTTP Web API

Is my next step to build all of the controllers within the web api project to expose get, put, etc?

And then do I create a Breeze API that consumes the controllers in my web API project?

Answer 1

Hot Towel contains all of the prerequisite components so all you should need is a single project containing Hot Towel. I think you're making it more complex than it needs to be.

John Papa has an excellent course on Pluralsight that walks you through Hot Towel. Although I'm not using Hot Towel (I shifted to Angular), this course really helped me understand the fundamentals of building a SPA on .Net.