How to use a WSDL

I would fire up Visual Studio, create a web project (or console app – doesn’t matter).

For .Net Standard:

1. I would right-click on the project and pick “Add Service Reference” from the Add context menu.
2. I would click on Advanced, then click on Add Service Reference.
3. I would get the complete file path of the wsdl and paste into the address bar. Then fire the Arrow (go button).
4. If there is an error trying to load the file, then there must be a broken and unresolved url the file needs to resolve as shown below:
   
   Refer to this answer for information on how to fix:
   Stackoverflow answer to: Unable to create service reference for wsdl file
   

If there is no error, you should simply set the NameSpace you want to use to access the service and it’ll be generated for you.

For .Net Core

1. I would right click on the project and pick Connected Service from the Add context menu.
2. I would select Microsoft WCF Web Service Reference Provider from the list.
3. I would press browse and select the wsdl file straight away, Set the namespace and I am good to go.
   Refer to the error fix url above if you encounter any error.

Any of the methods above will generate a simple, very basic WCF client for you to use. You should find a “YourservicenameClient” class in the generated code.

For reference purpose, the generated cs file can be found in your Obj/debug(or release)/XsdGeneratedCode and you can still find the dlls in the TempPE folder.

The created Service(s) should have methods for each of the defined methods on the WSDL contract.

Instantiate the client and call the methods you want to call – that’s all there is!

YourServiceClient client = new YourServiceClient();
client.SayHello("World!");

If you need to specify the remote URL (not using the one created by default), you can easily do this in the constructor of the proxy client:

YourServiceClient client = new YourServiceClient("configName", "remoteURL");

where configName is the name of the endpoint to use (you will use all the settings except the URL), and the remoteURL is a string representing the URL to connect to (instead of the one contained in the config).