A largely misunderstood issue in .Net web services is the capability of overloading web service methods. Overloading web service methods is possible and very easy but it helps to have some understanding of SOAP first.
If you navigate to your web service and click the link "Service Description", or just add ?WSDL onto the end of your web service within your browser, example:
You will see the Web Service Description Layer (WSDL). Inside your WSDL you will see your web service methods represented as operations such as:
Now if you go into your Add method inside .Net and add try to overload it, the problem you have is that method names within .Net map to both operations and message elements within your WSDL and you cannot have two message names that are the same, example:
Cannot exist twice. The fix is simple, add a WebMethod attribute to both methods and make sure they have distinct names between them.
public int Add(int x, int y)
return x + y;
public int Add(int x, int y, int z)
return x + y + z;
Now your WSDL will have message elements with names:
But your operations (within WSDL) will have the following:
Thus when you generate your proxy class for your web service (IE: Web Reference, or WSDL.exe) then you can open your proxy class and see how it maps overloaded methods to the operations properly.
While it's not necessary to rewrite the WSDL yourself, understanding how to manipulate the WSDL through attributes within your .Net web service is invaluable.
See Also: WSDL spec from the W3C