Open DWIAltonaAnalytics opened 4 weeks ago
Addendum: If I add /property:AppendPlatformToOutputPath=True
to the dotnet test
call, it searches with plattform AnyCPU
without regard to what is configured in the csproj.
Can you please build both of the above with binary log?
/bl:dotnet-build.binlog
/bl:dotnet-test.binlog
I don't think we are assuming anything about the output path in dotnet test, we get it from msbuild via TargetPath
: https://github.com/microsoft/vstest/blob/main/src/Microsoft.TestPlatform.Build/Microsoft.TestPlatform.targets#L86
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