Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

9
  • Apparently Microsoft.TestPlatform.TestHost and Microsoft.NET.Test.Sdk is supported up to .NetCoreApp Version=v1.0 Is this the issue? Commented Feb 20, 2019 at 4:15
  • Running into the same issue, any update on this? All documentation I can find on the subject states that you should do a dotnet publish on the project in order to solve the issue, but since I'm trying to run the tests based on the build output of all test projects this doesn't seem practical (I'm guessing you are doing the same thing?) Commented Feb 25, 2019 at 20:20
  • 1
    I've created an issue for this on github: github.com/Microsoft/vstest/issues/1928 Commented Feb 25, 2019 at 20:36
  • @WouterRoos In the above issue you raised, as the answer specified dotnet publish. Can you please elaborate on that? I added what I have in my build.yaml Commented Mar 31, 2019 at 5:25
  • 1
    they recommend publishing all net core test projects using dotnet publish, which will include all necessary binaries needed to run the tests using the vstest task. I currently use the DotNetCoreCLI@2 step with command set to publish, use a minimatch pattern for the projects argument that captures all netcore test projects in the solution and using --no-build as arguments since my solution has already been built at that point. Commented Apr 1, 2019 at 7:41