NuGet package

[simon-berger]

Work in progress!

Do not merge.

Issue

Close #297

TODOs

• Locally create working package
• Automate package generation (CI)
• (Automated) publishing of the created package
• Fix uploaded version of 1.9.0
• Update Readme

Description

Because of the poor documentation from Microsoft, I mainly used this manual as a guide: link
With this, I managed to create a native NuGet package which automatically gets created from a CI job if a new release tag is created. The created package is then uploaded as a job artifact and published to NuGet.org.
Here is an example of the CI action with an working package build: example CI run

[simon-berger]

I have successfully created a CI job which automatically creates the NuGet package and uploads the result as an artifact (example run) 🎉 .
The next step would be to (automatically) publish the package (if intended) to NuGet.org, for which I would need a NuGet account and API key (How to publish).
Moreover we maybe need to change certain metadata in the .nuspec file (e.g. Who should be the authors/owners?).

@COM8 can you please please briefly check the metadata and let me know if you want the package to be published.

[COM8]

Looks overall good.

[COM8]

In my eyes it makes sense the you use an API-Key I provide as "libcpr" to make sure we can even in the future change stuff if required directly.

[COM8]

I have created an account for nuget@libcpr.org. Like for the .deb package I can forward all mail arriving there to you in case you are interested.

[simon-berger]

I completed testing with this fresh package.

[COM8]

Great work! Thanks.

[COM8]

The CI worked perfectly: https://www.nuget.org/packages/libcpr/#versions-body-tab

[simon-berger]

Just got the email, perfect 🎉