Hi Alex,

Welcome to the MSDN newsgroup.

As for the generating client proxy for ASP.NET webservice that contains
generic types parameters/return value problem you mentioned, this is an
expected behavior due to  XML webservice's nature.

Basically, webservice only publish the WSDL document as the service
contract to client users. And client users (some webservice toolkit or
component) will generate the proxy code from the WSDL document. However,
because WSDL document  is based standard XML schema,  no matter what
platform specific types we haved used in webservice code, the WSDL document
will use standard xml schema types to represent them. And for .net
framework, such types like List, ArrayList, Collection will be represented
by xml array.  Also, using such standard xml schema types can help
different client platform able to generate the correct proxy types to map
the webservcie parameters/return values.  

Therefore, for your scenario, your webservice client is also using .net
framework and you want to have the client proxy also use the .net specific
types (the same as serverside service code), you have to manually modify
the generated proxy code.

Please feel free to let me know what you think.

Regards,

Steven Cheng
Microsoft Online Support