Stuck on an issue?

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.

Error, warn, or fix behavior when specifying output path when building a solution

See original GitHub issue

Specifying the output path (commonly by using the -o command line option to dotnet build or dotnet publish) when building or publishing a solution can lead to issues, as multiple projects building to the same path may override each other’s files.

We should either block specifying the output path for a solution, or do something to fix the behavior (for example by appending the project name to the specified output path for each project).

State:
Created 3 years ago
Reactions:6
Comments:5 (4 by maintainers)

Top GitHub Comments

2reactions

ericstjcommented, Oct 12, 2022

@dsplaisted @marcpopMSFT this should be prioritized. In the past month I’ve observed multiple teams hit this issue and spend a tremendous amount of time chasing down the source of the binclash / wrong binaries in the output.

1reaction

ericstjcommented, Oct 17, 2022

One case is linked above: https://github.com/dotnet/runtime/issues/75086. The other was an internal request which I just forwarded. I’m pretty sure this has also come up on the .NET discussion alias a few times.

Top Results From Across the Web

Solution-level `--output` option no longer valid for build- ...

Learn about a breaking change in the .NET 7.0.200 SDK where using the `--output` option is no longer valid when using a solution...

The OutputPath property is not set for this project

I encountered the error while running a build process on TFS 2017, after I changed the "Path to solution or packages.config" from a...

Cannot debug net6.0-macos Apps - Developer Community

When I hit debug, the following error is shown in the Terminal: Possible reasons for this include: * You misspelled a built-in dotnet...

Troubleshooting AWS CodeBuild

Issue: When you try to run a build project, the build fails with this error. Possible cause: Your source repository has a self-signed...

Upgrading your build from Gradle 7.x to 8.0

This behavior was potentially an error because the classesDirs property did not contain the output for processResources . Since 8.0, this implicit dependency ......