Xunittest MSB3277 conflicts between different assembly versions

[srivatsn]

From @fubar-coder on February 2, 2017 9:1

Steps to reproduce:

dotnet new -t Xunittest
dotnet restore
dotnet test

Output:

Build started, please wait...
C:\Program Files\dotnet\sdk\1.0.0-rc3-004530\Microsoft.Common.CurrentVersion.targets(1912,5): warning MSB3277: Found conflicts between different versions of the same dependent assembly that could not be resolved.  These reference conflicts are listed in the build log when log verbosity is set to detailed. [C:\temp\test\test.csproj]
Build completed.

Test run for C:\temp\test\bin\Debug\netcoreapp1.0\test.dll(.NETCoreApp,Version=v1.0)
Microsoft (R) Test Execution Command Line Tool Version 15.0.0.0
Copyright (c) Microsoft Corporation.  All rights reserved.

Starting test execution, please wait...
Passed   Tests.UnitTest1.Test1

Total tests: 1. Passed: 1. Failed: 0. Skipped: 0.
Test Run Successful.
Test execution time: 1,7098 Seconds

Expected:

No warning

dotnet --info

.NET Command Line Tools (1.0.0-rc3-004530)

Product Information:
 Version:            1.0.0-rc3-004530
 Commit SHA-1 hash:  0de3338607

Runtime Environment:
 OS Name:     Windows
 OS Version:  10.0.14393
 OS Platform: Windows
 RID:         win10-x64
 Base Path:   C:\Program Files\dotnet\sdk\1.0.0-rc3-004530

Copied from original issue: dotnet/sdk#786

[ErikSchierboom]

I have the same issue on my MacBook:

Eriks-MacBook-Pro:accumulate erikschierboom$ dotnet --info
.NET Command Line Tools (1.0.0-rc3-004530)

Product Information:
 Version:            1.0.0-rc3-004530
 Commit SHA-1 hash:  0de3338607

Runtime Environment:
 OS Name:     Mac OS X
 OS Version:  10.12
 OS Platform: Darwin
 RID:         osx.10.12-x64
 Base Path:   /usr/local/share/dotnet/sdk/1.0.0-rc3-004530

[AbhitejJohn]

Tagging @smadala who I believe was investigating this.

[natemcmaster]

See also dotnet/sdk#517 (comment)

[codito]

Same issue as #393. Fix is in PR #444.

[smadala]

Moving xunit.runner.visualstudio to >=2.2.0-rc1-build1247 solves issue.

[ErikSchierboom]

As @smadala said, upgrading to the latest version solves this issue.