Update YamlDotNet dependency

[joergrosenkranz]

YamlDotNet.Signed was deprecated. That's why it was replaced by the current version of YamlDotNet. This fixes #29.

[Roel84]

The AppVeyor build is failing. Please have a look.

Are the remarks from @bh-sijtnic still applicable? The new YamlDotNet package does support NetStandard2.0 and is strong-named.

[joergrosenkranz]

The AppVeyor build is failing. Please have a look.

Yes, exactly. That was my comment in the issue about: "I can build the assemblies and run the tests, but someone should have a look at the build files in the repo."
I have no idea how to fix the Fake build files.

The other comments are about moving the project forward to a new version. My fix is only for the deprecated dependency.

[Roel84]

The AppVeyor build is failing. Please have a look.

Yes, exactly. That was my comment in the issue about: "I can build the assemblies and run the tests, but someone should have a look at the build files in the repo." I have no idea how to fix the Fake build files.

The other comments are about moving the project forward to a new version. My fix is only for the deprecated dependency.

I fixed the build script. If you update your branch it should build now.

[joergrosenkranz]

Thanks, it seems to build now.

[Roel84]

Changes looks good. Thank you for your contribution to the project.

I will publish a new NuGet package.

[Roel84]

@joergrosenkranz unfortunately the API key for publishing the NuGet package is expired.

@PMudra could you renew the API key please?

[PMudra]

I have updated the key (which will be valid for a year) and triggered the NuGet publish process again. So the package should be available very soon.