title: SonarQube Not Analyzing .cs Files In .NET Standard 2.0 Project
body: <p>I'm running SonarQube 7.9.1 on Windows 10 64-bit via the StartSonar.bat script. My backing database is SQL Server 2017, and my startup config is all default except the JDBC connection string and credentials for SQL Auth. </p>
  
  <p>I started SonarQube and created a new project for my Selenium test harness solution, which contains some middleware assemblies targeting .NET Framework 4.5, a framework assembly targeting .NET Standard 2.0 that takes a dependency on the middleware, and some test assemblies targeting .NET Core 2.2 that take dependency on the Selenium framework and in some cases on a few of the .NET Framework 4.5 middleware assemblies as well. </p>
  
  <p>When I run an analysis of my solution like so:</p>
  
  <pre><code>dotnet sonarscanner begin /k:"MyCompany.Selenium"; dotnet build; dotnet sonarscanner end
  </code></pre>
  
  <p>The middleware assemblies are all scanned so I can see the lines of code, bugs, vulnerabilities, code smells, etc as I'd expect but the actual framework code isn't analyzed at all:</p>
  
  <p><a href="https://i.stack.imgur.com/ID9vd.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/ID9vd.png" alt="Example of code with no metrics"></a></p>
  
  <p>My guess is that somewhere SonarQube is deciding on my behalf that the framework project is a "test" project and doesn't need code analysis, but the info I found at <a href="https://docs.sonarqube.org/latest/analysis/scan/sonarscanner-for-msbuild/" rel="nofollow noreferrer">https://docs.sonarqube.org/latest/analysis/scan/sonarscanner-for-msbuild/</a> for Detection of Test Projects indicates that project names ending in Test/Tests and MSTest projects are the only ones automatically flagged as such, and neither apply to my framework. Is there anything else I should be looking for?</p>