dotnet-installer/tools/CrossGen.Dependencies/CrossGen.Dependencies.csproj

<Project Sdk="Microsoft.NET.Sdk" ToolsVersion="15.0" xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
  <PropertyGroup>
    <TargetFramework>$(CliTargetFramework)</TargetFramework>
    <RuntimeIdentifier>$(SharedFrameworkRid)</RuntimeIdentifier>
  </PropertyGroup>

  <ItemGroup>
    <PackageReference Include="Microsoft.NETCore.App" Version="$(MicrosoftNETCoreAppPackageVersion)" />
  </ItemGroup>

</Project>
-												Update dotnet new to generate a "2.0" project.

											
										
										
											2017-01-27 23:46:55 +00:00
+								<Project Sdk="Microsoft.NET.Sdk" ToolsVersion="15.0" xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
 								  <PropertyGroup>
-												Refactor tests to use CliTargetFramework variable instead of hard-coding target framework

											
										
										
											2018-07-06 22:15:46 +00:00
+								    <TargetFramework>$(CliTargetFramework)</TargetFramework>
-												Remove CoreCLRRid property

This property was only legitimately by the project which wants to
restore `crossgen`. Since that now comes from
Microsoft.NETCore.App (i.e. the shared framework) use
SharedFrameworkRid instead.

I also ensured that we passed UsePortableLinuxSharedFramework to
dotnet restore when restoring the tool projects, so we can use the
platform specific RID when non portable build.

											
										
										
											2017-05-12 21:04:45 +00:00
+								    <RuntimeIdentifier>$(SharedFrameworkRid)</RuntimeIdentifier>
-												Update dotnet new to generate a "2.0" project.

											
										
										
											2017-01-27 23:46:55 +00:00
+								  </PropertyGroup>
-												Update Microsoft.NETCore.App to 2.0.0-beta-001507-00.

Use the crossgen and jit that comes with Microsoft.NETCore.App so we don't have to keep a corresponding CoreCLR version around.

Remove workarounds for crossgen bug https://github.com/dotnet/coreclr/issues/9118

											
										
										
											2017-02-06 20:37:39 +00:00
-												Update dotnet new to generate a "2.0" project.

											
										
										
											2017-01-27 23:46:55 +00:00
+								  <ItemGroup>
-												Updating dependency version properties in alignment with sample orchestrated build file at: https://dotnetfeed.blob.core.windows.net/orchestrated/20171129-03/orchestration-metadata/PackageVersions.props

											
										
										
											2017-12-02 04:07:48 +00:00
+								    <PackageReference Include="Microsoft.NETCore.App" Version="$(MicrosoftNETCoreAppPackageVersion)" />
-												Update dotnet new to generate a "2.0" project.

											
										
										
											2017-01-27 23:46:55 +00:00
+								  </ItemGroup>
-												Update Microsoft.NETCore.App to 2.0.0-beta-001507-00.

Use the crossgen and jit that comes with Microsoft.NETCore.App so we don't have to keep a corresponding CoreCLR version around.

Remove workarounds for crossgen bug https://github.com/dotnet/coreclr/issues/9118

											
										
										
											2017-02-06 20:37:39 +00:00
-												Only restore crossgen for the current rid.

Today we download crossgen for all supported runtime ids. This
introduces a dependency on having builds for all supported platforms
in order to build the CLI on a single platform. This is problematic
for the build from source effort because we only build artifacts for a
specific rid (the RID of the host/target).

Update the CrossGen.Dependencies project to restore for only the RID
we are building for.

											
										
										
											2017-03-21 23:52:21 +00:00
+								</Project>