I’m not sure if you put your web services in a seperate project but currently all our web services are in our WAP project under various folders….to me it’s a royal mess.
anyway, besides unit testing, mocking, etc. I created a new Web Project. I want to consume one of the other web project’s service for testing purposes.
But I realize that when I add a project referene to that other web project, I start getting reference errors for stuff like 3rd party controls probably because the web.config in this test web project doesn’t have some of the same keys.
Obviously this is the wrong way to go. What is an easy way to utilize the service without having to refactor how we are storing the services at the moment physically?
If your source project is a web service project, you can create a new asp.net web application project, right click and add a Service Reference to your service project.
From there, there are many ways to test the service. You could make a page that would go through all the different service methods and generate a web page that shows you the results or have a page to allow you to put in inputs to test each service method.
Here’s the MSDN page to get started with web services, they most likely have some good tutorials.
http://msdn.microsoft.com/en-us/library/t745kdsh.aspx
I also suggest investigating WCF services as another service option
http://msdn.microsoft.com/en-us/netframework/aa663324.aspx
Of course, unit testing may be your best bet. In visual studio you can add a unit test project to test the class of your web service and test the individual methods that way.