MSBuild target incorrect framework when using project dependencies to enforce build order

[lennoncork]

I have a solution that has multiple projects. Most of the projects are targeting multiple frameworks using the new .csproj format and one of them is only targeting a single framework (net 4.6.1). If you set up build order MSBuild attempts to build the referenced project with (what appears to be) the wrong target framework.

When building from within Visual Studio everything works fine.

When building with MSBuild (MSBuild.exe" /t:rebuild) on the command line the build fails.

The impact is we can't build on our CI server.

Attached is a test project.

ResharperTests.zip

[lennoncork]

If you remove the project dependency the build order is wrong but MSBuild succeeds. If you need to enforce build order, adding a project dependency causes MSBuild to fail.

[rainersigwald]

Probably related to #1915.

[Kassoul]

Do you have a workaround for this issue ?
Is it necessary to return to old csproj for build my solution on my CI server again ?

[lennoncork]

@Kassoul I simply created two solutions and executed them in the appropriate order on the build server. I only had one dependency so it wasn't too big of an issue. Not a great solution but it worked as a stop gap for us.

[lennoncork]

An additional workaround. As the project was a binary executable, adding the "netstandard" build target wasn't an option. However I was able to add a target that changed the output type. This allowed us to target multiple framwworks without any build errors.

  <!-- SEE https://github.com/Microsoft/msbuild/issues/2191 -->
  <PropertyGroup Condition="'$(TargetFramework)'=='netstandard1.6'">
    <!-- Update to library so can be compiled as netstandard. -->
    <OutputType>Library</OutputType>
  </PropertyGroup>

  <!-- SEE https://github.com/Microsoft/msbuild/issues/2191 -->
  <ItemGroup Condition="'$(TargetFramework)'=='netstandard1.6'">
    <!-- Remove all files from being compiled -->
    <Compile Remove="**\*.cs" />
  </ItemGroup>

[lennoncork]

Somewhat related to #3200