New templated probing path is breaking dotnet test

[eerhardt]

Description

With the latest .NET Core SDK, we’ve recently added a new additionalProbingPath to the runtimeconfig.dev.json file that is breaking the dotnet test functionality.

See dotnet/sdk#1306

The issue is that we have templated this path with |arch| and |tfm| that get substituted at runtime by the host with the current process’s architecture and the app’s TFM.

{
  "runtimeOptions": {
    "additionalProbingPaths": [
      "C:\\Users\\eerhardt\\.dotnet\\store\\|arch|\\|tfm|",
      "C:\\Users\\eerhardt\\.nuget\\packages"
    ]
  }
}

The problem is that dotnet test is reading these paths and expecting them to be valid full paths:

https://github.com/Microsoft/vstest/blob/5deac05760d13de70ffae373fc4fa0ed58612cef/src/Microsoft.TestPlatform.TestHostProvider/Hosting/DotnetTestHostManager.cs#L360-L364

Steps to reproduce

Using the latest build from dotnet/sdk:

dotnet new xunit
dotnet test

Expected behavior

The test should run

Actual behavior

> dotnet test
Build started, please wait...
Build completed.

Test run for F:\DotNetTest\TestTest\bin\Debug\netcoreapp2.0\TestTest.dll(.NETCoreApp,Version=v2.0)
Microsoft (R) Test Execution Command Line Tool Version 15.3.0-preview-20170601-03
Copyright (c) Microsoft Corporation.  All rights reserved.

Starting test execution, please wait...
Illegal characters in path.
Parameter name: path

Environment

.NET Command Line Tools (2.0.0-preview2-006367)

Product Information:
 Version:            2.0.0-preview2-006367
 Commit SHA-1 hash:  3f5e5241a3

Runtime Environment:
 OS Name:     Windows
 OS Version:  10.0.15063
 OS Platform: Windows
 RID:         win10-x64
 Base Path:   F:\cli\artifacts\win10-x64\stage2\sdk\2.0.0-preview2-006367\

Microsoft .NET Core Shared Framework Host

  Version  : 2.0.0-preview2-25407-01
  Build    : 40c565230930ead58a50719c0ec799df77bddee9

dotnet/sdk build is 2.0.0-preview2-20170608-1