The ASP.NET Web Services generator relies on the .NET Framework to create the WSDL on the fly when requested at runtime.
Notes:
When you develop your client application, you need to include the URL which identifies the location on the Web server at which the WSDL file can be found. The URL should be in the format http://[MachineName]/[VirtualDirectory]/ [BundleName].asmx?WSDL.
When you get the "Unable to load the WSDL file" error while using the Discovery tool, the IIS error "IIS ERROR_ACCESS_DISABLED_BY_POLICY" must be removed. This error means that the Web Service Extension is not enabled. You can resolve the error by double-clicking ISAPI and CGI Restrictions in Internet Information Services (IIS) Manager, clicking Add in the Actions pane, typing the path to the binary you want to add in the ISAPI or CGI path box along with the description in the Description box, and selecting the Allow extension path to execute option.
When you get a null exception while using the Discovery Tool for testing generated Dotnet Web Services, you should set the value to 0 for the decimal fields, if there is no value for the decimal fields.