title: Setting custom <OutputPath> in .NET Core (stop adding framework target)?
body: <p>In traditional .NET applications, it was possible to set a custom <code>&lt;OutputPath&gt;</code> of an assembly in the <code>.csproj</code> file (or via the project properties dialog). A path of e.g. <code>bin\$(Configuration)\$(Platform)</code> resulted in <code>bin\Debug\AnyCPU</code>.</p>
  
  <p>I had the habit of setting those values independent of the current build configuration (in its own <code>ItemGroup</code>, together with <code>DocumentationFile</code>, etc).</p>
  
  <p>When I'm setting up my configuration in the new .NET core <code>.csproj</code> like this...</p>
  
  <pre><code>&lt;OutputPath&gt;bin\$(Configuration)\$(Platform)&lt;/OutputPath&gt;
  &lt;DocumentationFile&gt;$(OutputPath)$(AssemblyName).xml&lt;/DocumentationFile&gt;
  </code></pre>
  
  <p>..the following folder structure gets created:</p>
  
  <pre><code>bin\
    Debug\
      AnyCPU\
        MyAssembly.xml
        netstandard1.0\
          MyAssembly.exe
  </code></pre>
  
  <p>So it seems <em>msbuild</em>, or whatever automatically appends the <code>TargetFramework</code>, which is rather annoying.</p>
  
  <p>Is there a way to truly customize the output path or disable this behavior?</p>