Create strong named assembiles

[bothzoli]

Create strong named NuGet package

To create a strong named NuGet package, a new project CSharpFunctionalExtensions.StrongName was added to the solution.
The project references source files from CSharpFunctionalExtensions.csproj and it uses the generated signing key (CSharpFunctionalExtensions.snk) to sign the assembly.

The Dockerfile was updated so that a strong named NuGet package is also built.
The azure-pipelines.yml was also modified so that the newly created package is uploaded as both a GitHub release asset and to nuget.org as well.

Minor fixes were applied to the azure-pipelines.yml file:

• the authorization header should have Bearer instead of token based on the documentation
• the cURL upload should use the --data-binary switch (note that nuget packages were not added to previous releases either)
• run conditions were added to the publish steps so that the pipeline won't fail if the credentials are not provided, but simply skip the publish steps

The version file version.txt was also updated with a patch version bump.

Fixes: #27

[hankovich]

New csproj is just a copy of the existing one. I suggest you to move common properties to Directory.Build.props

[bothzoli]

Oh yeah, thanks mate. I knew something was amiss.
I'll update the PR shortly.

[bothzoli]

I wonder though, wouldn't a Directory.Build.props be imported into all projects including Examples, Tests?
I'm not sure that'd be correct.
Shall I separate the main projects into an src folder?
Or use a different .props file and explicitly import where needed?

[bothzoli]

I've gone with a Common.Build.props file at the root of the solution.
Please let me know if you'd prefer a different approach.

[bothzoli]

Hey, any thoughts on the PR?
Thanks

[vkhorikov]

Hey, sorry, really short on time these days. I'll test it during the upcoming weekend and will push it "to prod" if everything looks good (which it does on the first glance).

[vkhorikov]

The current approach looks good, no need to include the common proj into examples and tests, those aren't getting published anyway. Locally everything looks good, merged it to master, let's see how the build goes.

[vkhorikov]

note that nuget packages were not added to previous releases either

Yeah, binaries stopped being published to GitHub awhile ago, this is the last release where it did get published: https://github.com/vkhorikov/CSharpFunctionalExtensions/releases/tag/v2.14.0

The new --data-binary option didn't help, I think it's something with the URL that GitHub has changed because the last 2 commands return 404.

[vkhorikov]

The pipeline has published the new nuget package successfully.

[bothzoli]

Wow, that's awesome news. I'll start using it right away.
Thank you very much 😊
I'll try to keep my eyes open, but if there are issues opened for the strong named package (that are working correctly with the regular one) feel free to tag me in the issue.