Monthly Archives: December 2013

7 reasons to use WAQS WAQS documentation We saw that, using WAQS, we can querying directly from the client. But, when we do this, we sometimes want to be able to filter the result in the server in order … Continue reading →

7 reasons to use WAQS WAQS documentation Why using a DTO instead of an entity? Using a DTO could be very complex if this one is modified on the client side and if you want to save your changes. … Continue reading →

7 reasons to use WAQS WAQS documentation A service method in WAQS vocabulary is neither a calculated property, nor a metadata definition nor a validation method. Service methods could be used to define some process. So for example, you … Continue reading →

7 reasons to use WAQS WAQS documentation Imagine that we want to be sure that an order does not exist without any detail. This basic feature is not as easy as it seems because of concurrency. Indeed, if it’s … Continue reading →

7 reasons to use WAQS WAQS documentation If you really want to be sure that the couple (CompanyName, ContactName) on customers is unique and if you don’t want to express it in the DB to not spit your business … Continue reading →

7 reasons to use WAQS WAQS documentation In our previous sample, the validation rule will be apply on SaveChanges when the entity is Added or Modified. But perhaps we also want to apply it on Delete or perhaps we … Continue reading →

7 reasons to use WAQS WAQS documentation With the same way than for calculated properties, you can use NotApplicableOnClient attribute to specify that a validation method is only applicable on the server on saving and still with the same … Continue reading →

7 reasons to use WAQS WAQS documentation Metadata allows to define some basic validation rules. But sometimes, validation is more complex. For example imagine that we want to be sure that order’s OrderDate is always less than ShippedDate with … Continue reading →

7 reasons to use WAQS WAQS documentation WAQS uses edmx metadata for validation: MaxLength (for string and byte array) and Nullable. However, edmx metadata often are insufficient: no MinValue, no MaxValue, no MinLength, no Pattern and even less dynamic … Continue reading →

7 reasons to use WAQS WAQS documentation Sometimes, we want to calculate the property on the server only. For this, WAQS has an attribute to specify it: NotApplicableOnClient. Sometimes, we need to execute a query into the DB to … Continue reading →