Monthly Archives: April 2014

WAQS: Modules dependency

7 reasons to use WAQS WAQS documentation   Imagine that you have two modules: one for managing stock and one for ordering. In ordering one you have a service method ConfirmOrder that create invoices and which also has to update … Continue reading

Posted in 16868 | Leave a comment

WAQS: Global context

7 reasons to use WAQS WAQS documentation   One of the cool feature of WAQS is the fact that, like with Entity Framework, when you save client context changes, all the SQL operations are executed in the same transaction. With … Continue reading

Posted in 16868 | Leave a comment

How to use WAQS? Split the generated code in many projects

7 reasons to use WAQS WAQS documentation   In the last post, I presented you how to share specification methods between many edmx. WAQS does not allow you to use many edmx in the same project. So we need one … Continue reading

Posted in 16868 | Leave a comment

WAQS: Multi edmx and specifications methods

7 reasons to use WAQS WAQS documentation   It is often recommended to use small edmx (one per functional module for example) instead of one huge. Why using many edmx instead of only one? First, even if the availability to … Continue reading

Posted in 16868 | Leave a comment

WAQS: Client Server namespaces conversion

7 reasons to use WAQS WAQS documentation   Sometimes we want to use some types in the specifications that exist in the client with a different namespace. To let you doing it, WAQS allows you to define namespace mapping. In … Continue reading

Posted in 16868 | Leave a comment

WAQS: Sharing code between server and client

7 reasons to use WAQS WAQS documentation   I do love the way to share code using specifications. However, if you want to share constants between server and client for example, specifications can’t help you. So there is another way … Continue reading

Posted in 16868 | Leave a comment

WAQS: Specifications factorization

7 reasons to use WAQS WAQS documentation   In some cases we want to factorize one part of specifications methods. For example, imagine that we want to extract InvoiceDetail creation in our MakeInvoice method. However, we don’t want to have … Continue reading

Posted in 16868 | Leave a comment

WAQS: Querying factorization

7 reasons to use WAQS WAQS documentation   Generated entities are partial. So you can extend them. In the client, you can let them implementing some interfaces for example. For example, imagine this interface IAddressable public interface IAddressable{    string Address { get; … Continue reading

Posted in 16868 | Leave a comment

WAQS and unit tests: Mock the database

7 reasons to use WAQS WAQS documentation   Unit testing implies without DB. Imagine that you wrote this two specification methods: public static bool HasOrderInLast120Days(string customerId, INorthwindWAQSEntities context){    return context.Orders.Any(o => o.CustomerId == customerId && (DateTime.Now – o.OrderDate).Days < 120);} public static Invoice MakeInvoice(this Order … Continue reading

Posted in 16868, 18099 | Leave a comment

WAQS: Write your code faster and better

WAQS is a code-generation solution to speed up and improve quality of.Net data centric applications development. It abstracts away the technical code in order to let developers focus on value add tasks: screens and business code. It’s great for both … Continue reading

Posted in 16402, 16868, 17697, 7674 | 2 Comments