WebService WSDL reference

1) Enter the local path, VS automatically generates the relevant code, the generated in 2017 seems to be different from 2015, the structure is more obvious and easy to understand;

< br>

2) “In the ServiceModel client configuration section, the default endpoint element referring to the contract could not be found. This may be because the application configuration file was not found, or because the client element Cannot find the endpoint element that matches this agreement.”

If the content generated in app.config is not used in this project, you need to copy the relevant content to the relevant project using the reference.

3) “There is no endpoint listening to the *** that can accept messages. This is usually caused by incorrect addresses or SOAP operations. If it exists In this case, please refer to InnerException for details.”}

This is because the external network address is used in the internal network, but The address resolved by the intranet used for actual access.

(It is the opposite of the reference situation, refs, http://www.cnblogs.com/Fooo/p/3228115.html)

4) “The maximum message size quota for incoming messages (65536) has been exceeded. To increase the quota, please use the MaxReceivedMessageSize attribute on the corresponding binding element.”

This is due to the amount of data that needs to be accepted It’s too big,

(refs,http://www.cnblogs.com/xinaixia/p/5945316.html)

Leave a Comment

Your email address will not be published.