The --dotnet-runtime-resolution logic relies on some string parsing to understand where we placed the .dll or .exe assemblies we need to identify. I did not think about local PackageReferences that needs to be restored in a chained order.
Thus my logic extracted the first element it found in the stdout log, where it should have looked for the last.
The
--dotnet-runtime-resolution
logic relies on some string parsing to understand where we placed the.dll
or.exe
assemblies we need to identify. I did not think about localPackageReferences
that needs to be restored in a chained order.Thus my logic extracted the first element it found in the
stdout
log, where it should have looked for the last.