dotnet-installer/TestAssets/TestProjects/MSBuildTestApp/MSBuildTestApp.csproj

<Project Sdk="Microsoft.NET.Sdk" ToolsVersion="15.0" xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
  <PropertyGroup>
    <OutputType>Exe</OutputType>
    <TargetFramework>netcoreapp2.0</TargetFramework>
    <RuntimeIdentifiers>win7-x64;win7-x86;osx.10.10-x64;osx.10.11-x64;ubuntu.14.04-x64;ubuntu.16.04-x64;centos.7-x64;rhel.7.2-x64;debian.8-x64</RuntimeIdentifiers>
    <RuntimeFrameworkVersion>2.0.0-beta-001509-00</RuntimeFrameworkVersion>
  </PropertyGroup>

  <ItemGroup>
    <DotNetCliToolReference Include="dotnet-portable">
      <Version>1.0.0</Version>
    </DotNetCliToolReference>
    <DotNetCliToolReference Include="dotnet-prefercliruntime">
      <Version>1.0.0</Version>
    </DotNetCliToolReference>
  </ItemGroup>
</Project>
Updating the projects files in the repo to use the SDK attribute. 2016-12-20 21:29:45 +00:00			`<Project Sdk="Microsoft.NET.Sdk" ToolsVersion="15.0" xmlns="http://schemas.microsoft.com/developer/msbuild/2003">`
dotnet-build3 Adding msbuild execution command to cli 2016-06-17 23:16:09 +00:00			`<PropertyGroup>`
			`<OutputType>Exe</OutputType>`
Moving as many of our test assets to netcoreapp2.0 as possible. I believe the only ones missing at the test packages, because tools always target 1.0. And the other ones are VSTestDotNetCore and VSTestXUnitDotNetCore, because we can't run tests on 2.0 yet. Or, when I tried it failed. I may came back to try this out later. 2017-03-02 20:46:21 +00:00			`<TargetFramework>netcoreapp2.0</TargetFramework>`
Remove OpenSUSE13 and Fedora23 since they are end of lifed. 2017-03-01 21:12:16 +00:00			`<RuntimeIdentifiers>win7-x64;win7-x86;osx.10.10-x64;osx.10.11-x64;ubuntu.14.04-x64;ubuntu.16.04-x64;centos.7-x64;rhel.7.2-x64;debian.8-x64</RuntimeIdentifiers>`
Moving as many of our test assets to netcoreapp2.0 as possible. I believe the only ones missing at the test packages, because tools always target 1.0. And the other ones are VSTestDotNetCore and VSTestXUnitDotNetCore, because we can't run tests on 2.0 yet. Or, when I tried it failed. I may came back to try this out later. 2017-03-02 20:46:21 +00:00			`<RuntimeFrameworkVersion>2.0.0-beta-001509-00</RuntimeFrameworkVersion>`
dotnet-build3 Adding msbuild execution command to cli 2016-06-17 23:16:09 +00:00			`</PropertyGroup>`

Moving the ProjectToolsCommandResolver to dotnet out of Cli.Utils because of the dependency on Microsoft.Build. Also added a EndToEnd test for tools ref using the MSBuildTestApp. 2016-10-04 04:40:24 +00:00			`<ItemGroup>`
Fixing the tools item name in csproj. Nuget used a different one then was originally at the spec. 2016-10-05 22:27:30 +00:00			`<DotNetCliToolReference Include="dotnet-portable">`
Moving the ProjectToolsCommandResolver to dotnet out of Cli.Utils because of the dependency on Microsoft.Build. Also added a EndToEnd test for tools ref using the MSBuildTestApp. 2016-10-04 04:40:24 +00:00			`<Version>1.0.0</Version>`
Fixing the tools item name in csproj. Nuget used a different one then was originally at the spec. 2016-10-05 22:27:30 +00:00			`</DotNetCliToolReference>`
Making Project Tools use the CLI shared runtime if they have the prefercliruntime in the root of their package. This allows for project tools to not have to change when a new runtime comes up as long as they are compatible with the runtime that the CLI is using. 2016-11-22 21:56:13 +00:00			`<DotNetCliToolReference Include="dotnet-prefercliruntime">`
			`<Version>1.0.0</Version>`
			`</DotNetCliToolReference>`
Moving the ProjectToolsCommandResolver to dotnet out of Cli.Utils because of the dependency on Microsoft.Build. Also added a EndToEnd test for tools ref using the MSBuildTestApp. 2016-10-04 04:40:24 +00:00			`</ItemGroup>`
dotnet-build3 Adding msbuild execution command to cli 2016-06-17 23:16:09 +00:00			`</Project>`