If this variable is set in your environment, running `build.sh -t` will
pass it to the test harness, causing these tests to fail.

Teach Command.EnvironmentVariable() to handle `null` as an empty string,
so that if the DotNetRoot() extension method is called with a `null`
parameter, the $DOTNET_ROOT and $DOTNET_ROOT(x86) environment variables
are essentially unset as far as pal::getenv() is concerned.


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

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

* Localization update including term changes.

* eevert "revert localization update including term changes."

This reverts commit dotnet/core-setup@3863cbbb23b0991679362a2c49ed16a659a43728.

revert localization update.

* Localization update for PTB term changes.

* Convert checked-in CRLF to LF


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

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

* Update dependencies from https://github.com/dotnet/arcade build 20190904.31

- Microsoft.DotNet.VersionTools.Tasks - 1.0.0-beta.19454.31
- Microsoft.DotNet.Arcade.Sdk - 1.0.0-beta.19454.31
- Microsoft.DotNet.Build.Tasks.Feed - 2.2.0-beta.19454.31
- Microsoft.DotNet.Build.Tasks.Packaging - 1.0.0-beta.19454.31

* Enable post-build publishing for 3.1 channels and fixup legacy channle names


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

Make static hostpolicy context a shared pointer so that it won't get
destructed as part of exit if it is in use by another thread

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

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

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

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

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

* Bundles: Align assemblies at a 4K boundary

Align assemblies at a 4K boundary to facilitate their load
directly from the (memory-mapped) bundle by the runtime.

Assemblies are written with 4K alignment to facilitate loading from bundle
Remaining files (native binaries and other files) are written without alignment.

The unaligned files are written first, followed by the aligned files,
and finally the bundle manifest.

Further work is required to order the files better in order to minimize bundle size.

Bundle size change due to this change:
Console self-contained: Increased by 0.3 MB (67.95 -> 68.26)
WebAPI self-contained: Increased by 0.5 MB (84.53 -> 85.10)

The 4K alignment is strictly not necessary in order to map the contents of the bundle for loading.

MAPMapViewOfFile already maps sections that are not 4K aligned (by mapping extra bytes before/after each section, possibly redundantly). With some additional work to CorUnix::InternalMapViewOfFile and MAPMapViewOfFile, loading from single-exe bundles can also be made to work without the requirement for 4K alignment (at least as well as the section-loading currently works).

Checking in this changes provides a HostModel package that is 4K aligned for experimentation/prototyping. Once the changes to map.cpp are implemented, the change can be reverted.


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

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

Incorporates source-build patch that was added to exclude WindowsDesktop from NuGet restore. Adds logic to determine RestoreAllBuildRids based on DotNetBuildFromSource, so that source-build doesn't have to pass in the '/p:RestoreAllBuildRids=false' override argument.

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

Allow the SDK to restore SourceLink and find its MSBuild props and targets files. These are used to fetch Git information.

Use Arcade-generated '_version.c'. The new '_version.c' is identical to the old 'version.cpp'. The host build.sh generated an empty 'version.cpp' when it doesn't already exist at the specified path, which caused the "No version information" message to be included.

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

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

* Set up auto-update for infra packages

* React to packaging tools centralizing specs


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

* Fix bundle installer signing

* Remove SignMsiFiles.proj MSBuild cycle

This OrderProjectReference is unnecessary: ensuring the MSI files are signed before bundling them is already handled by the infrastructure in the GetBundledMsiFiles target.


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

This reverts commit dotnet/core-setup@4b82b1edad5fb7b1f9e865a8429c2da33c921854.

The changes break VS and may even change the default on Windows to x86
instead of x64.

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

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

* Split blob publish into stages run before Arcade

The Arcade publish stages contain the job that promotes the build, causing auto-update PRs to be generated. This means that running installer publish after Arcade can cause a temporarily broken update PR. To fix this, publish blobs before the Arcade stages.

Leave dotnet/versions publish and build finalization until after the Arcade stages, so that they still only happen after the nupkgs are published.

* Changes per feedback

Remove "Custom" verbiage, not useful and in some cases now incorrect.

Order publish.yml stages by dependency to help readability.


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

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

* Single-File: MemoryMap the bundle file

This changes makes a few changes in preparation for
loading IL files from the single-file bundle.

**Memory Mapping**

