Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
What does .NET offer the VFP doesn't
Message
 
 
To
13/07/2002 01:47:37
General information
Forum:
Visual FoxPro
Category:
Visual FoxPro and .NET
Miscellaneous
Thread ID:
00672445
Message ID:
00678369
Views:
23
I am not sure I follow your process below... Bascially, you create the web service project in .NET which yields a asmx file. Assuming the project is called test, you can get the wsdl like this:

http://localhost/pubs/pubs.asmx?wsdl

Intrestingly enough, while you can access the web service in VFP 7, the intellisense doe not work.

IAC, if you are working in .NET, you simply add a web reference by pointing to the asmx URL. Consuming web services, whether you are in VFP or .NET is a snap. Creating web services OTOH, I find to be streamlined in .NET.





>Yes, it helps. So, if I understand correctly, in .NET, we don't have to do an extra step such as using the WSDL generator to generate the WSDL file. Basically, you just update your code, compile and you're ready to go. So, this should ease the manipulation of the files from the development environment to the server as, at least, as the WSDL generation step is builtin in .NET.
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform