breeze

I've been struggling for a while with many-to-many associations in a breeze app. I have issues both on the client and server side but for now, I'll just expose my client-side issue. I don't know if the approach I've come up with is correct or not, and I would really like to get feedback from the breeze team on this: My business model: public class Request { public virtual IList<RequestContact> RequestContacts { get; set; } } public class RequestContact { public virtual Contact Contact { get; set; } public virtual Guid ContactId { get; set; } public virtual Request Request { get; set; } public

I'm looking into BreezeJs and there samples are using Q.js for promises to handle asynchronous calls. John Papa is also using Q. JQuery has promises as well . What are the differences between the two? Bergi Both are based on the Promises/A standard and implement a then method (though only current jQuery, they once had a incompatible pipe instead of then ). However, there are a few differences: Q has exception handling. All thrown errors in the async then callbacks will be caught and reject the promise (and will only get re-thrown if you call .end() ). Not sure whether I personally like that.

We are considering breeze js to build enterprise applications. The awesomeness of breeze is that we can execute queries right from the client browser. This allows to constructs dynamic queries based on the users input without loading unnecessary data. I have found that using Breeze we can create business logic that reduces data traveling/transferring by 1/10 or even more when using a lazy loading strategy. using queries like these Hooray breeze!!! But what about Business Logic security, For example, We could have a repository in which we could conceal, hide and obscure our business logic; and

I'm experimenting with BreezeJS with Web API using the BreezeControllerAttribute. How should calculated properties on an entity be exposed? The only way I've found to do this reliably is to create an intermediate DTO that inherits from the entity or use a projection. Normally I would use a readonly property for this scenario, but those appear to be ignored. When Breeze maps JSON property data to entities, it ignores properties that it does not recognize . That's why your server class's calculated property data are discarded even though you see them in the JSON on the wire. Fortunately, you can