Hi Tyler,

Welcome to the MSDN newsgroup.

As for the webservice client proxy generate through .net tool, in ASP.NET
web application, since it no longer expose the autogenerated source file,
it will prevent us from modifying it manually. What we can do so far is use
custom soapExtensionImporter to do some customizing on the wsdl or cilent
proxy generation process, however, so far I haven't found any means to
modify the method's referenced parameter type. It can only help add new
proxy class type or apply some custom attributes:

#How to: Customize the Generation of Service Descriptions and Proxy Classes
 
http://msdn2.microsoft.com/en-us/library/f9hatst6.aspx

You can have a look at the WSE's extensionImporter
type(Microsoft.Web.Services3.Description.WseExtensionImporter) for
reference.  Anyway, creating such a custom importer is a bit too hard.

So IMO, I'd suggest you create the webservice class in a separate class
library project so that you can maintain the generated source file. Or you
can also manually use the wsdl.exe to generate the proxy outside the
project(in commandline).

Hope this helps.

Regards,

Steven Cheng
Microsoft Online Support