>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

Hi Tim,

I'll describe my overall strategy for the project. A business partner wishes to take orders on their own web app and pass them to ours behind the scenes. Our existing web application (not done in .Net) contains the appropriate logic for processing those orders. Our partners don't want the end-users to have to go to two different web sites to complete an order. I planned to repackage that order processing code as a COM server and make this web service a wrapper for the COM server.

The web service itself will take in a few objects as parameters, pass them to the COM component to process, package the results as another object and return that to the caller, as well as handle a file upload from the client intended to be attached to the order in question.

The existing code base is all done in VFP 9, an environment I am a lot more comfy in after about 10 years of using VFP.


Yes, the error happens in VS2008 specific to the process of adding a web reference to a small fake windows forms client app I made to test the web service with. Once the reference has been successfully created, the little app has no problem making reference to the service. Right now most web methods don't do anything. One takes a file upload. They can be called from the client and get results returned. (Though I am having other problems not related to this error)

I suspect IIS on my development machine is not quite set right somehow.