* 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

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

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

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

* Copy ExecWithRetries from BuildTools

Adds working dir, log importance to ExecWithRetries. Also Inline attemptMessage and add log importance comment.

* Add WindowsDesktop sfx bundle installer, refactor

Adds bundle creation support to the packaging-tools, and factors the framework pack and runtime WiX files into a single, more flexible, "product" set of WiX files.

The old MSI generation directory is removed entirely: with the new "product" WiX files, the host and hostfxr MSI creation can move to the new system. The VS insertion nupkg generation code is also ported from PowerShell to MSBuild to fit the new system.

The old system is still used for some macOS pkgs and the macOS bundle installer, some Debian/RPM packages, and some tarballs/zips.


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

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

Previously these fields were public and so simple `.GetField("name")` worked. Now they are internal, so we need to use the overload which takes `BindingFlags` and ask for private reflection.



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

Support Visual Studio Preview Install Path discovery at Build

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

flag. Changing the code to match corefx implementation.


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

* Make apphost.exe and comhost.dll MSI id stable


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

* Enabling and conditioning the 'NuGetCommand' task.

* Update eng/jobs/windows-build.yml
Co-Authored-By: NDavis Goodin <dagood@users.noreply.github.com>

* Update eng/jobs/windows-build.yml
Co-Authored-By: NDavis Goodin <dagood@users.noreply.github.com>

* Updates per code review.


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

build


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

Simply aggregate exception happens in failed apphost deletion

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

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

port changes in SDK after Microsoft.NET.HostModel.AppHost is created

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

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

Port https://github.com/dotnet/sdk/pull/3427 by @peterhuene with my edit

This commit deletes the output apphost when the CreateAppHost task fails from
an exception.

Partially fixes dotnet/core-setup#2989

-------------
* deletes the output apphost when the `CreateAppHost` task fails from
an exception.

* aggreates the Exception for future logging from deleting the failed apphost


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

Port https://github.com/dotnet/sdk/pull/3310 by @peterhuene

The resource updater was not specifying a CharSet for the Windows API
P/Invoke signatures and therefore the ANSI versions of the APIs were
being used.

This caused an unhandled exception when customizing the apphost on
Windows when the intermediate apphost path contained Unicode characters
because the ANSI resource updating API couldn't find the file.

Fixes ABdotnet/core-setup#900429.


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

Unless intentionally disabled or building from source, always create the full platform manifest that lists assets from all platforms. With the platform manifest included in runtime packs, it needs to be generated the same across all official build jobs. Producing it locally during a default build also reduces the diff from dev to official builds.

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

Fixes "__PackageId__" placeholder appearing in outputs. Added test to ensure this doesn't happen.

Also adds platform manifest to runtime packs.

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