WCF request data: the maximum Message Size quota for incoming messages (65536) has been exceeded. To increase the quota, use the maxcompute edmessagesize attribute on the corresponding binding element ., Wearing A Cute vest for sanitation

WCF request data: the maximum Message Size quota for incoming messages (65536) has been exceeded. To increase the quota, use the maxcompute edmessagesize attribute on the corresponding binding element ., Wearing A Cute vest for sanitation

 

Generally, the WCFClient tool is used for testing after the WCF Service is written. When a data request is sent, an exception or error occurs when the returned data volume exceeds the default value.

The error is also prompted clearly, which is nothing more than modifying the size of the received value. This configuration modification test can also be performed on the WCFClient, as shown in the following steps:

The Client. dll. config displayed in the service configuration shows the simulated Client configuration information. The value of maxcompute edmessagesize is not set in the Bind node, and the default value is 65536.

Right-click the configuration file and you will see the option "Edit with SvcConfigEditor" = ".

Set MaxBufferPoolSize/MaxBufferSize/MaxReeiveMessageSize to the maximum value "2147483647". You will be pleasantly surprised when you refresh the service ~~~ After saving, the client configuration will be automatically updated.

When you call a method, everything is OK. However, big data is not displayed in formatting. The complete service data is returned in XML.

In this case, you only need to change the client configuration to the actual client configuration of your project.

But !!! When you use WCFClient for testing again next time, you will find that the client configuration has been restored to the default value =. Fellow me ~ Open tools/Options =

Just hook up this circle ~~!

This dog skin plaster can be used .........