dotnet-installer/TestAssets/TestProjects/MSBuildIntegration/build.props

<Project ToolsVersion="14.0" DefaultTargets="Validate">
  <Import Project="$([MSBuild]::GetDirectoryNameOfFileAbove($(MSBuildThisFileDirectory), dir.props))\dir.props" />

  <ItemGroup>
    <Sdk Include="Microsoft.NET.Sdk" Version="$(CLI_NETSDK_Version)" />
  </ItemGroup>
</Project>
MSBuildSDKsPath (#4824) * Tests in place * Implementation 2016-11-24 07:54:44 +00:00			`<Project ToolsVersion="14.0" DefaultTargets="Validate">`
Include Microsoft.Net.Sdk in CLI layout (#4895) * WiP * Update test * Working version of Net SDK * Latest SDK doesn't work as packageref * DCR + PR * Harden CLI tests against #4884 2016-12-03 22:19:54 +00:00			`<Import Project="$([MSBuild]::GetDirectoryNameOfFileAbove($(MSBuildThisFileDirectory), dir.props))\dir.props" />`

MSBuildSDKsPath (#4824) * Tests in place * Implementation 2016-11-24 07:54:44 +00:00			`<ItemGroup>`
use Sdks attribute in `dotnet new` templates (#4916) * Move dotnet-new templates to Sdk attribute * Update to MSBuild 15.1.0-preview-000454-01 To pick up a fix for Microsoft/msbuild#1431. * Fix template newlines * Fix casing on Microsoft.Net.Sdk * Move migration test csproj's to Sdk attribute * Disable parallel sdk restore Each SDK restore operation will try to manipulate the same assets.json file since the dependency name&version are injected into a common csproj file. This can cause runtime failures when two NuGets try to restore the project at once. * Make casing of SDK 'NET' and not 'Net' * Remove redundatn imports * Fix test string * Additional race * Replacing the SDK with the Web.Sdk when it is a Web project. * Fixing the test by writting the csproj before running the migration rule. 2016-12-05 06:31:58 +00:00			`<Sdk Include="Microsoft.NET.Sdk" Version="$(CLI_NETSDK_Version)" />`
MSBuildSDKsPath (#4824) * Tests in place * Implementation 2016-11-24 07:54:44 +00:00			`</ItemGroup>`
			`</Project>`