Target .NET Standard 1.0. #11
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Thanks @lookatmike , |
|
Thank you @AndreyTsvetkov! |
|
What is the status for this? (And is there something I can do to help?) |
|
I think we are here on standoff, Can i help? |
|
If you guys still want a .NET Standard version of this package, I've forked this since the maintainer of this repo no longer seems active: https://github.com/Mackiovello/Mackiovello.Maybe |
|
Well, I'm back and the .NET Standard version is now live and on Nuget. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
To start with, this pull request isn't intended to be accepted as-is. It would break for anyone using it in a net40 project and possibly your AppVeyor build as well.
Would you consider adding .NET Standard 1.0 as a target so this library can be used in .NET Core projects? It requires no changes to .cs files to work, but multitargeting certainly adds complexity to project/build management (depending on what AppVeyor supports -- I'm not familiar with it).
I'm also happy to simply keep my netstandard fork updated, just wanted to float the idea of multitargeting.