Add cli tool support to .net proj files #419
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
|
It looks like the same error/warning is happening on Travis & AppVeyor, but those builds continue on instead of erroring out like my local build. |
|
|
|
This looks great! Thanks for including a link to the relevant documentation, as well as an example URL. Those made it really easy to understand/test. |
Merged
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 expands the existing .net proj file linking to also support cli references via
DotNetCliToolReference.The tests are passing locally, but as per #418 I'm unable to build & test it myself 😞
An example of where this would work is https://github.com/aspnet/DotNetTools/blob/3c20e7c45beb5d45547b549964a3da83b2e8303e/samples/dotnet-watch/LaunchAnyCommand/LaunchAnyCommand.csproj#L6-L10