breeze

Breeze and Angular 'ToDo' app does not work with IE 8

谁都会走 提交于 2019-11-27 02:55:28
问题 I have downloaded the sample 'Breeze 0.83.5' applications from http://www.breezejs.com/documentation/download The Angular 'ToDo' sample does not work with IE8. I have included the following script references above my Breeze script reference. Any idea why this doesn't work? 回答1: Breeze's Angular support makes use of the 'backingStoreAdapter' which in turn depends on the ES5 Javascript 'defineProperty' method being implemented by the browser. This was not implemented in IE8, and unfortunately,

Use jQuery or Q.Js for promises

◇◆丶佛笑我妖孽 提交于 2019-11-26 22:49:52
问题 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? 回答1: 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

breezejs: date is not set to the right time

让人想犯罪 __ 提交于 2019-11-26 22:46:45
I've noticed that if a date property comes back from the server with the value "2013-07-11T17:11:04.700", then breeze changes the value to Thu Jul 11 19:11:04 UTC+0200 2013. Notice the time is now 2 hours ahead ! I had already come across this issue when saving entities, so I had to explicitly convert my date properties using momentjs : date.hours(date.hours() - moment().zone() / 60); But now it seems the problem occurs also when doing read operations. What's the best way to make sure breeze does not alter values of my date properties ? Breeze does not manipulate the datetimes going to and

breeze: many-to-many issues when saving

元气小坏坏 提交于 2019-11-26 22:09:07
问题 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;

How is breeze.js handling security and avoiding exposing business logic

岁酱吖の 提交于 2019-11-26 14:05:46
问题 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

Handling calculated properties with breezejs and web api

血红的双手。 提交于 2019-11-26 11:29:42
问题 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. 回答1: When Breeze maps JSON property data to entities, it ignores properties that it does not recognize . That's why your server class's

breezejs: date is not set to the right time

≡放荡痞女 提交于 2019-11-26 09:11:37
问题 I\'ve noticed that if a date property comes back from the server with the value \"2013-07-11T17:11:04.700\", then breeze changes the value to Thu Jul 11 19:11:04 UTC+0200 2013. Notice the time is now 2 hours ahead ! I had already come across this issue when saving entities, so I had to explicitly convert my date properties using momentjs : date.hours(date.hours() - moment().zone() / 60); But now it seems the problem occurs also when doing read operations. What\'s the best way to make sure