-
Notifications
You must be signed in to change notification settings - Fork 559
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SVCUTIL generates methods without arguments #5468
Comments
I have tried running the tool against the given wsdl and encountered below warnings, the warnings indicate that the wsdl file contains some elements that are not supported by the tool, this might result in incomplete or incorrect code generation.
Svcutil.exe and dotnet-svcutil.exe behave the same, so it doesn't seem to be regression issue of dotnet-svcutil tool. |
What do you advice? Is there an easy way to self implement the custom header and the missing arguments? I didn't find much online about it. I also noticed that the arguments are generated correctly when the method is generated async but they aren't present if I generate a sync method. |
Hi, as per this warning message "Unsupported WSDL, the fault message part must reference an element." , I tried to fix it by saving the WSDL locally and do below updates to the file:
With the updates, dotnet-svcutil generates both sync and async operations with arguments. Hope this helps. |
Thank you, is there no workaround to also add the header? |
Running the dotnet-svcutil tool with |
Thank you, yes I get the header this way but it doesn't generate the methods properly, I reported these issues to the API providers, hopefully they are able to fix it. |
Describe the bug
Broken class is generated from wsdl
To Reproduce
I'm importing this webservice in visual studio: https://api.learningassistant.com/webservices/soap/company.cfc?wsdl
the methods that are generated don't have any arguments
Expected behavior
A working class is generated
Additional context
version: [Microsoft.Tools.ServiceModel.Svcutil, Version 2.2.0-preview1.23462.5]
The text was updated successfully, but these errors were encountered: