In some cases of nested projects, if a subproject references a local one higher in path, dotnet publish will generate .deps.json files for both projects. The actual logic finds and uses the first .deps.json file found, even though it is not for the scanned project.
This PR fixes that bug.
Attached bellow an example of a .bin folder for the SecondaryProj, generated by dotnet publish were the bug can be visualised
In some cases of nested projects, if a subproject references a local one higher in path,
dotnet publish
will generate.deps.json
files for both projects. The actual logic finds and uses the first.deps.json
file found, even though it is not for the scanned project. This PR fixes that bug.Attached bellow an example of a
.bin
folder for theSecondaryProj
, generated bydotnet publish
were the bug can be visualised