build.sh: adding OutputDirectory command line argument to nuget commands #64
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 for this. Faced the same issue. |
Alex-Witkowski
approved these changes
Oct 25, 2019
|
We did some maintenance work on this repo which included removing of the @t081as Can you please create a new PR targeting |
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.
Due to a missing "-OutputDirectory" command line argument (nuget commands) in the build.sh file (that is present in the build.ps1 file) the behavior of the two files is different if a Nuget.config file exists in the project folder.
see https://gitlab.com/tobiaskoch/LinkTime/-/jobs/122604224