How to design WCF Contracts?
Posted
by Amitabh
on Stack Overflow
See other posts from Stack Overflow
or by Amitabh
Published on 2010-03-15T23:57:41Z
Indexed on
2010/03/15
23:59 UTC
Read the original article
Hit count: 231
We are designing a WCF layer which can be invoked either by a Asp.Net or a WinForm application. Our Application contains too many Entities. If we design WCF Contract around these entities then we get too many Contracts e.g IPartyService, IUserService, IPaymentService etc. So, I may end up with 30-40 Contracts? Is it a good idea or should we go for one huge contracts with around 100 operations? What are the pros and cons of each approach or is there a better way.
© Stack Overflow or respective owner
