I have a web service method that I would like to have optional parameters so that I don't have to write 3 overloaded methods and name them all differently.
Wouldn't it be easier to just pass in an object from the client?
That way I wouldn't get errors when the client doesn't submit the double that my web service defines (because it is optional in the method).
I could receive the object and then work on it server-side in my service.
How do I go about doing this? I guess I am confused because of the web service client that .NET creates by default for my service. Can I just override that ugly default page and make my own client? My users will not want to use the page itself anyway. They are going to have their own client pages.
Am I missing something here?
Wouldn't it be easier to just pass in an object from the client?
That way I wouldn't get errors when the client doesn't submit the double that my web service defines (because it is optional in the method).
I could receive the object and then work on it server-side in my service.
How do I go about doing this? I guess I am confused because of the web service client that .NET creates by default for my service. Can I just override that ugly default page and make my own client? My users will not want to use the page itself anyway. They are going to have their own client pages.
Am I missing something here?