I would strongly suggest that WSDL on the fly is not the solution to any
problem that you are trying to solve. Unless the client is doing simple
mesage processing, the proxy class would need to be created at compile time,
which means that it won't vary with your WSDL.
You may consider a flexible object model for your return types so that you
can get the data that you want back to the client.
"Manish Soni" wrote:
I wish to expose a set of backend functions as web services. Now the
metadata for the functions is not available before hand. So I want to have a
way to dynamically generate the wsdl when user requests for it. I should be
able to execute some code to generate wsdl and then return that. How can I
override the default behavior of ASP.NET to accomplish this?
-- Manish Soni