sorry but I think that using InvokeMethod_ParameterArray the parameters should be correctly adapted by helper....
As you can see (in my previous messages) with a call with only 8 params if I use the function in Proxy all is good, with the same parameter and InvokeMethod_ParameterArray it not work.... (tell me fuction do not exist)
If you're using InvokeMethod_ParameterArray and it says method not found you're passing an incorrect type for a parameter most likely. Having the InvokeMethod that takes parameters isn't going to help that. The parameters have to be typed properly or the method will simply not be found. With 15 or more parameters this gets difficult to troubleshoot which is why it sucks to have methods that have that many parameters.
More info can be found here:
http://west-wind.com/wsdlgenerator/docs?page=_3680sgboj.htm
+++ Rick ---
Thanks for the quick and kind answer Rick...
I wait for next release...
How you can see in my prevoius post using InvokeMethod_ParameterArray I have a problem of "Method not Found" that I can't fix with my knowledge...
Using Directly call to method have the disadvantage of parameter passing... some of this are Byte[]... and I not be able to directly transform data form Vfp9 to something accepted by Method (or I do not be able to do it :-) )
Have a nice Sunday...
Flavio
Yes the latest version of wwDotnetBridge supports only 10 parameters in InvokeMethod. You can use InvokeMethod_ParameterArray to pass more parameters.
The next update will include an updated InvokeMethod that supports 24 parameters (foxpro's maximum) by default. In the meantime InvokeMethod_ParameterArray is the preferred way to do this.
Alternately you can also try invoking the method directly:
loProxy.oService.MyMethod(1,2,3..,n)
You should be able to pass any number of parameters to the method if you call it directly. As long as the method accepts FoxPro safe parameters you can always call it directly.
+++ Rick ---
I downolad latest version form this site and installed it. Version report release 1.25
Where does your version of wwdotnetbridge.dll come from? What product and when did you download it?
The proxy generator was updated a few days ago actually so if that's where it comes from, you should update it to the latest version.
+++ Rick ---
Hi.... I have noticed that in my version (shareware) of wwwDotNEtBridge there isn't fouction correspondi at invokeMethod with 13,14,15 parameters (that should exist form version 1.18 if i understand correctly)....
May be this the problem? outdated wwwDotNetBridge dll? .net reflector report 5.66 version...
thanks for help
Flavio