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.
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.
* Add support to build with the linux portable
* Pass targets to run for the linux portable
* Address PR comments
* Update the bootstrapper version
* Address the PR comments for improving the help text
* Fixing permissions
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
* Archive asp.net package references
* Archive asp.net package references
* Change the hash input so it's the same on all platforms
* Address PR comments
* Centralize Microsoft.Net.Sdk package version
Note: Templates were omitted as their version needs to be static.
* Unifying additional missmatched versions
* prefercliruntime
whitespace threw off ReplaceAll
* Additional missed globs
* Revert SDK version for performance tests
* PR Feedback
* Roll back VSTestXunitDesktopAndNetCore.csproj SDK version
* Updating the Microsoft.Net.Sdk & Microsoft.Net.Sdk.Web versions
* Fixed merge conflicts. Had to re-update the Sdk version in one place.
* re-migrate dotnet.dll
* Revert Performance Test Projects
* Fix test test
* Add missing WithRuntime
* Disable failing test test
* Upgrade MSBuild references to 15.1.0-preview-000370-00
* Custom logger for MSBuild to receive telemetry events
Had to make the telemetry session ID a static variable so that the forwarding app could use it.
I've tested this all manually and will be writing tests after everyone signs off on the implementation here.
* Add support for sdk props/targets defaults to Migration.
* fix the transform applicator
* remove transform applicator dependency on insertion order for item merges
* defaults constructor msbuild version change
* rel/1.0.0-preview2:
Update versions of EF and scaffolding tools
Update Kestrel to 1.0.1
Update version of routing to 1.0.1
Add missing comma to F# lib project.json
Update cshtml wildcard in publishOptions
Don't print arguments in F# console app
Update F# dotnet-new templates for Preview 2 (Enrico Sada rebase)
Update MVC version to 1.0.1
Upgrade Corefx and coreclr references
fix typo in dotnet-install file
Remove the VS2012 CRT dependency from docs (#3632)
Fix README to use hostfxr download links (#3622)
Fix Oracle Linux version in README.md
Use NugetCache Sentinel for Telemetry setting.
Add Serviceable assembly attribute and nuspec attributes for all shipping CLI assemblies.
Remove showing firsttime eula for non verbs.
Adding Oracle Linux and Linux Mint to the titles
Moving Ubuntu 16.04 to be next to Ubuntu 14.04
Update README.md
* Rebase
* Remove Multi-Project Validator
* Remove projectmodelserver tests
* Enable test package creation
* Incremental test restore
* WiP
* Enable Test Asset Project restore
* Build Test Assets & Restore Test Projects
* Build Test projects
* Enable Test Execution
also moves Test Targets to a well-known CLI Version [Stage 2]
* Pass throuh existing telemetry profile
* 2-space tabs
* Revert TestTargets.cs
* WiP PR feedback
* Refactoring
* Fix naming of RestoreTestAssetPackages
* DotNetTest task
* Fix merge issue
* ExecuteWithCapturedOutput
MSBuild considers StdErr output to be failures. This causes output of any test command which is expected to produce an error to be swallowed in the test.
* Workaround for always-on tracing functionality in dotnet-test
* Fix Path Separator Windows/Unix
* Seperate package build from pack
* Windows Pathing issues
* PR Feedback
* Workaround for msbuild #773https://github.com/Microsoft/msbuild/issues/773
