01:33:22 AM
3MF03C60X
I don't think you have a lot of choices with Windows Store Apps because it's not actually the 'real' .NET runtime. This is why there's a difference in behavior I suspect. The SOAP Toolkit also has very little in the way of customizing the SOAP output, so I don't think you can really do much from that end.
It might be a better choice to re-write the service in .NET and serve the data from a FoxPro COM object possibly.
+++ Rick ---
We have a SOAP 3.0 webservice written in VFP9. No Problem to consume it in a WPF app, Add Service Reference is your friend.
Now we want to consume it in a Win8 App. The Add Service Reference wizard runs, shows the webservice methods and creates the wrapper. However, no method wrappers are generated. The Visual Studio 2012 error message tells this:
Custom tool warning: Contract 'DataServiceSoapPort' is not compatible with Windows Store apps because it contains one or more operations with SOAP Encoding (use='encoded'). Only the non-encoded operations will be generated.
Is there a way to generate a different type of WSDL file in VFP that doesn't use SOAP Encoding?
Or is there some C# code around that allows me to create my own win8 App compatible SOAP 3.0 service wrapper without reinventing the wheel?
TIA,
Markus
West Wind Technologies
Making waves on the Web
from Maui, Hawaii
