"Thomas Lunsford" <tl*******@gmail.comwrote in message
news:ba**********************************@k39g2000 hsf.googlegroups.com...
>I have been asked to allow one of our old-school .asp pages to support
being used as a web service. Specifically, WSDL was mentioned. I am
not an expert on this , but I have done quite a bit of reading, and I
understand that I can create a WSDL file that supports HTTP POST and
then use WSDL.exe with the proper parameters to generate a web service
proxy. To this point, all I get from WSDL.exe when doing so is
"Warning: no classes were generated." I am using /protocol:HttpPost
and referencing the WSDL as a file url. This works if I run WSDL.exe
with the SOAP protocol. I have seen many, many references stating
that it should be able to work with an http post, but absolutely none
of them have worked for me, even when I copy/paste the exact code.
I have been researching and testing, testing and researching this for
days now. Hopefully someone can provide some answers or even a
completely new direction.
I would suspect what is meant is that ASP Pages application functionality
would be converted/rewritten over to a .Net XML Web service solution. That
I know of, there is no way you're going to be able to take any classic ASP
page and do anything with it in .NET.
The WSDL would point to a url that was a .Net XML Web service solution to
generate the proxy classes in C# or VB .Net that a Web service client
application would use to access the Web Methods that the Web service
provides.
I think you first need to build a Web service application to understand what
is happening.
http://support.microsoft.com/default...;EN-US;Q301273
You can then build the proxy class off of the
Http://Localhost/webservice to
see what is generated, which you can then include that class in a Web
service client project that would consume the Web service and use it.
