Unit Test Discovery Crawls

Situation: My solution consists of an Angular/Typescript web site, ASP.Net Core middle layer, some support library projects, and T-SQL database layer. The Angular website project is NOT included in the build. It is just there sharing GIT space. Problem: Whenever building the solution, Visual Studio brings the system to a crawl. Why? Because detection of Unit Tests is searching the Angular project even though it should be ignored. Angular projects have 1000's of files, none of them important to VS Unit Tests. Resolution: Visual Studio should NOT search projects that are NOT included in the build when searching for Unit Tests. Information: By removing the Angular project, and simply managing it with VS Code, Visual Studio behaves responsively. This problem occurs when using either MS Tests or NUnit. The fix should be simple because the solution properties can be examined by the Visual Studio team and skip those project folders that are not part of the build.