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

* Write an empty global.json for tests so they don't use the repo's global.json

* Create new SetupRoot variable that represents the root of core-setup. Convert usages of RepoRoot and ProjectDir to either SetupRoot or RepoRoot depending on if they need files that are at the root of the repo or are setup-specific.

* regenerate-readme-table should always target the root README.

* Make pack-managed.proj an SDK project.

* Make the root directory of the repository configurable in corehost/build.cmd and corehost/build.sh.

* Rename LICENSE.TXT to LICENSE. Set properties for the Microsoft.DotNet.Build.Tasks.SharedFramework.Sdk so we don't need to customize them during consolidation.

* Update Microsoft.DotNet.Build.SharedFramework.Sdk version.

* Update eng/Version.Details.xml
Co-Authored-By: NDavis Goodin <dagood@users.noreply.github.com>


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

In order to conform with Catalina notarization requirements, the template apphost
will be shipped after codesigning.

This commit implements a change to remove the code-signature when customizing the apphost for an app.

Testing:
- Tested the HostModel library using a locally signed version of apphost
- Verified that unsigned host can be re-signed later
- Verified that the original unsigned-apphost, and the signature-removed-apphost are binary equal.


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

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

* Use global dotnet installation if matching

Arcade guarantees that the requested version specified in global.json
is installed.

* Enforce a minimum dotnet sdk version

Specify a minimum dotnet sdk version in the sdk section global.json
which is honored by the Desktop msbuild as well. Set a roll-forward
policy so that a globally installed sdk with a more recent version can
be used when invoking a project directly.

* Use the user's nuget cache for local builds

Other dotnet repositories like CoreFx are already using the user's
nuget cache for local builds vs the repo local cache for CI builds
and no problems were reported. Switching to remove differences in builds

* Write out a test-local global.json file to ensure that the tests don't use the repo's global.json.


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

Set apphost and bundle file permission to 755₈

When building a .net core 3 app, the SDK currently simply copies the apphost template (including its permissions) from the install-location. 

This caused two problems in Unix systems:
* If the dotnet install location is write-protected, the build fails when SDK tries update the apphost (to set the app-path, etc.)  (dotnet/core-setup#8511)
* The built apphost can only be run by the owner (dotnet/core-setup#7062)

This change explicitly sets the file permissions of the Apphost in the SDK to fix the above issues.




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

The Bundler excludes PDB files by default. When looking for PDB files,
the extension is normalized by using ToLower().
This change fixes the issue to use invariant culture instead.

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

* Add sharedfx SDK reference

* Configure build to use sharedfx SDK

* Remove core-setup copy of sharedfx infra


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

On Unix systms where $TMPDIR is not set, temp-directory is currently
determined as:

/var/tmp/... (if it exists)
/tmp (if not)

However, this causes failures on systems where /var/tmp exists, but is not
writable (as is the case in AWS lambda).

This change fixes the issue with a writability check.

Fix dotnet/core-setup#7940

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

Start consuming `includedFrameworks` in the runtime config and use it to validate frameworks for natively hosted components loaded into self-contained apps.

* Test refactoring to enable self-contained app execution

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

* Update build containers to match CoreCLR's containers.

* Clean up ijwhost/CMakeLists.txt by bringing over updated function implementations in functions.cmake from CoreCLR.

* Clean up gen-buildsys-win.bat

* Clean up corehost build.sh

* Update instructions for building.


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

* Snap updates for 3.0 GA

* Updates for  review comments


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

To enable building core-setup on arm64 machines (not cross compiled), we need
to do a few things:

- Set the right TargetArchitecture

  When `TargetArchitecture` is not explicitly specified and when the currently
  running architecture is Arm64, use arm64 as the `TargetArchitecture`. Don't
  always use the currently running architecture as that doesn't play well with
  an x86 Visual Studio trying to create x64 builds.

- Use the right coreclr JIT

  If we are cross-compiling, we need to use the x86_arm64 libclrjit.so. But if
  we are building on an arm64 machine, we need to filter the list of found
  libclrjit.so files to pick the normal-RID (eg, linux-arm64) libclrjit.so from
  the two:

  ./.packages/transport.runtime.linux-arm64.microsoft.netcore.jit/<version>/runtimes/linux-arm64/native/libclrjit.so
  ./.packages/transport.runtime.linux-arm64.microsoft.netcore.jit/<version>/runtimes/x64_arm64/native/libclrjit.so

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

* Remove WindowsDesktop projects

* Remove WD package test

* Remove WinForms/WPF dependencies


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

* Enable using a live CoreCLR build when building core-setup by passing a path to a CoreCLR product directory via /p:CoreCLROverridePath.

* Enable using a live CoreFX build for Core-Setup restore.

* Grab ucrt redist from CoreCLR output directory.

* Fix overriding long-name DAC on CoreCLR-live build.

* Don't add non-existent doc files to the list of doc files to package.

* Add documentation about how to build with a local coreclr or corefx.

* PR Feedback.

* Extract out the overrides to a local targets file for the netcoreapp shared framework restore. Call out in the documentation of this build feature that it is only supported for the NETCoreApp shared framework.

* Update src/pkg/projects/netcoreapp/src/localnetcoreapp.override.targets
Co-Authored-By: NDavis Goodin <dagood@users.noreply.github.com>


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

The file entry validity check marked empty files as invalid. This is wrong, the file size must be non-negative number.

Added a test and fixed the condition.

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

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

3.0 GA snap update

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

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

* Update COM-activation.md

Update documentation.


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

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

Handle SDK target name change from ResolveFrameworkReferences to ProcessFrameworkReferences.

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

Based on the successful build and test run of dotnet/core-setup#8312, I'm updating the core-setup instructions to state that VS2019 is supported.

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

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

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

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

* Copy files over from dotnet/sdk.

* Update JSON code for ComHost to use System.Text.Json.

* Rename bundle tests folder to also make sense for other tests for Microsoft.NET.HostModel.

* Add tests for Clsidmap generation.

* Add RegFreeComManifest tests.

* PR Feedback.


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

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

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

Remove the runtime property AppDomainCompatSwitch as it's not used by CoreCLR anymore. (dotnet/core-setup#8289)

The usage of this has been removed several years ago in https://github.com/dotnet/coreclr/pull/5708. The new runtime behavior is always the one we were explicitly selecting with the property value anyway.

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

* remove 1.1 snap assets

* snapcraft.yaml updates for Sep release


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

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

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

Add NuGetAuthenticate task.

Create proxy build scripts that include pre-build auth plugin install.

Add workaround to avoid running test restore against authenticated feed.

Pass the NuGet auth env vars set by the AzDO build step into the Docker container.

Add configurability for internal publish.

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

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

Use NuGet.config, not RestoreSources

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

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

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

* Fix NonShipping packages to always be unstable

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

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