System.Runtime dependency in xunit.execution.DotNetCore

[herecydev]

The NetPlatform TFM for xunit.execution.DotNetCore has a dependency on System.Runtime (4.0.20). When I target dotnet and have xunit (beta4) as the only dependency it throws errors similar to the following:

I'm guessing that the incorrect version of System.Runtime is being pulled in, 4.0.0 instead of 4.0.20. Anything I'm doing wrong here?

Thanks

[clairernovotny]

What kind of project do you have, what are your dependencies, what is your target platform?

[herecydev]

I have an xproj targeting dotnet, with the only dependency on xunit.

[bradwilson]

• If you are using DNX beta6 or earlier: revert back to xUnit.net 2.1 beta 3.
• If you are using DNX beta7 or later: Use the latest build from our CI MyGet feed: https://www.myget.org/F/xunit/ (xunit will be an rc1 build, and xunit.runner.dnx will be a beta5 build)

[bradwilson]

Also, do not target dotnet with a .xproj today. It doesn't work the way you expect it to.

[herecydev]

Okay thanks, do you have any additional information about dotnet with xproj? Oren had some confusion to begin with, but his recent blogs indicate that this should be the correct target.

[bradwilson]

For starters, dotnet is for class libraries only. If you're building an application, it needs to target one or more specific frameworks.

In addition, the dotnet target basically means "I intend to be compatible with anything which can link against System.Runtime". There is really no mechanism today to limit that to specific targets. In addition, the things you want to link against -- ASP.NET, specifically -- don't necessarily have dotnet targets themselves (looking at Microsoft.AspNet.Http.1.0.0-beta7-15511, I see dual binaries for dnx451 and dnxcore50).

If I were making a class library for use with ASP.NET today, I would follow the two-target strategy.

[herecydev]

Okay thanks, it is a class library I'm creating. I will hold off until more has been established. Cheers for the explanation.