Could you point a workaround to this problem when registering a .DLL by using West Wind Web Service Proxy Generator .NET Web Service Proxy Generator for Visual FoxPro?

Hi Experts

Could you point a workaround to this problem when registering a .DLL by using  West Wind Web Service Proxy Generator  .NET Web Service Proxy Generator for Visual FoxPro?

When generating by using the tool:
So, when code runs:
Inside the box means:
Failed to load file or assembly 'filec: \ wwwproxy \ hello_serviceproxy.dll'
or one of its dependencies. The system can not find the file

Thanks in advance!
Eduardo FuerteDeveloper and AnalystAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Olaf DoschkeSoftware DeveloperCommented:
First keep everything but the WSDL URL at defaults. So let the generator generate to c:\program files (x86)\west wind web service proxy generator for visual foxpro\generated

You can get the generated files and dependencies to another target folder later via this dialog:
The generation works, but the generated PRG shows a few errors in the WSDL, one of them is:
cServiceUrl = ""

Open in new window

It must be cServiceUrl = ""
In the end the service fails in returning text/html instead of text/xml as specified in the WSDL.

In the end the WSDL definition is erroneous. Unless this is your own webservice you better look for another sample web service with a working WSDL definition, or correct it.

By the way, the errors within this WSDL definition surely are also what causes "no recognizable response was received", if you request fro a non existing service URL, you get a timeout and no response, yes. It must be plug, not pug, an L is missing.

Bye, Olaf.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Eduardo FuerteDeveloper and AnalystAuthor Commented:

So, after finding a good WSDL

<definitions name="Service" targetNamespace="urn:Service" xmlns:typens="urn:Service" xmlns:xsd="" xmlns:soap="" xmlns:soapenc="" xmlns:wsdl="" xmlns="">
        <message name="getUser"/>
        <message name="getUserResponse">
                <part name="getUserReturn" type="xsd:string"/>
        <portType name="UserFacadePortType">
                <operation name="getUser">
                        <input message="typens:getUser"/>
                        <output message="typens:getUserResponse"/>
        <binding name="UserFacadeBinding" type="typens:UserFacadePortType">
                <soap:binding style="document" transport=""/>
                <operation name="getUser">
                        <soap:operation soapAction="urn:UserFacadeAction"/>
                                <soap:body namespace="urn:Service" use="encoded" encodingStyle=""/>
                                <soap:body namespace="urn:Service" use="encoded" encodingStyle=""/>
        <service name="ServiceService">
                <port name="UserFacadePort" binding="typens:UserFacadeBinding">
                        <soap:address location=""/>

generated it as you mentioned.

Open in new window

PHP part
class UserFacade {
         * @return string
        public function getUser() {
                $sName = 'MeuNome';
                $sName .= ' MeuSobrenome';
                return $sName;
$oSoapServer = new SoapServer('service.wsdl');

Open in new window

It perfectly worked

Eduardo FuerteDeveloper and AnalystAuthor Commented:
Thank you for the assistance!
Olaf DoschkeSoftware DeveloperCommented:
Looks good. Thanks for showing your success with this. Now you might address something you initially wanted to address.

Bye, Olaf.
Eduardo FuerteDeveloper and AnalystAuthor Commented:
Thank you, Olaf!
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
.NET Programming

From novice to tech pro — start learning today.