Add .Net 4.6 target #28
Merged
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
added 2 commits
December 3, 2018 11:31
Updated assembly version number.
|
Good idea. Is the net46 target necessary or will net45 suffice? I would assume that you should be able to reference the net45 assembly in a net46 project. |
|
Selfishly, I'd ask for 4.6 since a 4.6 build has already gone through our QA process. But theoretically I see no problem with just targeting 4.5. |
|
I'll start with net45 for now. Thanks! |
|
Thank you for adding it! |
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.
I have some legacy code on .Net 4.6 that could benefit from the recent updates to IdParser error handling. And it would be nice to continue using an "official" package rather than a custom build.