Sounds very formal...but it's not..I've made a couple of things in C# because I tried out Talking SOAP with C#. But that was different. I imported web-references and used whatever was built from "our" supplier...

But this was my first "proffesional" application. The purpose of the application was to filter out mails by date, and print out attachments by date, in two different formats. First page was a "cover-page", and the second was an attachment in  the filetype .pdf, that was X-pages of stickers, that could be taken out from the subject of the mail. The project started June'2019, as a curiosity from my side. First commit to GitHub was in September'2019, after the project was approved from my employer.

This article about SOAP(client) is actually platform-specific. But programming in C# is very popular and is a big part of .NET I feel it's important to learn/get a hang of C# and its way of handling the SOAP-service. It's been a long time since the last time I used Visual Studio, but I remember it as being a very nice experience. I used to do some programming in Visual C++ and the DirectX interface. I think it was DirectX 8..or 9..using Direct3D/DirectSound and so on...but this is a digression...The point of this article is to connect to a server using the SOAP-protocol via a WSDL. I think using the WSDL is the more simple way, and it's easy to use. Must admit that this is the first time I appoach C#. I went through a "basics"-tutorial and found out that the syntax and language was quite like C, but also a little bit like Java(even though I do not have a lot of experience programming Java).