Despite the absence of a maximum, you may encounter problems with Metadata Exchange- and the next configuration value and the default maxNameTableCharCount.
When trying to add a new function to existing functionality WCF Service, I encountered errors when trying to "Refresh the service link", because the default value is maxNameTableCharCounttoo small to handle the size of the mextranslation.
Metadata Exchange, mex binding .
, , , :
(16384) XML. , , XML - XML- , . MaxNameTableCharCount XmlDictionaryReaderQuotas XML-. 1, 332845.
Mex :
<endpoint address="mex"
binding="customBinding"
contract="IMetadataExchange"
name=""
bindingConfiguration="customMex"
listenUriMode="Explicit" />
Custom Binding, :
<customBinding>
<binding name="customMex">
<textMessageEncoding>
<readerQuotas maxDepth="2147483647" maxStringContentLength="2147483647"
maxArrayLength="2147483647" maxBytesPerRead="2147483647"
maxNameTableCharCount="2147483647" />
</textMessageEncoding>
<httpTransport transferMode="Buffered" maxReceivedMessageSize="2147483647"
maxBufferSize="2147483647"/>
</binding>
</customBinding>
, .