Hi Chris, yes, this is a totally underdocumented feature. But there actually is a very powerful means to hook into WSDL and SOAP generation. The best approach to this is from within a SoapExtension (client and/or service side). The appropriate classes to take a look at are SoapExtensionImporter, SoapExtensionReflector and ServiceDescriptionFormatExtension and their appropriate config settings in machine.config. There is a great demo on how to do this from Clemens Vasters [1].
[1] http://www.newtelligence.com/wsextensions/index.aspx HTH, Christian --------------------------------- .NET XML Web Services Repertory http://www.xmlwebservices.cc/ --------------------------------- Christopher Dix wrote: > Can anyone point me to the source of WSDL generation for an ASP.NET web > service? > > I understand that for a .NET Remoting web service, the WSDL comes from a > custom sink (SdlChannelSink) that is provided by default for all > services. I can't seem to find the mechanism/trigger for WSDL > generation from ASP.NET, though. Maybe it is internal to > System.Web.Services.WebService, or an HttpModule or HttpApplication that > intercepts those requests? > > I have two goals here: > 1) to hook into the process, which I think that I can do with Soap > Extensions, and > 2) to duplicate the process on a per-application basis with a query > string other than ?wsdl. > > Thanks, > Chris Dix > http://www.thoughtpost.com/ You can read messages from the Advanced DOTNET archive, unsubscribe from Advanced DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
