Summary
When developing a Web Service, you will inevitably run into bugs and other issues. After those bugs are eliminated, you will deploy the application and see more bugs pop up. As the bugs change, your debugging techniques will change as well.
One of the best things you can do for your own sanity is to include an auditing mechanism in your application. This auditing mechanism can be used to track Web Service use, as well as track down aberrant behavior. If mysterious bugs appear, the auditing mechanism can save the day.
Finally, design a test plan that looks for holes in your logic and in how your Web Service handles large numbers of clients. It is always better to find these holes before announcing that the Web Service is live and someone ...
Get Creating and Consuming Web Services in Visual Basic® now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
