You can disable WSDL file generation, which is enabled by default, for all Web services on an ASP.NET application. Disabling automatic WSDL file generation makes it possible for you to override the default WSDL binding definition generated in the WSDL file for each Web service. You can also enable WSDL file generation, if it has been disabled.

Note:
When you disable WSDL file generation, you must specify another location containing the WSDL file that you want to use instead and make sure that the specified WSDL file is up to date with changes made to the Web service definition.

For more information, see How to: Control WSDL File Generation for ASP.NET Web Services.

You can override the default WSDL binding definition in the WSDL file for each Web service. Overriding the default WSDL binding definition makes it possible for you to specify a different WSDL binding definition instead. The generated WSDL file will then reference the specified WSDL file with the WSDL binding definition you want to use instead.

Note:

The WSDL binding definition describes the endpoint behavior for a Web service, including the operations, parameters, additional operation and parameter types, and protocols that other applications must use to call the Web service. By default, the WSDL binding definition is generated from the Web service definition, which is obtained from the corresponding Web service class and any additional operation and parameter type classes in the associated application project.

For more information, see How to: Override WSDL Binding Definitions in WSDL Files.

Other Resources