Hard to choose target runtime for IDE-integrated test runner

[mgravell]

At the moment, the only way I've found to change the target runtime for the test runner is via project properties. Edit: scratch that - that doesn't actually seem to work; nothing seems to work! I have coreclr as my default, and both my test project and library project set to use a specific runtime: coreclr - and the IDE test runner is still using clr

Compared to how easy it is to play or run the console test tool (awesome drop down, thanks) and view code (top left of edit window, also awesome) for different runtimes, this feels awkward.

I don't know how much is possible, but one thing in particular that I notice: if you run a test from the editor, it still uses the project properties runtime, not the top-left-picker runtime.

[sayedihashimi]

@vijayrkn thoughts?

FYI @vijayrkn is out of office right now so it may take him some time to reply back.

[mgravell]

Not sure how or why I closed this - but this is still a really awkward thing to do; @vijayrkn - did you ever get a chance to look at this?

[vijayrkn]

Are you using the latest preview2 tooling? Test runner uses the first target framework in project.json.
For e.g: this project.json has both frameworks, VS will use netcoreapp1.0 in this case. If you change the order it will use the net451.
https://github.com/aspnet/Mvc/blob/dev/test/Microsoft.AspNetCore.Mvc.Abstractions.Test/project.json

[mgravell]

Yes I'm using all the current tooling, but ... yikes, that's not intuitive
or convenient :/

On Fri, 8 Jul 2016 17:35 Vijay Ramakrishnan, notifications@github.com
wrote:

Are you using the latest preview2 tooling? Test runner uses the first
target framework in project.json.
For e.g: this project.json has both frameworks, VS will use netcoreapp1.0
in this case. If you change the order it will use the net451.

https://github.com/aspnet/Mvc/blob/dev/test/Microsoft.AspNetCore.Mvc.Abstractions.Test/project.json

—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
#50 (comment), or mute
the thread
https://github.com/notifications/unsubscribe/AABDsLvYqCgBUYBi1RgG1QTflgOgHDF0ks5qTnw8gaJpZM4EO3H1
.

[NickCraver]

Are there planned improvements to this?

[vijayrkn]

There is a work item to support running tests for all frameworks in project.json so that switching frameworks wont be required. This needs the trait support to be implemented first. (https://github.com/dotnet/cli/issues/2252)

[mderriey]

/cc @plioi looks like what we talked about re: tests in Parsley

[mlorbetske]

TFS Bug#241358

[webtools-bot]

The GitHub Issue Tracker for the aspnet/Tooling repo is being deprecated in favor of Visual Studio's Report a Problem tool.

If this issue is still a problem with the RTW release of Visual Studio 2017, please report a new issue using the Report a Problem tool. While you can still use .NET Core and ASP.NET Preview tools with Visual Studio 2015, Visual Studio 2017 is now the officially supported tool for developing .NET Core and ASP.NET Core projects.

By using the Report a Problem tool (available in both VS 2017 and VS 2015), you can collect detailed information about the problem, and send it to Microsoft with just a few button clicks. See Visual Studio's Talk to Us page for more details.

Please use the discussion topic here for feedback and questions on the deprecation of this issue tracker. Thanks!

[mlorbetske]

This is now being tracked on the Microsoft/vstest repo as microsoft/vstest#624 and microsoft/vstest#298