-
Notifications
You must be signed in to change notification settings - Fork 935
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix BuildTool output path #2219
Conversation
@lillo42 please test. |
@hazzik it is not fixes yet, pushd not found: https://stackoverflow.com/a/5193087
|
Very strange... |
@lillo42 I've replaced pushd/popd with cd. Could you please check now? |
@hazzik it's working now \o/ |
fi | ||
cd "$SCRIPT_PATH" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would just have used cd ../..
before the fi
, but why not.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I was thinking, but decided against it.
(Verified under Windows and Linux, from the same folder and from |
There seems to be a difference in
-o
behaviour between versions of .NET Sdk. The .NET Sdk up to 2.2 output the build artefacts relative to the project file, and starting from previews of 3.0 the build output is calculated relative to the current directory.