Geek Answers Handbook

Is there a limit to the number of work contracts in WCF services?

I have a WCF service that contains a number of operating contracts. When the number of these operations was too much, I get an error message in wcftestclient to bind the service. When I split this service into two services, this problem is resolved.

What is the problem? Is there a limit to the number of operating contracts in WCF services?

+1
c # wcf
source share
2 answers

I do not know the limitation of the number of work contracts for the WCF test client, but in general it is considered good practice to limit the number of operating contracts in any given service to a small number (I think Juval Lowry recommends about 12 in his book).

The WCF Test Client does not support all WCF features — can it be that one or more of your operations use something that is not supported?

Types: Stream, Message, XmlElement, XmlAttribute, XmlNode, types that implement the IXmlSerializable interface, including the corresponding XmlSchemaProviderAttribute attribute, as well as the XDocument and XElement types and the ADO.NET DataTable data type.

Duplex agreement.

deal.

Security: CardSpace, certificate and username / password.

Bindings: WSFederationbinding, any context bindings and Https bindings, WebHttpbinding (support for Json response messages).

Taken from WCF Validation Client (WcfTestClient.exe)

+2
source share

I do not think that there is such a limit. In one of my projects, the maintenance contract was hundreds of maintenance contracts, which made the service terrible. Then we divided it by business. I think you should group business operations.

0
source share

More articles:


All Articles