OK,
As I mentioned, Visual Studio wants to see the WSDL XML contract that is
generated by the current webservice. It uses this to compile a proxy class.
You can do the same thing by running the WSDL.EXE utility against the WSDL
XML file and see how it works.
In order for an ASP.NET Webservice to work, there needs to be an IIS Virtual
Directory (IIS Application) for it, at least one .asmx file which represents
the endpoint for the WS, and a class file behind that with at least one
method attributed with the [WebMethod] directive.
All this stuff is in the documentation; if you aren't familiar with how it
works, an hour or so taken out to read up on it now will save you a lot of
time later.
Peter
--
Co-founder, Eggheadcafe.com developer portal:
http://www.eggheadcafe.com
UnBlog:
http://petesbloggerama.blogspot.com
"mph140" wrote:
Peter, sorry I am not sure I am getting this. Do you mean the
services populated when I do Add Web refererence is stored in a WSDL
Xml file? I am only working on my locall PC for now so I suppose able
to find this WSDL xml file contains those unwanted services? And when
you say Http://servername/WebServiceRoot/Ser...Name.asmx?WSDL
what exactly should I do?
Thanks a lot for your help