Merge pull request #5792 from Rageking8/structure-error-references-in-range-lnk1000-lnk1220

Structure error references in range [LNK1000, LNK1220]

Author: v-dirichards

docs/error-messages/tool-errors/linker-tools-error-lnk1000.md

@@ -1,15 +1,16 @@
 ---
-description: "Learn more about: Linker Tools Error LNK1000"
 title: "Linker Tools Error LNK1000"
-ms.date: "06/18/2018"
+description: "Learn more about: Linker Tools Error LNK1000"
+ms.date: 06/18/2018
 f1_keywords: ["LNK1000"]
 helpviewer_keywords: ["LNK1000"]
-ms.assetid: 86421b9a-460a-4285-8dce-9b8257d78122
 ---
 # Linker Tools Error LNK1000
 
 > unknown error; consult documentation for technical support options
 
+## Remarks
+
 Note the circumstances of the error, then try to isolate the problem and create a reproducible test case. For information on how to investigate and report these errors, see [How to report a problem with the Visual C++ toolset or documentation](../../overview/how-to-report-a-problem-with-the-visual-cpp-toolset.md).
 
 You may get this error if you mix standard header files (for example, Windows.h) and your own files. Include a precompiled header, if any, first, then the standard headers, followed by your own header files.

docs/error-messages/tool-errors/linker-tools-error-lnk1103.md

@@ -1,14 +1,15 @@
 ---
-description: "Learn more about: Linker Tools Error LNK1103"
 title: "Linker Tools Error LNK1103"
-ms.date: "11/04/2016"
+description: "Learn more about: Linker Tools Error LNK1103"
+ms.date: 11/04/2016
 f1_keywords: ["LNK1103"]
 helpviewer_keywords: ["LNK1103"]
-ms.assetid: c8e9bc54-6a71-471c-899e-6f98122ee3c4
 ---
 # Linker Tools Error LNK1103
 
-debugging information corrupt; recompile module
+> debugging information corrupt; recompile module
+
+## Remarks
 
 This error can be caused because the compilation was terminated before a valid object file was created.
 

docs/error-messages/tool-errors/linker-tools-error-lnk1104.md

@@ -1,15 +1,16 @@
 ---
 title: "Linker Tools Error LNK1104"
 description: "Describes the Microsoft C and C++ (MSVC) linker error LNK1104, its causes, and possible solutions."
-ms.date: "12/13/2019"
+ms.date: 12/13/2019
 f1_keywords: ["LNK1104"]
 helpviewer_keywords: ["LNK1104"]
-ms.assetid: 9ca6f929-0efc-4055-8354-3cf5b4e636dc
 ---
 # Linker Tools Error LNK1104
 
 > cannot open file '*filename*'
 
+## Remarks
+
 This error is reported when the linker fails to open a file, either for reading or for writing. The two most common causes of the issue are:
 
 - your program is already running or is loaded in the debugger, and

docs/error-messages/tool-errors/linker-tools-error-lnk1106.md

@@ -1,14 +1,15 @@
 ---
-description: "Learn more about: Linker Tools Error LNK1106"
 title: "Linker Tools Error LNK1106"
-ms.date: "11/04/2016"
+description: "Learn more about: Linker Tools Error LNK1106"
+ms.date: 11/04/2016
 f1_keywords: ["LNK1106"]
 helpviewer_keywords: ["LNK1106"]
-ms.assetid: 528f7e65-04be-4966-b8af-9276837c7cda
 ---
 # Linker Tools Error LNK1106
 
-invalid file or disk full: cannot seek to location
+> invalid file or disk full: cannot seek to location
+
+## Remarks
 
 The tool could not read or write to `location` in a memory-mapped file.
 

docs/error-messages/tool-errors/linker-tools-error-lnk1107.md

@@ -1,6 +1,6 @@
 ---
-description: "Learn more about: Linker tools error LNK1107"
 title: "Linker tools error LNK1107"
+description: "Learn more about: Linker tools error LNK1107"
 ms.date: 12/10/2021
 f1_keywords: ["LNK1107"]
 helpviewer_keywords: ["LNK1107"]
@@ -9,10 +9,10 @@ helpviewer_keywords: ["LNK1107"]
 
 > invalid or corrupt file: cannot read at location *address*
 
-The tool couldn't read the file. The file may be corrupt, or have an unexpected file type.
-
 ## Remarks
 
