-
Notifications
You must be signed in to change notification settings - Fork 321
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
dotnet test assumes different output path than dotnet build #5264
Comments
Addendum: If I add |
Can you please build both of the above with binary log?
I don't think we are assuming anything about the output path in dotnet test, we get it from msbuild via If you cannot share your binlog, can you please check what the value of TargetPath is in the build that is handed over to the vstest target linked above? You can do so by producing the binary log and then viewing it via the binary logger viewer: https://msbuildlog.com/ |
Description
in a two step build using
step 1 build:
step 2 test:
I get an error that
[OutputPathBase]\Release\[ProjectAssemblyName].dll
was not found.which is correct, because it can be found at
[OutputPathBase]\x86\Release\[ProjectAssemblyName].dll
.If I use this for building (which is very poorly documented):
the test runs without that error as the build produces the output without
x86
Steps to reproduce
see above
Expected behavior
dotnet test should not assume plattform/architecture is missing from the outputpath
Actual behavior
without adjusting build, the tests expect the output to be in a different place.
Environment
The text was updated successfully, but these errors were encountered: