Share via

Web Service Deployment

  • Article

When deploying your custom applications that use Web Services, you must include redistributable components from the Toolkit. If your custom application only accesses existing Web Services, you only have to include the SOAP Client merge module.

For applications that must publish a Web Service, you must include both client-side and server-side merge modules from the Toolkit. In addition, you must have the specific server-side support files (for example, ASP listener, WSDL files). You might want to consider using the _webservices foundation classes to automate this process the first time the deployed application is run. If you automate the Web Service publishing process, you can have a virtual directory created and support files generated on the fly. It is recommended that you do extensive setup testing if you choose to take this approach to deployment.

See Also

Web Services Overview | Web Service Registration | Calling Web Services | Specifying a Web Service Default Location | Web Service Publishing | Using the Web Services Project Hook