You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm observing that when I use the Refresh Tests feature (or anything in the test explorer) in a workspace with a solution filter open, the solution filter is ignored and the build is done on the root project.
I expect the "Refresh Test" option to respect the solution filter I have active in my workspace. For large solutions, running the root solution when I am in the context of a single project increases the amount of time spent building in my dev loop unnecessarily.
Environment Information
VSCode version: 1.100.2 C# Extension: 2.76.27 Using OmniSharp: false
The text was updated successfully, but these errors were encountered:
Hi @Jxwoon, do you know who could help us dig into this ?
I noticed that after following the repro steps, even just right-click the solution AspNetCore(HttpAbstractions) and choosing Build triggers a build for AspNetCore.slnx instead of HttpAbstractions.slnf
This doesn't look like an issue in Test Explorer and it seems more related to the project system.
Is this expected behavior, or does it look like a bug ?
Describe the Issue
I'm observing that when I use the
Refresh Tests
feature (or anything in the test explorer) in a workspace with a solution filter open, the solution filter is ignored and the build is done on the root project.Steps To Reproduce
git clone --recursive https://github.com/dotnet/aspnetcore.git
cd aspnetcore
./restore.sh
src/Http
./startvscode.sh
HttpAbstractions.slnf
in VS Code.Expected Behavior
I expect the "Refresh Test" option to respect the solution filter I have active in my workspace. For large solutions, running the root solution when I am in the context of a single project increases the amount of time spent building in my dev loop unnecessarily.
Environment Information
VSCode version: 1.100.2
C# Extension: 2.76.27
Using OmniSharp: false
The text was updated successfully, but these errors were encountered: