Oh sorry, I thought I answered. The legacy web service clients in PB do NOT support TLS 1.2. So that's why I was trying to encourage you to use HTTPClient, which supports up to TLS 1.3.
SOAP sends the data in XML format. Once you have figured out what the expected XML is, you should be able to switch to HttpClient or RESTClient objects without too much trouble.
There are no replies made for this question yet. However, you are not allowed to reply to this question.
Please login to post a reply
You will need to be logged in to be able to post a reply. Login using the form on the right or register an account if you are new here. Register Here »
We use cookies which are necessary for the proper functioning of our websites. We also use cookies to analyze our traffic, improve your experience and provide social media features. If you continue to use this site, you consent to our use of cookies.
The .NET assembly was compiled using csc.
csc /t:library hellowebserviceproxy.cs
There is a compile_all.cmd in the wsproxies folder.
The C# source in the wsproxies folder is a copy of the emitted files of the PowerBuilder WebService Proxy Project.
... 10 min. later...
But now I used VS 2019 community to setup and configure a VS Studio project.
I startet with "ClassLibrary (.NET Framework) C#" type of project.
No Problems so far.
The DLL is now a bit larger (8kb) because of additionally information for version, company etc.
hth
Arnd