Merge branch 'MicrosoftDocs:main' into main

Author: greysk

.github/ISSUE_TEMPLATE/new-c---2017-stl-library-documentation-topic-.md

@@ -1,11 +1,13 @@
 ---
-name: 'New C++ 2017 STL library documentation topic '
+name: 'New C++ 2017 STL library documentation topic'
 about: Create a C++ 2017 doc tracking work item
 title: ''
 labels: C++17, STL doc work
 assignees: ''
-
 ---
+{Use this template to request **new** documentation to cover a feature area in the ISO C++17 standard library. Replace this text in curly braces with a description of the feature area to cover. Include a link to the proposal paper that introduced the issue (for example, `[N4086 Removing Trigraphs??!](https://wg21.link/n4086)`), or cite the chapter and section number or \[short.name] in the C++ standard that describes the feature. Add the Visual Studio version that first implements this feature. If you don't know or don't have these values, then this issue template probably isn't the right one to use.
+
+If documentation already exists on docs.microsoft.com for this feature area, and you're requesting an update, bug fix, or clarification, don't use this template. Go to the article on docs.microsoft.com and use the **This page** button in the **Feedback** section at the bottom of the document to create a GitHub issue. Include a citation for the ISO standard feature area in your description.}
 
-ISO paper for this feature: [PaperID]()
-First implemented in: VS 20YY major.minor
+ISO paper or location in the standard for this feature: {insert link or section here}
+First implemented in: {VS 20YY major.minor}

.github/ISSUE_TEMPLATE/new-c---2020-stl-library-documentation-topic-.md

@@ -1,11 +1,13 @@
 ---
-name: 'New C++ 2020 STL library documentation topic '
+name: 'New C++ 2020 STL library documentation topic'
 about: Create a C++ 2020 doc tracking work item
 title: ''
 labels: C++20, STL doc work
 assignees: ''
-
 ---
+{Use this template to request **new** documentation to cover a feature area in the ISO C++20 standard library. Replace this text in curly braces with a description of the feature area to cover. Include a link to the proposal paper that introduced the issue (for example, `[N4086 Removing Trigraphs??!](https://wg21.link/n4086)`), or cite the chapter and section number or \[short.name] in the C++ standard that describes the feature. Add the Visual Studio version that first implements this feature. If you don't know or don't have these values, then this issue template probably isn't the right one to use.
+
+If documentation already exists on docs.microsoft.com for this feature area, and you're requesting an update, bug fix, or clarification, don't use this template. Go to the article on docs.microsoft.com and use the **This page** button in the **Feedback** section at the bottom of the document to create a GitHub issue. Include a citation for the ISO standard feature area in your description.}
 
-ISO paper for this feature: [PaperID]()
-First implemented in: VS 20YY major.minor
+ISO paper or location in the standard for this feature: {insert link or section here}
+First implemented in: {VS 20YY major.minor}

.github/ISSUE_TEMPLATE/new-c---2023-stl-library-documentation-topic.md

@@ -1,11 +1,13 @@
 ---
-name: New C++ 2023 STL library documentation topic
+name: 'New C++ 2023 STL library documentation topic'
 about: Create an issue to track C++ 2023 STL doc work
 title: ''
-labels: C++23
+labels: C++23, STL doc work
 assignees: ''
-
 ---
+{Use this template to request **new** documentation to cover a feature area proposed for the ISO C++23 standard library. Replace this text in curly braces with a description of the feature area to cover. Include a link to the proposal paper that introduced the issue (for example, `[N4086 Removing Trigraphs??!](https://wg21.link/n4086)`), or cite the chapter and section number or \[short.name] in the C++ standard that describes the feature. Add the Visual Studio version that first implements this feature. If you don't know or don't have these values, then this issue template probably isn't the right one to use.
+
+If documentation already exists on docs.microsoft.com for this feature area, and you're requesting an update, bug fix, or clarification, don't use this template. Go to the article on docs.microsoft.com and use the **This page** button in the **Feedback** section at the bottom of the document to create a GitHub issue. Include a citation for the ISO standard feature area in your description.}
 
-ISO paper for this feature: [PaperID](http link to iso paper)
-First implemented in: VS 20YY major.minor
+ISO paper or location in the standard for this feature: {insert link or section here}
+First implemented in: {VS 20YY major.minor}

.github/ISSUE_TEMPLATE/new-c---stl-library-doc-topic-.md

@@ -1,11 +1,13 @@
 ---
-name: 'New C++ STL library documentation topic '
+name: 'New C++ STL library documentation topic'
 about: Create a C++ doc tracking work item
 title: ''
 labels: STL doc work
 assignees: ''
-
 ---
