title: Azure CI Pipeline does not discover any tests once I have multiple 'TargetFrameworks'
body: <p>Here's the relevant part of my C# library csproj file</p>
  <pre class="lang-xml prettyprint-override"><code>&lt;Project Sdk=&quot;Microsoft.NET.Sdk&quot;&gt;
   &lt;PropertyGroup&gt;
      &lt;TargetFrameworks&gt;net46;net48&lt;/TargetFrameworks&gt;
      &lt;Platforms&gt;AnyCPU;x64&lt;/Platforms&gt;
      &lt;GenerateAssemblyInfo&gt;false&lt;/GenerateAssemblyInfo&gt;
  </code></pre>
  <p>As the question states, my Azure CI build pipeline completes successfully, but I'm noticing that the <em>Test</em> task in my pipeline takes only 1 second - and that is due to the discovery of any 'test' .dll's is failing to find anything.</p>
  <p>I am quite certain that it's due to my outdated test DLL discovery paths</p>
  <pre><code>**\$(BuildConfiguration)\*test*.dll
  !**\obj\**
  </code></pre>
  <p>The above is what USED to work, when there was only 1 target framework moniker.</p>
  <p>Now that I'm trying to support multiple frameworks, I am wondering if there's a slick way to indicate that by tweaking these discovery paths (some type of wildcard technique that I can use everywhere, across different Azure DevOps projects)</p>