At startup, the entire bundle-file is memory mapped.
The individual embedded files are then extracted out to actual files on disk on startup.
However, this change will facilitate later checkins to:
* Loading files directly from bundle (ex: IL files using PELoader, config files using memory-streams, etc ).
* Extracting out files to disk lazily
Further details are available in [this document](https://github.com/dotnet/designs/blob/master/accepted/single-file/design.md#the-host)

**Refactoring**

* Static bundle_runner: The bundle_runner is made a static class that holds a global pointer
  to the memory-mapped application bundle, and meta-data about the contents.
  This facilitates the implementation of call-backs for accessing content directly from the bundle,
  as explained in [this document](https://github.com/dotnet/designs/blob/master/accepted/single-file/direct.md)

* A few new classes are created by factoring out functionality from bundle_runner
   * Extractor: Functionality for extracting contents of a bundle to files on disk.
   * Reader: This is a helper class that implements sequentional reading on memory-mapped bundle file.
   * dir-Util: Extraction directory handling utilities that assist in processing the bundle.

* Naming: bundle::bundle_runner is renamed as bundle::runner to remove the redundancy.
  Similarly, the newly refactored classes are named bundle::extractor and bundle::reader.

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

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

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

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

Copy over branding from .NET Core Runtime bundle installer to Windows Desktop Runtime bundle installer, then remove the "WelcomeHeaderMessage" and "WelcomeDescription" strings that could be confusing in the WD context. The result is a WindowsDesktop bundle installer with no useful description, but with UI localization.

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

* When installing the SharedHost; copy all files to the traditional default install location: 'ProgramFiles'\dotnet



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

The above test was disabled in PR dotnet/core-setup#6885 because the lab runs
showed failures because of "not enough disk space"

This PR now enables the test, since the test job no longer uses the hosted pool.

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

* Switch to stage-based publishing with custom steps

* Workaround: allow known symbol publisher warnings

Use Arcade-supported symbol publish workaround

* Workaround: run gather drop dry to avoid flakiness

* Use hosted pool for custom publish


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

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

- Set the right TargetArchitecture

  Use the currently running architecture to decide the HostArch. Use that
  as the default value of TargetArchitecture, unless another value was
  provided by the build configuration.

- 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 host, we need to pick the normal-RID
  (eg, linux-arm64) libclrjit.so from the two:

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

- Use a version of SourceLink that supports arm64

  We need to upgrade SourceLink to a version that contains
  https://github.com/dotnet/sourcelink/pull/288. This commit just
  updates it to the latest version.

Fixes dotnet/core-setup#7653

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

This change ports the Import [AppHost updater tests](https://github.com/dotnet/sdk/blob/dotnet/core-setup@a1cc8ec5a9741a5a2191fe022e12dd8a7f7348c7/src/Tasks/Microsoft.NET.Build.Tasks.UnitTests/GivenAnAppHost.cs) previously in SDK branch to work with HostModel library.

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

* HostModel: Retry ResourceUpdate on Win32 File-Lock error

On Win32 PE files, the SDK copies resources on the AppHost binary
from the intermediate assembly.

This update is performed using native Win32 operations.
This change retries the resource update if the operation fails
because the file is locked (say because of AntiVirus scan).

This change is similar to: https://github.com/dotnet/core-setup/pull/7617
which handles failures in managed code via IOException.

The Retry logic is factored out to the RetryUtil class. Currently the
HostWriter is the only client for the class. But it is made public
because other components (like Bundler) may use it in future.


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

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

* Fixes https://github.com/dotnet/wpf/issues/1423

Add PresentationUI.dll to WPF profile

* Update WPF Dependencies


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

Update Retry counters in HostWriter to match the
retry numbers in AppHost.

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

* HostModel: Retry updates on IO error

The HostModel implements services for updating the AppHost DLL
- Write App-dll name
- Set GUI/CUI bit
- Read/Write BundleHeader marker

These updates involve multiple file open/close operations.
An Antivirus scanner may intercept in-between and cause these operations
to fail with IO-Error.

So, this change adds a few retries to the IO operations, similar to
https://github.com/dotnet/core-setup/pull/7135

Fix for dotnet/core-setup#7597


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

Skip framework validation for secondary components loaded into a self-contained app (dotnet/core-setup#7618)

* Skip framework validation for secondary components loaded into a
self-contained app

* Add tests for loading a component in a self-contained app


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

* Reference WPF theme assemblies by default

* Fix test expecting >0 ReferencedByDefault attrs


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

Also fix a small bug where both the new and old infrastructure were creating a zip for the NETCoreApp sfx. This wasn't causing a problem in parallel because they are ordered, but it made it unclear to a reader which infra was responsible for the zip.

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

* Add support for ProgID registration

* Update COM activation documentation


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