The combination of Angular and Breeze is incredible. Finally EF makes sense for me and I can get the whole workflow working.

To save someone else running across the 5 hour "learning experience" i had yesterday when first getting this whole thing up and running :

Breeze (or at least I think it's Breeze) will camel case the object properties coming back in the JSON object unless explicitly told not to. This will matter - a lot - when binding in Angular with ng-model = 'controller.name' if you think name begins with a capital letter because it does in your POCO class model. There will be no error you just won't see anything in your HTML. It will never get rendered. You will spend a *lot* of time with Fiddler and Chrome Dev Tools figuring out why it appears you are not getting the data you are obviously actually getting.

And if you are really new to web development, but advised the name on the command string in Web.config should be the same as the name of the dbContext in the data project if you want everything to hook up like magic without further configuration (convention over configuration, neh?)

If anyone has words of wisdom about the best way to address multiple databases using Breeze with EF, I'm all ears. I assume multiple dbContexts, and then do you munge both into the same repository or use separate repositories and munge it in the BreezeController or multiple breeze controllers and bring it all together in a datacontext.js service???

Would love to connect with other actively working with the HTML5-Angular-Breeze-WebApi-EF-SqlServer stack ala John Papa's latest Pluralsight SPA. I think this is exciting stuff but it is definitely a lot of new stuff to absorb.