You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For a multi-targeted build, the --output command-line option will cause the builds for multiple target frameworks to go to the same output path. This will likely cause a build failure due to files being in use, or an incorrect build output. See #13359.
We should do something to avoid this pit of failure. Some possibilities:
Generate a build error saying this isn't supported
Automatically append the TargetFramework to the specified output path
???
The text was updated successfully, but these errors were encountered:
@dsplaisted, I closed the MSBuild issue for this with dotnet/msbuild#5675. Are you planning to make the PR for consuming this in the SDK, do you want me to, or was it already done, and I forgot?
My preferred solution would be that we map BaseOutputPath to -o instead of OutputPath for both legacy and Sdk-style projects. With BaseOutputPath (dotnet/msbuild#5238) support added to Common targets, we could just do that.
For a multi-targeted build, the
--output
command-line option will cause the builds for multiple target frameworks to go to the same output path. This will likely cause a build failure due to files being in use, or an incorrect build output. See #13359.We should do something to avoid this pit of failure. Some possibilities:
The text was updated successfully, but these errors were encountered: