[NETSDKE2E][Green]There is not any response after clicking Run project associated with this file button in console app.

[yinjiehe01]

REGRESSION INFO
Not repro on C#DK April release Stable build and April prerelease4 (3.14.196)
The dotnet.testWindowEnablenextTest is default unchecked in C#DK April release Stable build and April prerelease4 (3.14.196).

INSTALL STEP

1. Install SDK 10.0.300.
2. Install latest VS Code and C# dev kit May prerelease3 3.21.203 (C# May release 2.140.9) extension.

REPRO STEPS

1. Create a console app and then open it in VS Code.
2. Clicking Run project associated with this file button on the .cs file

The dotnet.testWindowEnablenextTest is default checked in May prerelease3 C#DK

Expected
After clicking the button, there is output in the terminal.

Actual
There is not any response after clicking the button.

Notes

1. I found the dotnet.testWindowEnablenextTest is default checked after installing C#DK extension. under this setting the button works well for UT test project, but it cannot work for console apps.
2. If we uncheck it, it works well for console apps, but it cannot work for UT test project.

This phenomenon is very strange.

[balachir]

@yinjiehe01 nice find on this issue. Can you add a screenshot of the setting in your repro steps above? Also, for the REGRESSION INFO, can you additionally add a comparison with latest-released C# DK build in prerelease? I wonder if this is a setting that's turned on by default only in prerelease but not in stable channel.

[F3-L1x]

Hey, I've got the same issue.

Using the last available 3.10.x version (release) from the dropdown (being 3.10.14) it works,
by contrast using the oldest 3.20.x (release) (being 3.20.195) and current, it doesn't.

The C# Dev Kit - Test Explorer logs "[warning] No test projects to run."

[claudiaregio]

@F3-L1x sounds like you're trying to run a test file with that button correct?

[F3-L1x]

@claudiaregio Yes, I tried it the way, @yinjiehe01 did.
And after disabling the experimental "dotnet.testWindow.enableNextTest" setting, the run-button works for the "main()"-function again.

[gf-nexwise]

Confirming this on Windows too, with what looks like the exact trigger.

Repro: "Run/Debug project associated with this file" does nothing — no build, no terminal, no debug session — when the active file belongs to a non-test project. In my case an ASP.NET Core Web API with Program.cs open. The C# Dev Kit - Test Explorer output channel logs No test projects to run. on every click, so the run command is being routed to the test runner instead of launching the app.

Environment:

• C# Dev Kit 3.20.199 (pre-release)
• C# 2.140.8
• .NET SDK 10.0.201
• VS Code 1.122.1, Windows
• No test projects in the solution.

Fix / workaround: the setting dotnet.testWindow.enableNextTest defaults to true on the May pre-release. Setting it to false immediately restores Run/Debug for app projects:

// .vscode/settings.json (or User settings)
{
  "dotnet.testWindow.enableNextTest": false
}

Then run Developer: Reload Window. After that, "Run/Debug project associated with this file" builds and launches the app normally again.

Since enableNextTest is on by default in the pre-release, any solution without test projects ends up with a dead Run/Debug button until this is flipped.

[yinjiehe01]

@balachir Thank you for your addition; I have already updated it.

@yinjiehe01 nice find on this issue. Can you add a screenshot of the setting in your repro steps above? Also, for the REGRESSION INFO, can you additionally add a comparison with latest-released C# DK build in prerelease? I wonder if this is a setting that's turned on by default only in prerelease but not in stable channel.