Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
"dotnet publish -o obj/foo" does not respect output parameter
See original GitHub issueI found that when passing an explicit output path to the dotnet publish task, the task modifies the output path by appending the projectFileName on the end (see getModifiedOutputForProjectFile). This is unexpected and makes it hard to chain commands together when left “guessing” what the output path will actually be.
Expected behavior: If an explicit output path is specified, it should be left untouched
Actual behavior: The projectFileName is appended to the output path.
Issue Analytics
- State:
- Created 6 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
I’ve given up on the Dotnet Core tasks, and just used a simple command task
With 2.0 version of the task, now there is an option to not change the default behavior by appending the container path. With this control is in user’s hands. The reason for still having the option to preserve the old behavior is that the task can work with multiple projects. In such a case, if an ouput path is provided, this behavior lets you have cleanly publish all of them.