From @NikolayPianikov on November 17, 2017 15:8

I mean project output directory, nuget and etc.

• We could have the identical behavior for full and core .net, I mean when I specify TestAdapterPath for .net full it does not try to find adapters in the project output directory but for .net core it properly finds.

So I should copy my custom adapter to the root of solution directory to run tests for mixed solution (with full .net and core .net projects). And vstest could spend potentially significant time finding all required adapters when agent checkout directory has a lot of files/directories. It is very important for CI.

• It would be great if we could specify several paths separated by semicolon or add new parameter TestAdapterPaths for that to work together with other lookup methods.

Copied from original issue: microsoft/vstest-docs#103