+{Use this template to request **new** documentation to cover a feature area in the ISO C++ standard library. Replace this text in curly braces with a description of the feature area to cover. Include a link to the tracking issue or PR in the [Microsoft/STL](https://github.com/microsoft/STL/pulls) repo that implements the feature area. If relevant, include a link to the proposal paper that introduced the issue (for example, `[N4086 Removing Trigraphs??!](https://wg21.link/n4086)`), or cite the chapter and section number or \[short.name] in the C++ standard that describes the feature. Add the Visual Studio version that first implements this feature. If you don't know or don't have these values, then this issue template probably isn't the right one to use.
+
+If documentation already exists on docs.microsoft.com for this feature area, and you're requesting an update, bug fix, or clarification, don't use this template. Go to the article on docs.microsoft.com and use the **This page** button in the **Feedback** section at the bottom of the document to create a GitHub issue. If possible, include a citation for the ISO standard feature area in your description.}
 
-ISO paper for this feature: [PaperID]()
-First implemented in: VS YYYY major.minor
+[Microsoft/STL](https://github.com/microsoft/STL/pulls) PR, ISO paper or location in the standard for this feature: {insert link or section here}
+First implemented in: {VS 20YY major.minor}

.github/ISSUE_TEMPLATE/new-c--20-compiler-doc-topic.md

@@ -0,0 +1,14 @@
+---
+name: 'New C++20 compiler documentation topic'
+about: Create a C++ doc tracking work item
+title: ''
+labels: C++20, Standard doc work
+assignees: ''
+---
+{Use this template to request **new** documentation to cover a compiler feature area in the ISO C++20 standard. Replace this text in curly braces with a description of the feature area to cover. Include a link to the proposal paper that introduced the issue (for example, `[N4086 Removing Trigraphs??!](https://wg21.link/n4086)`), or cite the chapter and section number or \[short.name] in the C++ standard that describes the feature. Add the Visual Studio version that first implements this feature. If you don't know or don't have these values, then this issue template probably isn't the right one to use.
+
+If documentation already exists on docs.microsoft.com for this feature area, and you're requesting an update, bug fix, or clarification, don't use this template. Go to the article on docs.microsoft.com and use the **This page** button in the **Feedback** section at the bottom of the document to create a GitHub issue. If possible, include a citation for the ISO standard feature area in your description.}
+
+ISO paper or location in the standard for this feature: {insert link or section here}
+
+First implemented in: {VS 20YY major.minor}

.github/ISSUE_TEMPLATE/new-c--23-compiler-doc-topic.md

@@ -0,0 +1,14 @@
+---
+name: 'New C++23 compiler documentation topic'
+about: Create a C++ doc tracking work item
+title: ''
+labels: C++23, Standard doc work
+assignees: ''
+---
+{Use this template to request **new** documentation to cover a compiler feature area in the ISO C++23 standard. Replace this text in curly braces with a description of the feature area to cover. Include a link to the proposal paper that introduced the issue (for example, `[N4086 Removing Trigraphs??!](https://wg21.link/n4086)`), or cite the chapter and section number or \[short.name] in the C++ standard that describes the feature. Add the Visual Studio version that first implements this feature. If you don't know or don't have these values, then this issue template probably isn't the right one to use.
+
+If documentation already exists on docs.microsoft.com for this feature area, and you're requesting an update, bug fix, or clarification, don't use this template. Go to the article on docs.microsoft.com and use the **This page** button in the **Feedback** section at the bottom of the document to create a GitHub issue. If possible, include a citation for the ISO standard feature area in your description.}
+
+ISO paper or location in the standard for this feature: {insert link or section here}
+
+First implemented in: {VS 20YY major.minor}

.openpublishing.publish.config.json

@@ -28,7 +28,7 @@
   "sync_notification_subscribers": null,
   "branches_to_filter": [],
   "git_repository_url_open_to_public_contributors": "https://github.com/Microsoft/cpp-docs",
-  "git_repository_branch_open_to_public_contributors": "master",
+  "git_repository_branch_open_to_public_contributors": "main",
   "skip_source_output_uploading": false,
   "need_preview_pull_request": true,
   "enable_incremental_build": true,
@@ -68,4 +68,4 @@
   "docs_build_engine": {
     "name": "docfx_v3"
   }
-}
+}

.openpublishing.redirection.json

@@ -860,6 +860,21 @@
       "redirect_url": "/cpp/build/reference/running-nmake",
       "redirect_document_id": false
     },
