Hi FoxScully
SoapUI can aid in identifying WSDL errors, but it may not detect all issues preventing Visual Studio recognition. T
- To triage WSDL problems, utilize SoapUI by importing the WSDL, validating it with the "Check WS-I Compliance" feature, and inspecting its structure.
- Besides, consider employing other tools like Apache CXF WSDL Validator, online WSDL validators, XMLSpy, or Oxygen XML for comprehensive validation.
- Be aware of potential Visual Studio-specific issues, such as metadata endpoint requirements, authentication needs, and WSDL version compatibility. To ensure thorough checking, use multiple validation tools, verify Visual Studio constraints, and examine specific error messages.
While SoapUI is a valuable tool, combining it with other approaches will yield the best results in identifying and resolving WSDL-related problems.
To learn more
Check WSDL for WS-I compliance using the soapUI WS-I compliance test
WCF Error A SOAP 1.2 message is not valid when sent to a SOAP 1.1 only using wsHttpBinding - Stack Overflow
Hope this helps - Happy to help further!!
Thank you very much and have a great one!
Warm regards