+The tool couldn't read the file. The file may be corrupt, or have an unexpected file type.
+
 LNK1107 can occur if a file passed to the linker or related tools is corrupt. To resolve this issue, rebuild the file.
 
 LNK1107 can also occur if your build process puts an unexpected file type in the list of files passed to the tool. The linker and related tools expect to work on specific file types. For example, the linker can use object files, library files, compiled resources, and manifests to create an executable. It can't create an executable by using source files or DLLs. To resolve this issue, verify that your build process passes only the expected file types to the tool. For example, pass *`.obj`*, *`.lib`*, and *`.res`* files, not *`.cpp`*, *`.h`*, *`.dll`*, or *`.rc`* files.

docs/error-messages/tool-errors/linker-tools-error-lnk1112.md

@@ -1,10 +1,9 @@
 ---
-description: "Learn more about: Linker Tools Error LNK1112"
 title: "Linker Tools Error LNK1112"
+description: "Learn more about: Linker Tools Error LNK1112"
 ms.date: 05/23/2022
 f1_keywords: ["LNK1112"]
 helpviewer_keywords: ["LNK1112"]
-ms.assetid: 425793d8-37e6-4072-9b6e-c3d4e9c12562
 ---
 # Linker Tools Error LNK1112
 

docs/error-messages/tool-errors/linker-tools-error-lnk1113.md

@@ -1,14 +1,15 @@
 ---
-description: "Learn more about: Linker Tools Error LNK1113"
 title: "Linker Tools Error LNK1113"
-ms.date: "11/04/2016"
+description: "Learn more about: Linker Tools Error LNK1113"
+ms.date: 11/04/2016
 f1_keywords: ["LNK1113"]
 helpviewer_keywords: ["LNK1113"]
-ms.assetid: 269ff166-b143-48e9-bdf7-db6a0db59fe4
 ---
 # Linker Tools Error LNK1113
 
-invalid machine type type
+> invalid machine type type
+
+## Remarks
 
 The machine type specified in the object header is not valid.
 

docs/error-messages/tool-errors/linker-tools-error-lnk1120.md

@@ -1,15 +1,16 @@
 ---
 title: "Linker tools error LNK1120"
 description: "Describes the LNK1120 linker error, which reports the number of unresolved external symbol errors in the link."
-ms.date: "10/31/2019"
+ms.date: 10/31/2019
 f1_keywords: ["LNK1120"]
 helpviewer_keywords: ["LNK1120"]
-ms.assetid: 56aa7d36-921f-4daf-b44d-cca0d4fb1b51
 ---
 # Linker tools error LNK1120
 
 > *number* unresolved externals
 
+## Remarks
+
 Error LNK1120 reports the number of [unresolved external symbol](linker-tools-error-lnk2001.md#what-is-an-unresolved-external-symbol) errors in the current link.
 
 Each unresolved external symbol first gets reported by a [LNK2001](linker-tools-error-lnk2001.md) or [LNK2019](linker-tools-error-lnk2019.md) error. The LNK1120 message comes last, and shows the unresolved symbol error count.

docs/error-messages/tool-errors/linker-tools-error-lnk1123.md

@@ -1,14 +1,16 @@
 ---
-description: "Learn more about: Linker Tools Error LNK1123"
 title: "Linker Tools Error LNK1123"
-ms.date: "12/29/2017"
+description: "Learn more about: Linker Tools Error LNK1123"
+ms.date: 12/29/2017
 f1_keywords: ["LNK1123"]
 helpviewer_keywords: ["LNK1123"]
 ---
 # Linker Tools Error LNK1123
 
 > failure during conversion to COFF: file invalid or corrupt
 
+## Remarks
+
 Input files must have the Common Object File Format (COFF) format. If an input file is not COFF, the linker automatically tries to convert 32-bit OMF objects to COFF, or runs CVTRES.EXE to convert resource files. This message indicates that the linker could not convert the file. This can also occur when using an incompatible version of CVTRES.EXE from another installation of Visual Studio, the Windows Development Kit, or .NET Framework.
 
 > [!NOTE]

docs/error-messages/tool-errors/linker-tools-error-lnk1127.md

@@ -1,13 +1,14 @@
 ---
-description: "Learn more about: Linker Tools Error LNK1127"
 title: "Linker Tools Error LNK1127"
-ms.date: "11/04/2016"
+description: "Learn more about: Linker Tools Error LNK1127"
+ms.date: 11/04/2016
 f1_keywords: ["LNK1127"]
 helpviewer_keywords: ["LNK1127"]
-ms.assetid: 45404700-1420-4f24-97e1-efb7252ffd8f
 ---
 # Linker Tools Error LNK1127
 
-library is corrupt
+> library is corrupt
+
+## Remarks
 
 The library file is corrupt. Rebuild the library.