Hello,
just trying to help you:
one of my employers had a very similar issue recently, we were digging very-very deep into VisualStudio's NUSOAP service .cs code generation method (he was into generating c# instead of vb:NET code you mentioned).
We found the following, hope this help:
- I assume you are trying to reference NUSOAP webservice as Service reference, this caused the error for the employer i mentioned above
- once you reference your NUSOAP webservice as WebServiceReference in your VisualStudion vb.NET solution (for my eployer i found that solution in c#) code generation starts to work fine
- the problem is basically being caused by "encoding" NUSOAP webservice method definition, in case of using "encoded" causes error in VisualStudio code class generation, but using "literal" code generation will pass, but afterwards when you try to call your webservice, parsing the webservice's respones is going to fail on vb.NET side
The informations i provided above is for free, hoping does help you to move with your problem.
I can help you even with testing if you can provide me the PHP source of your NUSOAP service, my fee in my proposal is for that case.
For my employer the final solution i suggested him was to move away from using PHP with NUSOAP, that is how he did and implemented his webservice using different technology (i don't know what technology ho chose).
Have a nice day,
chris