Support for C++/CLI (.NET 4.5) #976
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
|
Hi I'm not sure whether this is still a thing. Comment here if this is important. My perspective is Json.NET is focused on managed consumers. |
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.
This PR adds support for C++/CLI (.NET 4.5).
An import node for the
.targetsfile gets added to the project during the installation of the NuGet package, which includes all necessary references and reuses thenet45build. IntelliSense in VS2015 Update 3 recognizes this change immediately.The "trick" with the
_._file is required, because NuGet needs alibentry namednative(TFM).A
runbuild.ps1and a test using a private NuGet feed works as expected.