Skip to content

Port to .NET Standard #255

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 38 commits into from
May 12, 2017
Merged

Port to .NET Standard #255

merged 38 commits into from
May 12, 2017

Conversation

aaubry
Copy link
Owner

@aaubry aaubry commented May 8, 2017

This contains all the changes proposed and discussed in #244.

What's included:

  • Added two targets, Release-DotNetStandard-Unsigned and Release-DotNetStandard-Signed that produce assemblies targeting netstandard1.3.
  • Added the netstandard1.3 assemblies to the Nuget packages. This means that using YamlDotNet on .NET core should no longer be a problem.
  • Fixed some issues that surfaced when updating the AppVeyor image to VS2017 because it already includes the Unity prerequisites.
  • Added a Dockerfile that builds an image (aaubry/yamldotnet) that contains all the dependencies needed to build YamlDotNet on Linux. This was necessary to overcome some difficulties with mono, but it is also useful for anyone wanting to build the library without having to install anything (besides Docker).
  • Changed the Travis build so that it uses our docker image and performs a full build, including unit tests. This will help detect problems in case a test passes on Windows only.

What's still missing:

  • The unit tests project should also be converted so that tests are also run against the .NET Standard assemblies.

@aaubry aaubry mentioned this pull request May 8, 2017
//
// You can specify all the values or you can default the Revision and Build Numbers
// by using the '*' as shown below:
[assembly: AssemblyVersion("4.1.1.0")]
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am not sure if you meant to check this in since it's always updated during testing. :)

[InlineData("F", "ko-KR", "2017년 1월 13일 금요일 오전 5:32:06")]
[InlineData("g", "ko-KR", "2017-01-13 오전 5:32")]
[InlineData("G", "ko-KR", "2017-01-13 오전 5:32:06")]
// [InlineData("f", "ko-KR", "2017년 1월 13일 금요일 오전 5:32")]
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I tried to look into these failures because the tests work on Windows but not Linux. From what I could tell, Mono is having troubles trying to fetch the AM/PM designator for ko-KR (because it is always null).

Copy link
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I left a comment to @justinyoo , who contributed this code. Maybe he knows more about this problem.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@conniey @aaubry Yep, I'll have a look. In the meantime, you can comment out those lines.

@conniey
Copy link
Contributor

conniey commented May 9, 2017

LGTM. 👍 Thanks a lot for putting this together!

@aaubry aaubry mentioned this pull request May 11, 2017
@aaubry aaubry merged commit cd1a0da into master May 12, 2017
@nbarbettini
Copy link
Contributor

Confirmed that 4.2.0 works fine in my .NET Standard 1.3 project. I don't have to use PackageTargetFallback anymore! 🎉 Thanks @aaubry and @conniey.

@aaubry aaubry deleted the netstandard branch May 15, 2017 09:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants