a35ae177ff
- Project dependencies are always built into their specific folders and the main project is the only one that uses the output path and intermediate output path variable. - Publish respects the output path for publish only, not compile as part of publish. This means that publishing multiple runtimes will stomp on each other. So don't do that. We can throw if you specify and output location and you haven't specified a specific combination of RID and framework. Alternatively it should probably just pick the first TFM/RID pair from the lock file. This is similar to how `dotnet run` works. - Cleaned up the incremental build output formatting - Use a single stream (output stream) since interleaving them was causing formatting issues (like losing random characters in the middle of outputting things). - Didn't change how pack works, it still preserves the output structure when passing `--output`, this one is worth discussing. We could leave the build output inplace and only move the package to the output location. That's more consistent with how everything else works and can be a follow up PR. |
||
|---|---|---|
| .. | ||
| argument-forwarding-tests.ps1 | ||
| argument-forwarding-tests.sh | ||
| check-prereqs.ps1 | ||
| check-prereqs.sh | ||
| package-command-test.ps1 | ||
| package-command-test.sh | ||
| runtests.ps1 | ||
| runtests.sh | ||
| validate-dependencies.ps1 | ||
| validate-dependencies.sh | ||