+    {
+      "source_path": "docs/build/manifest-generation-in-visual-studio.md",
+      "redirect_url": "/cpp/build/understanding-manifest-generation-for-c-cpp-programs#manifest-generation-in-visual-studio",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "docs/build/manifest-generation-at-the-command-line.md",
+      "redirect_url": "/cpp/build/understanding-manifest-generation-for-c-cpp-programs#manifest-generation-at-the-command-line",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "docs/build/how-to-embed-a-manifest-inside-a-c-cpp-application.md",
+      "redirect_url": "/cpp/build/understanding-manifest-generation-for-c-cpp-programs#how-to-embed-a-manifest-inside-a-c-cpp-application",
+      "redirect_document_id": false
+    },
     {
       "source_path": "docs/build/unwind-data-for-exception-handling-debugger-support.md",
       "redirect_url": "/cpp/build/exception-handling-x64",

docs/assembler/arm/arm-assembler-command-line-reference.md

@@ -1,78 +1,120 @@
 ---
 title: "ARM Assembler command-line reference"
 description: "Reference guide to the Microsoft ARM assembler command-line options."
-ms.date: "02/09/2020"
+ms.date: 05/09/2022
 ms.assetid: f7b89478-1ab5-4995-8cde-a805f0462c45
 ---
 # ARM Assembler command-line reference
 
-This article provides command-line information about the Microsoft ARM assembler, **armasm**. **armasm** assembles ARMv7 Thumb assembly language into the Microsoft implementation of the Common Object File Format (COFF). The linker can link COFF code objects produced by both the ARM assembler and the C compiler. It can link either together with object libraries created by the librarian.
+The Microsoft ARM assemblers, **armasm** and **armasm64**, support several command-line options. By default, **armasm** assembles ARMv7 Thumb assembly language into the Microsoft implementation of the Common Object File Format (COFF). The **armasm64** assembler creates COFF object code for ARM64 and ARM64EC targets. The linker can link COFF code objects produced by both the ARM assembler and the C/C++ compiler. It can link either together with object libraries created by the librarian.
 
 ## Syntax
 
 > **`armasm`** [*options*] *source_file* *object_file*\
-> **`armasm`** [*options*] **`-o`** *object_file* *source_file*
+> **`armasm`** [*options*] *source_file*
+
+> **`armasm64`** [*options*] *source_file* *object_file*\
+> **`armasm64`** [*options*] *source_file*
 
 ### Parameters
 
 *options*\
 A combination of zero or more of the following options:
 
+- **`-16`**\
+  Available only in **armasm**. Assemble source as 16-bit Thumb instructions.  This option is the default.
+
+- **`-32`**\
+  Available only in **armasm**. Assemble source as 32-bit ARM instructions.
+
+- **`-coff_thumb2_only`**\
+  Available only in **armasm**. Allow only Thumb-2 code.
+
+- **`-errorReport:`** *option*\
+   This option is deprecated. In Windows Vista and later, error reporting is controlled by [Windows Error Reporting (WER)](/windows/win32/wer/windows-error-reporting) settings.
+
 - **`-errors`** *filename*\
-   Redirect error and warning messages to *filename*.
+  **`-e`** *filename*\
+  Redirect error and warning messages to *filename*. By default, these messages are sent to `stdout`.
 
-- **`-i`** *dir*[**`;`**<em>dir</em>]\
-   Add the specified directories to the include search path.
+- **`-funcOverride:`** *function_name*\
+  Available only in **armasm64**. Emit function overriding support for *function_name*.
 
-- **`-predefine`** *directive*\
-   Specify a SETA, SETL, or SETS directive to predefine a symbol.\
-   Example: `armasm.exe -predefine "COUNT SETA 150" source.asm`\
-   For more information, see the [ARM Compiler armasm Reference Guide](https://developer.arm.com/documentation/dui0802/latest/).
+- **`-g`**\
+  Generate debugging information.
 
-- **`-nowarn`**\
-   Disable all warning messages.
+- **`-gh:SHA1`**\
+  Use the SHA-1 cryptographic hash algorithm to generate a checksum of each source file in debug info. Overrides **`-gh:SHA256`**.
 
-- **`-ignore`** *warning*\
-   Disable the specified warning. For possible values, see the section about warnings.
+- **`-gh:SHA256`**\
+  Use the SHA-256 cryptographic hash algorithm to generate a checksum of each source file in debug info. This option is on by default in Visual Studio 2022 version 17.0 and later.
+
+- **`-guard:ehcont`**[**`-`**]\
+  Generate a sorted list of the relative virtual addresses (RVA) of all the valid exception handling continuation targets for a binary. It's used at runtime for `NtContinue` and `SetThreadContext` instruction pointer validation. By default, **`-guard:ehcont`** is off and must be explicitly enabled. To explicitly disable this option, use **`-guard:ehcont-`**. This option is available in Visual Studio 2019 version 16.7 and later. The feature is supported for 64-bit processes on a 64-bit OS.
 
 - **`-help`**\
-   Print the command-line help message.
+  **`-h`**\
+  Print the command-line help message.
+
+- **`-i`** *dir*[**`;`** *dir*]\
+  Add one or more specified directories to the include search path. Separate directories by using a semi-colon (`;`).
+
+- **`-ignore`** *warning_number*\
+  Disable the specified warning number. For possible values, see [ARM Assembler diagnostic messages](arm-assembler-diagnostic-messages.md).
+
+- **`-list`** *list_file*\
+  Create a detailed listing of the generated assembly language to *list_file*. The *list_file* parameter is optional. If it's omitted, the assembler appends *`.lst`* to the base name of *source_file* to create the listing file.
 
 - **`-machine`** *machine*\
-   Specify the machine type to set in the PE header.  Possible values for *machine* are:\
-   **ARM**—Sets the machine type to IMAGE_FILE_MACHINE_ARMNT. This option is the default.\
-   **THUMB**—Sets the machine type to IMAGE_FILE_MACHINE_THUMB.
+  Specify the machine type to set in the PE header. In **armasm**, possible values for *machine* are:
+  - **ARM**—Sets the machine type to `IMAGE_FILE_MACHINE_ARMNT`. This option is the default.
+  - **THUMB**—Sets the machine type to `IMAGE_FILE_MACHINE_THUMB`.
 
-- **`-oldit`**\
-   Generate ARMv7-style IT blocks.  By default, ARMv8-compatible IT blocks are generated.
+  In **armasm64**, possible values are:
+  - **ARM64**—Sets the machine type to `IMAGE_FILE_MACHINE_ARM64`. This option is the default.
+  - **ARM64EC**—Sets the machine type to `IMAGE_FILE_MACHINE_ARM64EC`.
 
-- **`-via`** *filename*\
-   Read additional command-line arguments from *filename*.
+- **`-noesc`**\
+  **`-noe`**\
+  Ignore C-style escaped special characters, such as `\n` or `\t`.
 
-- **`-16`**\
-   Assemble source as 16-bit Thumb instructions.  This option is the default.
+- **`-nologo`**\
+  Suppress the copyright banner.
 
-- **`-32`**\
-   Assemble source as 32-bit ARM instructions.
+- **`-nowarn`**\
+  **`-now`**\
+  Disable all warning messages.
 
-- **`-g`**\
-   Generate debugging information.
+- **`-o`** *object_file*\
+  Specify the name of the object (output) file. The **`-o`** option is optional; you can instead specify an object file name as the last element of the command line.
 
-- **`-errorReport:`** *option*\
-   This option is deprecated. Starting in Windows Vista, error reporting is controlled by [Windows Error Reporting (WER)](/windows/win32/wer/windows-error-reporting) settings.
+- **`-oldit`**\
+  Available only in **armasm**. Generate ARMv7-style IT blocks. By default, ARMv8-compatible IT blocks are generated.
+
+- **`-predefine`** *directive*\
+  **`-pd`** *directive*\
+  Specify a SETA, SETL, or SETS directive to predefine a symbol.\
+  Example: `armasm.exe -predefine "COUNT SETA 150" source.asm`\
+  For more information, see the [ARM Compiler armasm Reference Guide](https://developer.arm.com/documentation/dui0802/latest/).
+
+- **`-sourcelink:`** *sourcelink_filename*\
+  *sourcelink_filename* specifies a JSON-formatted configuration file that contains a simple mapping of local file paths to URLs for source files to display in the debugger. For more information on the format of this file, see [Source Link JSON Schema](https://github.com/dotnet/designs/blob/master/accepted/2020/diagnostics/source-link.md#source-link-json-schema). Source Link is a language- and source-control agnostic system for providing source debugging for binaries. Source Link is supported for native binaries starting in Visual Studio 2017 version 15.8. For an overview of Source Link, see [Source Link](https://github.com/dotnet/designs/blob/master/accepted/2020/diagnostics/source-link.md). For information on how to use Source Link in your projects, and how to generate the SourceLink file as part of your project, see [Using Source Link](https://github.com/dotnet/sourcelink#using-source-link-in-c-projects).
+
+- **`-via`** *filename*\
+  Read extra command-line arguments from *filename*.
 
 *source_file*\
 The name of the source file.
 
 *object_file*\
-The name of the object (output) file.
+The last element of the command line can specify the name of the object (output) file. If it's omitted, and no **`-o`** option is specified, the assembler appends *`.obj`* to the base name of *source_file* to create the object file.
 
 ## Remarks
 
 The following example demonstrates how to use armasm in a typical scenario. First, use armasm to build an assembly language source (.asm) file to an object (.obj) file. Then, use the CL command-line C compiler to compile a source (.c) file, and also specify the linker option to link the ARM object file.
 
 ```cmd
-armasm myasmcode.asm -o myasmcode.obj
+armasm -o myasmcode.obj myasmcode.asm 
 cl myccode.c /link myasmcode.obj
 ```