I am in development of an application which has WPF as a client/UI application which will connect to a WCF service over internet to pull data to show to the user.
I have started with using NLayerApp approach suggested by Microsoft. It is all fine till the client application performs Add/Update/Delete operations on the entities.
I have following layers on my WCF service part.
1. Infrastructure Layer with EF 4 mapping and repositories.
2. domain layer with business entities and domain services.
3. Application Layer : I am confused about this
4. WCF layer with service contract and data contracts.
Now the application is growing in terms of business logic complexity. I mean the user should be able to provide filter conditions while viewing data and as the client is WPF the display mechanism is not that simple. So here I had to introduce some DataContracts
which will return complex data entities to be displayed on UI.
Here I need assistance on where the business logic layers should be put on server side and what will be the best approach to convert business entities to related data contracts.
Also to business logic will need to execute complex queries on database and I am not allowed to use stored procedures here so all I have to do is create complex queries using JOINS in C# only. Using repository
View Complete Post