Commit migrated from https://github.com/dotnet/core-setup/commit/0366d3f06d9dadbf1c1253e8b975ce6cb3a317d5

Comhost IErrorInfo test

Commit migrated from https://github.com/dotnet/core-setup/commit/e3135aa808ffbbd9316d3e660b03b407a678a2eb

Commit migrated from https://github.com/dotnet/core-setup/commit/a480b039445763a942746f32aa173fdfc40d2276

Commit migrated from https://github.com/dotnet/core-setup/commit/92fb649965eb488cf5918d371cc1d73d323af2ff

# Conflicts:
#	eng/Version.Details.xml
#	eng/Versions.props


Commit migrated from https://github.com/dotnet/core-setup/commit/970b3a5143dfda81556f2b5efc4bfc9c053465eb

access(2) does not need to validate and fill in the buffer passed to the
kernel, so it's slightly faster.


Commit migrated from https://github.com/dotnet/core-setup/commit/7d70bbe81b4b86d491e30f957551441464c85375

Commit migrated from https://github.com/dotnet/core-setup/commit/44650f0cdc1307f7d0a451a227a1b8d75f42a3fe

fstatat(2) is equivalent to stat(2), but it takes a file descriptor for
a directory, so that lookups are always relative to that file
descriptor.  There's no need to construct a temporary std::string.


Commit migrated from https://github.com/dotnet/core-setup/commit/6a6266a1ab4ba99b3c42b16cc8dc822db35fb45f

# Conflicts:
#	eng/Version.Details.xml
#	eng/Versions.props


Commit migrated from https://github.com/dotnet/core-setup/commit/5e8221cfd2da93462ba35dc0c4bc23b0d6d3fd32

Commit migrated from https://github.com/dotnet/core-setup/commit/3b8cebc9528342972f0229314aa375f9b09d0038

Commit migrated from https://github.com/dotnet/core-setup/commit/cafcf54a8caccf388715618943cb641fd49f912f

Add some more context to them (whenever possible, too).


Commit migrated from https://github.com/dotnet/core-setup/commit/053fa0473d74176fd4aca2e4ab12d47fbd787791

# Conflicts:
#	BranchInfo.props
#	dir.props
#	src/managed/CommonManaged.props
#	src/test/HostActivation.Tests/DependencyResolution/PortableAppRidAssetResolution.cs
#	src/test/HostActivation.Tests/DependencyResolution/ResolveComponentDependencies.cs
#	tools-local/setuptools/dotnet-deb-tool/dotnet-deb-tool.csproj


Commit migrated from https://github.com/dotnet/core-setup/commit/76796fa18c0d23279f0d92205eaf3b8b62cd1a73

* Fix dev deb/rpm build script

* Fix deb/rpm versions: use --ci, fix version props


Commit migrated from https://github.com/dotnet/core-setup/commit/8f90d9b792b3da42df518da28468ef1677107113

Commit migrated from https://github.com/dotnet/core-setup/commit/5057bc7688b810721b13ae8e0fc1df54cd79c809

* Always include CoreCLR in NCA versions txt file

This makes it appear where it's expected. It shouldn't be a problem that it now appears in a package that doesn't truly use CoreCLR. If anything, it makes it easier to find, which could be useful.

* Fix M.NETCore.App.Internal build file differences

Fix GetDependencyDataFileInclusionDefaults to actually affect the condition.

Use a template for the props file and have each pkgproj fill it, so that each pkgproj can configure it. Use non-".Internal" name to refer to platform manifest to keep that filename consistent.

* Fix latest commit usage

* Fix names of deps.json and runtimeconfig.json

* Remove Packaging tools package from sfx deps json

* Add comment about props file placeholders


Commit migrated from https://github.com/dotnet/core-setup/commit/32d0950119e1537f136efc5ee5bb13b800f4bda0

* Fix VersionComparisonDate: copy from buildtools

* Adjust ShortFrameworkName placement for sfxproj

Fixes MSIs missing the framework name. This commit also adds a check to prevent regression.

* Move ProductVersion usage from static to target

Fixes the netstandard package version and the version used for the layout, which fixes its install location in the MSI. Adds regression test.


Commit migrated from https://github.com/dotnet/core-setup/commit/11c7fb051ae5a3a417990008965168dc6acd887b

Commit migrated from https://github.com/dotnet/core-setup/commit/27f0bb094c4ed99fdb44fa81ea8248ff4b21bc14

Note that in reality this is a non-issue: The leaks are only present if something fails and in case of failure the process will immediately exit anyway.

I did this mostly for my own education on how to write this correctly. And since I had the changes read, we might as well merge it.

The structures are simple enough that we can rely on RVO alone. In one case there will be a copy (when inserting the files into the list), but that should be lot faster than explicit allocation.

Also remove any default ctors defined as they don't add any value.

Commit migrated from https://github.com/dotnet/core-setup/commit/e02bb0a4fa18355495e6af653de92d75d5a26ad3

Commit migrated from https://github.com/dotnet/core-setup/commit/43118387f9edb83f0abe12120a071c988b8b9e04

Change component dependency resolution tests to not use managed test app which requires full framework to run (and is slow). Instead implement component dependency resolution into native host test app and change all tests to use that.

