Hi Jim,
>Hi All,
>
>I'm new to Visual Studio 2008, and am working on a Web service written in VB.Net 2008. Right now, I'm just creating a stub service with method signatures and a few classes to nail down an interface to be used by our business partners to send order information to us in the background from their web application.
>
>I have no trouble, errors or warnings building the web service project, or publishing it.
>
>The URL shows up okay in my browser with the information about the service and its methods
>
>
>I created a small windows forms application to use as a client to test the service. I add a web reference in that project and provide the url, there is a long delay before the service description shows up. Sometimes here I get debug messages for inetinfo. Other times the description shows up fine on the left part of the dialog, but in the box on the right labeled:
>
>Web Services found at this URL: There is the following message, instead of a list of services I can create a reference to.
>
>
>There was an error downloading 'http://localhost/testservice/Servicetest1.asmx?op=ProcessOrder'.
>The request failed with the error message:
>--
><?xml version="1.0" ?>
><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN" "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
><html xmlns="http://www.w3.org/
>
>
>In today's case I hit refresh and the correct entry appears allowing me to create my reference. Similar long delays and errors occur when I make changes, after republishing, and try to refresh the web reference in the project from the right-click context menu. I have had to remove the reference and re-create it.
>
>Any and all advice is welcome. I admit my newbie-ness freely. No doubt I will have follow up questions as this project moves forward.
>
>Thanks as always ,
I don't have the answer to your specific question but I had a couple of questions for you. Is this web service to be used for applications built on technology other than Dot Net? I have a couple of web services created with WCF but I also created a seperate component so the using applications don't have to worry about the web service connection. I was just wondering about your overall strategy with the web service.
I am guessing the error you are getting above is in the test app you are working with to access it. Is this right?
Tim
Timothy Bryan
