Update all core-setup dependencies.
Fix the app to get its shared framework from stage0 instead of what is currently checked in to the repo (which my mis-match when many builds of core-setup come out at a time).
When passing a property using the commandline, it is not flown through to "dotnet publish" calls. So instead of using "dotnet publish", just use the MSBuild task to invoke the Publish target on the reidst project. This way properties flow correctly.
I also did a little cleaning of unused build logic.
Previously, this was 1.0 app. Since stage0 no longer contains a 1.0.X
shared framework, it would not run.
Move to 2.0.0 (instead of 1.1.X since the 1.1.X shared framework will
stop being in stage0 soon as well).
dotnet-cli-build had a package reference to both CoreCLR and a new
version of Microsoft.NETCore.App in order to pull down
crossgen. Crossgen is now restored by a specific project that only
deals will pulling down crossgen, so we can remove this code.
Fixes#6093
* Allow host info passed in from the command line to override machine settings
* Simplify the logic
* Address PR comments to keep a separate HostRid and HostOSName that are static
* Rename to BuildInfo.props
* Address PR comments
* Fix the previous merge
* Fix spacing
* Address PR comments
We were only building nupkgs on windows, which meant if a non-windows machine was the last leg to finish, we were writing a blank file to the versions repo.
Fix#4399
* rel/1.0.1: (66 commits)
Update LZMA license with correct text
Bump to 2.0.0-rc5-61427-04
Remove duplicate installer suffix
Add license text to LZMA SDK license notice
Updating the SDK to 1.0.0-alpha-20170224-6
Updating both platform abstractions and dependency model to 1.0.3.
Bump Roslyn to 2.0.0-rc5-61424-02
Update Stage0 to use the latest build.
Update README with new distros.
Back porting #5597 into rel/1.0.0
Fixing the exclude pattern used by the Migration to exclude WEB SDK globs.
Remove RID from test package creation
Disable migrate and publish web app with content because CI does not have NPM
Adding an E2E test for pack with content during migration.
Fixing a failing test and adding a few more E2E tests around binplace content for migrated projects.
Fix debian_config.json on ubuntu16.10
Updating publish, pack and build of content to use None with Never/false/Never in their metadata for excluded items.
Intermediate commit to get a WIP PR out. This adds the None Update with CopyToOutputDirectory set to Never.
Switching the CopyToOutput for build and publish and the file for pack to use None Update instead of include. Also, fixed the exclude patterns for web apps.
Do not migrate Content that is already included in the Web SDK for web apps.
...
Today, if you run update-dependencies --Update and there are no
changes that need to be made (for example, you ran it previously) and
there are pending changes (i.e. git status shows diffs) the program
crashes with an unhandled exception because some code in VersionTools
is upset that there are pending changes since it thinks there should
be none.
Re-structure the code such that we don't call the method that's going
to throw when we are just updating dependencies. This also means
devs (or the composed build) who want to run this more than once do
longer have to reset changes beforehand.
Davis added support for VersionTools to be able to pull from a local
filesystem layout that looks like what we have in GitHub on
dotnet/versions.
Start to consume this so a composed build can use this logic to update
dependencies using local version information produced during the build.