This makes the tests much faster and it also allows for more flexible tests (it's easy to mock shared frameworks now).

Notable refactorings:

Implement error writer redirector in the native tests - this is necessary to correctly handle multi-threaded error redirection. Using C++ templates to get multiple distinct function pointers (for each thread separately)
Split hostfxr exports into its own class which can be reused by multiple tests
Introduce hostpolicy exports
Implement case class for component dependency resolution tests with helpers and such
Added test which validates per-assembly version resolution behavior



Commit migrated from https://github.com/dotnet/core-setup/commit/2870b217650af9f49ffa1b835b998d58e25638c8

Update branding to 5.0

Commit migrated from https://github.com/dotnet/core-setup/commit/6bc158d4eb36a742a7926f85f12a0d3b8b3e9c0a

* Add '/p:Subset=' support for dev scenarios

* Fix readme table generation

* Improve VS build: update helper projects, doc

* Document Subsets better; add polish and safety

* Update windows-instructions.md, add Subsets hint


Commit migrated from https://github.com/dotnet/core-setup/commit/c9c64e72f18b6bf16a07dffa0a60fcee8477ea98

Commit migrated from https://github.com/dotnet/core-setup/commit/a77adb256164ad9028f8cd5d49427fd770539f77

Commit migrated from https://github.com/dotnet/core-setup/commit/5b613dcbf66aeb7f5a694b9fad0ec740d95ea62f

Commit migrated from https://github.com/dotnet/core-setup/commit/cf79d6fce1b6f2f9557caf2ddb4a10d1583da585

Commit migrated from https://github.com/dotnet/core-setup/commit/21217b1f4078188f9c2f1ac8390ee774db243ab1

Commit migrated from https://github.com/dotnet/core-setup/commit/ff7422d7346979b44e3cc3a9ec1235c62a57ac9e

Commit migrated from https://github.com/dotnet/core-setup/commit/3fbed74b39cd63761b9981dea4f983b678a62fce

Merge branch 'master' => 'dev/arcade-migration'

Commit migrated from https://github.com/dotnet/core-setup/commit/d7b62c4b66063d6ec7e77460d1d7587e71c48dab

# Conflicts:
#	BuildToolsVersion.txt
#	NuGet.config
#	dependencies.props
#	eng/Versions.props
#	eng/jobs/bash-build.yml
#	eng/jobs/windows-build.yml


Commit migrated from https://github.com/dotnet/core-setup/commit/a0c4047ed17874f72af66cb26085821b1649d8f8

[dev/arcade-migration] Add simple sharedfx package test project, fix PlatformManifest creation

Commit migrated from https://github.com/dotnet/core-setup/commit/99d2a27673278823e11c39d57ac25ce925fd89a5

Commit migrated from https://github.com/dotnet/core-setup/commit/c823497b00d73f33e2d55626ebda090c8db42a4e

Commit migrated from https://github.com/dotnet/core-setup/commit/a61c69df207317e6de0c18cc4e66835b71ccf06b

This is the recommended Arcade way to transfer this information. The Arcade SDK doens't support passing env vars while running tests.


Commit migrated from https://github.com/dotnet/core-setup/commit/fb43a6a3abab1b25356b7ee146586d14bb20b195

Commit migrated from https://github.com/dotnet/core-setup/commit/e611ece7a0313320b96eeea376a97219f901a8e1

The main part is to remove the `.a` file reference since we don't actually need or produce it.

Commit migrated from https://github.com/dotnet/core-setup/commit/622202134ce0103c953714879c0bb1746aaac434

Copy sources from Versions.props to NuGet.config

Commit migrated from https://github.com/dotnet/core-setup/commit/99c7780cb9e40835278152d23909c3079367b39d

Implements additional roll-forward policies for resolving a .NET
Core SDK based upon new SDK settings in `global.json`.

Two new values are now supported in `global.json` in the `sdk` settings:

* `rollForward` - the roll-forward policy to use (see below).
* `allowPrerelease` - controls whether or not preview SDKS may be resolved
(defaults to `true` to allow resolving prerelease SDKs).  


The new roll-forward policies are:

* `patch` - If the requested SDK is installed, use it. Otherwise, use the
  latest installed patch level that matches the requested major, minor, and
  feature band.
* `feature` - If the requested major, minor, and feature band is installed, use
the latest patch level for the specified feature band.  Otherwise, roll-forward
to the next available feature band and use the latest patch level for that
feature band.
* `minor` - If the requested major, minor, and feature band is installed, use
the latest patch level for the specified feature band.  Otherwise, roll-forward
to the next available feature band available for the same major version and use
the latest patch level for that feature band.
* `major` - If the requested major, minor, and feature band is installed, use
the latest patch level for the specified feature band.  Otherwise, roll-forward
to the next available feature band available without restriction and use the
latest patch level for that feature band.
* `latestPatch` - Use the latest installed patch level that matches the
requested major, minor, and feature band.
* `latestFeature` - Use the latest installed patch level for the latest
installed feature band that matches the requested major and minor version.
* `latestMinor` - Use the latest installed patch level for the latest installed
feature band for the latest installed minor version that matches the requested
major version.
* `latestMajor` - Use the absolutely latest .NET Core SDK available.

For backwards compatibility, the policy when a `version` is not specified in
`global.json` will be `latestMajor`.  The default policy when a `version` is
specified but `rollForward` is not specified will be `patch`.

Commit migrated from https://github.com/dotnet/core-setup/commit/5cd0245860335e0b307f6a46b99c6f9244887318

Retry extraction of bundle to avoid issues with locked files by AV software
Address some memory leaks


Commit migrated from https://github.com/dotnet/core-setup/commit/552dba193c0f21a03687d2f14861c7a4dcf8dd0f