-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Closed
Labels
Description
Steps to reproduce
- Create a new Console Application
- Add a new "XUnit test" project
- Edit the test project, and change the "target Framework" to "netcoreapp1.1" and the version of "Microsoft.NETCore.App" to "1.1.0"
You will have the following the CSPROJ
<Project Sdk="Microsoft.NET.Sdk" ToolsVersion="15.0">
<PropertyGroup>
<OutputType>Exe</OutputType>
<TargetFramework>netcoreapp1.1</TargetFramework>
</PropertyGroup>
<ItemGroup>
<Compile Include="**\*.cs" />
<EmbeddedResource Include="**\*.resx" />
</ItemGroup>
<ItemGroup>
<PackageReference Include="Microsoft.NETCore.App" Version="1.1.0" />
<PackageReference Include="Microsoft.NET.Test.Sdk" Version="15.0.0-preview-20161123-03" />
<PackageReference Include="xunit" Version="2.2.0-beta4-build3444" />
<PackageReference Include="xunit.runner.visualstudio" Version="2.2.0-beta4-build1194" />
</ItemGroup>
</Project>
- In Visual Studio 2017 RC, show the "Test Explorer" pane. The unit test is visible. Nice!
- Change the "Microsoft.NETCore.App" version to "1.2.0-*", and build the solution.
Expected behavior
The unit test is still visible in the "Test Explorer" pane
Actual behavior
The "Test Explorer" pane is searching a long time, and finally find no unit test anymore.
Please note that running "dotnet test -lt" with version "1.2.0-*" takes a long time, with the following warning and error on proxy connection:

If I run "dotnet test -lt" with version "1.1.0", I have the same warning but it succeed immediatly.

Environment data
dotnet --info output:
.NET Command Line Tools (1.0.0-preview4-004233)
Product Information:
Version: 1.0.0-preview4-004233
Commit SHA-1 hash: 8cec61c6f7
Runtime Environment:
OS Name: Windows
OS Version: 10.0.14393
OS Platform: Windows
RID: win10-x64
Base Path: C:\Users\Yves\AppData\Local\Microsoft\dotnet\sdk\1.0.0-preview4-004233