Structure error references in range [LNK1221, LNK2000]

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

@@ -1,14 +1,15 @@
 ---
-description: "Learn more about: Linker Tools Error LNK1221"
 title: "Linker Tools Error LNK1221"
-ms.date: "11/04/2016"
+description: "Learn more about: Linker Tools Error LNK1221"
+ms.date: 11/04/2016
 f1_keywords: ["LNK1221"]
 helpviewer_keywords: ["LNK1221"]
-ms.assetid: 70654bf9-1520-4fa3-a063-1219dd88abf7
 ---
 # Linker Tools Error LNK1221
 
-a subsystem can't be inferred and must be defined
+> a subsystem can't be inferred and must be defined
+
+## Remarks
 
 The linker does not have enough information to infer which subsystem you want to target.
 

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

@@ -1,14 +1,15 @@
 ---
-description: "Learn more about: Linker Tools Error LNK1223"
 title: "Linker Tools Error LNK1223"
-ms.date: "11/04/2016"
+description: "Learn more about: Linker Tools Error LNK1223"
+ms.date: 11/04/2016
 f1_keywords: ["LNK1223"]
 helpviewer_keywords: ["LNK1223"]
-ms.assetid: c4728c36-daee-462f-a1c7-8733dcdec88e
 ---
 # Linker Tools Error LNK1223
 
-invalid or corrupt file: file contains invalid .pdata contributions
+> invalid or corrupt file: file contains invalid .pdata contributions
+
+## Remarks
 
 For RISC platforms that use pdata, this error will occur if the compiler emitted a .pdata section with unsorted entries.
 

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

@@ -1,13 +1,14 @@
 ---
-description: "Learn more about: Linker Tools Error LNK1224"
 title: "Linker Tools Error LNK1224"
-ms.date: "11/04/2016"
+description: "Learn more about: Linker Tools Error LNK1224"
+ms.date: 11/04/2016
 f1_keywords: ["LNK1224"]
 helpviewer_keywords: ["LNK1224"]
-ms.assetid: e190b5d0-ce0c-4f65-8cc0-753f1cc9758a
 ---
 # Linker Tools Error LNK1224
 
-invalid image base address
+> invalid image base address
+
+## Remarks
 
 You specified an invalid base address for the image. Base addresses must be 64KB aligned (the last four hex digits must be zero) and image base must fit within a 32-bit signed or unsigned value.

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

@@ -1,10 +1,9 @@
 ---
-description: "Learn more about: Linker Tools Error LNK1237"
 title: "Linker Tools Error LNK1237"
+description: "Learn more about: Linker Tools Error LNK1237"
 ms.date: 06/29/2022
 f1_keywords: ["LNK1237"]
 helpviewer_keywords: ["LNK1237"]
-ms.assetid: 8722ffa8-096a-4bb0-85f9-f3aa0e10872a
 ---
 # Linker Tools Error LNK1237
 
@@ -20,7 +19,7 @@ To resolve LNK1237, don't use **`/GL`** to compile the symbol, or use [`/INCLUDE
 
 ## Example
 
-The following sample generates LNK1237. To resolve this error, don't initialize the array in `LNK1237_a.cpp` and add **`/include:__chkstk`** to the link command.
+The following example generates LNK1237. To resolve this error, don't initialize the array in `LNK1237_a.cpp` and add **`/include:__chkstk`** to the link command.
 
 Source file `LNK1237_a.cpp`:
 

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

@@ -1,13 +1,14 @@
 ---
-description: "Learn more about: Linker Tools Error LNK1240"
 title: "Linker Tools Error LNK1240"
-ms.date: "11/04/2016"
+description: "Learn more about: Linker Tools Error LNK1240"
+ms.date: 11/04/2016
 f1_keywords: ["LNK1240"]
 helpviewer_keywords: ["LNK1240"]
-ms.assetid: 7d0e065d-1015-4df0-8370-79c3cf045e1c
 ---
 # Linker Tools Error LNK1240
 
-failed to compile IDL content
+> failed to compile IDL content
+
+## Remarks
 
 The linker spawned MIDL to compile embedded IDL but there was a problem. Check the errors specified by MIDL.

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

@@ -1,14 +1,15 @@
 ---
-description: "Learn more about: Linker Tools Error LNK1241"
 title: "Linker Tools Error LNK1241"
-ms.date: "11/04/2016"
+description: "Learn more about: Linker Tools Error LNK1241"
+ms.date: 11/04/2016
 f1_keywords: ["LNK1241"]
 helpviewer_keywords: ["LNK1241"]
-ms.assetid: 7b8b52eb-0231-4521-b52a-2bce8d3e8956
 ---
 # Linker Tools Error LNK1241
 
-resource file 'resource file' already specified
+> resource file 'resource file' already specified
+
+## Remarks
 
 This error is generated if you run **cvtres** manually from the command line and if you then pass the resulting .obj file to the linker in addition to other .res files.
 

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

@@ -1,14 +1,15 @@
 ---
-description: "Learn more about: Linker Tools Error LNK1245"
 title: "Linker Tools Error LNK1245"
-ms.date: "11/04/2016"
+description: "Learn more about: Linker Tools Error LNK1245"
+ms.date: 11/04/2016
 f1_keywords: ["LNK1245"]
 helpviewer_keywords: ["LNK1245"]
-ms.assetid: 179c8165-ffbb-44cd-9f24-5250f29577cc
 ---
 # Linker Tools Error LNK1245
 
-invalid subsystem 'subsystem' specified; /SUBSYSTEM must be WINDOWS, WINDOWSCE, or CONSOLE
+> invalid subsystem 'subsystem' specified; /SUBSYSTEM must be WINDOWS, WINDOWSCE, or CONSOLE
+
+## Remarks
 
 [/clr](../../build/reference/clr-common-language-runtime-compilation.md) was used to compile the object and one of the following conditions was true:
 

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

@@ -1,6 +1,6 @@
 ---
-description: "Learn more about: Linker Tools Error LNK1248"
 title: "Linker Tools Error LNK1248"
+description: "Learn more about: Linker Tools Error LNK1248"
 ms.date: 08/31/2022
 f1_keywords: ["LNK1248"]
 helpviewer_keywords: ["LNK1248"]

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

@@ -1,22 +1,25 @@
 ---
-description: "Learn more about: Linker Tools Error LNK1256"
 title: "Linker Tools Error LNK1256"
-ms.date: "11/04/2016"
+description: "Learn more about: Linker Tools Error LNK1256"
+ms.date: 11/04/2016
 f1_keywords: ["LNK1256"]
 helpviewer_keywords: ["LNK1256"]
-ms.assetid: 55b64b2b-a56b-436c-a55e-ec9c6dcb050e
 ---
 # Linker Tools Error LNK1256
 
-ALINK operation failed : reason
+> ALINK operation failed : reason
+
+## Remarks
 
 A common reason for LNK1256 is an incorrect version number for an assembly. The value 65535 is not allowed for any part of the assembly version number. The valid range for assembly versions is 0 - 65534.
 
 LNK1256 can also be caused if ALINK could not find the named key container. Delete the key container and add it again to the strong name CSP by using [Sn.exe (Strong Name Tool)](/dotnet/framework/tools/sn-exe-strong-name-tool).
 
 Another reason for LNK1256 is a version mismatch between the linker and Alink.dll. This can be caused by a corrupted Visual Studio installation. Use **Programs and Features** in the Windows Control Panel to repair or reinstall Visual Studio.
 
-The following sample generates LNK1256:
+## Example
+
+The following example generates LNK1256:
 
 ```cpp
 // LNK1256.cpp

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

@@ -1,14 +1,15 @@
 ---
-description: "Learn more about: Linker Tools Error LNK1264"
 title: "Linker Tools Error LNK1264"
-ms.date: "11/04/2016"
+description: "Learn more about: Linker Tools Error LNK1264"
+ms.date: 11/04/2016
 f1_keywords: ["LNK1264"]
 helpviewer_keywords: ["LNK1264"]
-ms.assetid: 23b1aad7-d382-42c1-bae8-db68575c57a8
 ---
 # Linker Tools Error LNK1264
 
-/LTCG:PGINSTRUMENT specified but no code generation required; instrumentation failed
+> /LTCG:PGINSTRUMENT specified but no code generation required; instrumentation failed
+
+## Remarks
 
 **/LTCG:PGINSTRUMENT** was specified but no .obj files were found that were compiled with [/GL](../../build/reference/gl-whole-program-optimization.md). Instrumentation cannot take place and the link failed. There must be at least one .obj file on the command line that is compiled with **/GL** so that the instrumentation can occur.
 

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

@@ -1,14 +1,15 @@
 ---
-description: "Learn more about: Linker Tools Error LNK1277"
 title: "Linker Tools Error LNK1277"
-ms.date: "11/04/2016"
+description: "Learn more about: Linker Tools Error LNK1277"
+ms.date: 11/04/2016
 f1_keywords: ["LNK1277"]
 helpviewer_keywords: ["LNK1277"]
-ms.assetid: afca3de0-50cc-4140-af7a-13493a170835
 ---
 # Linker Tools Error LNK1277
 
-object record not found in pgd (filename)
+> object record not found in pgd (filename)
+
+## Remarks
 
 When using [/LTCG:PGOPTIMZE](../../build/reference/ltcg-link-time-code-generation.md), the path of one of the input .lib, def, or .obj files was different from the path on which they were found during /LTCG:PGINSTRUMENT. This may be explained by a change in the LIB environment variable after /LTCG:PGINSTRUMENT. The full path to the input files is stored in the .pgd file.
 

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

@@ -1,13 +1,14 @@
 ---
-description: "Learn more about: Linker Tools Error LNK1282"
 title: "Linker Tools Error LNK1282"
-ms.date: "11/04/2016"
+description: "Learn more about: Linker Tools Error LNK1282"
+ms.date: 11/04/2016
 f1_keywords: ["LNK1282"]
 helpviewer_keywords: ["LNK1282"]
-ms.assetid: 99c13f52-eb80-46ce-a5b9-4537583e32a9
 ---
 # Linker Tools Error LNK1282
 
-unable to /REBASE file; it has been signed
+> unable to /REBASE file; it has been signed
+
+## Remarks
 
 You attempted to change the base address of a signed assembly with the /REBASE option for [editbin](../../build/reference/editbin-reference.md). To do this, first change the base address and then sign the assembly.

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

@@ -1,13 +1,14 @@
 ---
-description: "Learn more about: Linker Tools Error LNK1287"
 title: "Linker Tools Error LNK1287"
-ms.date: "11/04/2016"
+description: "Learn more about: Linker Tools Error LNK1287"
+ms.date: 11/04/2016
 f1_keywords: ["LNK1287"]
 helpviewer_keywords: ["LNK1287"]
-ms.assetid: 48dc379d-370c-42f6-8028-5bbcf1cc88bd
 ---
 # Linker Tools Error LNK1287
 
-invalid managed entry point function
+> invalid managed entry point function
+
+## Remarks
 
 The entry point is not valid for a managed image. The return type of a managed entry point function can only be **`void`** or **`int`**. The type of the parameter of a managed entry point function can only be **`void`** or `String []`.

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

@@ -1,14 +1,15 @@
 ---
-description: "Learn more about: Linker Tools Error LNK1296"
 title: "Linker Tools Error LNK1296"
-ms.date: "11/04/2016"
+description: "Learn more about: Linker Tools Error LNK1296"
+ms.date: 11/04/2016
 f1_keywords: ["LNK1296"]
 helpviewer_keywords: ["LNK1296"]
-ms.assetid: f94a3d18-5411-456b-966f-89810fdcfe60
 ---
 # Linker Tools Error LNK1296
 
-unable to load filename
+> unable to load filename
+
+## Remarks
 
 The given DLL was unavailable.
 

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

@@ -1,14 +1,15 @@
 ---
-description: "Learn more about: Linker Tools Error LNK1301"
 title: "Linker Tools Error LNK1301"
-ms.date: "11/04/2016"
+description: "Learn more about: Linker Tools Error LNK1301"
+ms.date: 11/04/2016
 f1_keywords: ["LNK1301"]
 helpviewer_keywords: ["LNK1301"]
-ms.assetid: 760da428-7182-4b25-b20a-de90d4b9a9cd
 ---
 # Linker Tools Error LNK1301
 
-LTCG clr modules found, incompatible with /LTCG:parameter
+> LTCG clr modules found, incompatible with /LTCG:parameter
+
+## Remarks
 
 A module compiled with /clr and /GL was passed to the linker along with one of the profile guided optimizations (PGO) parameters of /LTCG.
 
@@ -30,7 +31,7 @@ For more information, see:
 
 ## Example
 
-The following sample generates LNK1301:
+The following example generates LNK1301:
 
 ```cpp
 // LNK1301.cpp

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

@@ -1,14 +1,15 @@
 ---
-description: "Learn more about: Linker Tools Error LNK1302"
 title: "Linker Tools Error LNK1302"
-ms.date: "11/04/2016"
+description: "Learn more about: Linker Tools Error LNK1302"
+ms.date: 11/04/2016
 f1_keywords: ["LNK1302"]
 helpviewer_keywords: ["LNK1302"]
-ms.assetid: aea3c753-c2c4-4249-bbc3-f2d4f0164b5e
 ---
 # Linker Tools Error LNK1302
 
-only support linking safe .netmodules; unable to link file .netmodule
+> only support linking safe .netmodules; unable to link file .netmodule
+
+## Remarks
 
 A .netmodule (compiled with **/LN**) was passed to the linker in a user attempt to invoke MSIL linking.  A C++ module is valid for MSIL linking if it is compiled with **/clr:safe**.
 

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

@@ -1,15 +1,16 @@
 ---
-description: "Learn more about: Linker Tools Error LNK1306"
 title: "Linker Tools Error LNK1306"
-ms.date: "11/04/2016"
+description: "Learn more about: Linker Tools Error LNK1306"
+ms.date: 11/04/2016
 f1_keywords: ["LNK1306"]
 helpviewer_keywords: ["LNK1306"]
-ms.assetid: fad1df6a-0bd9-412f-b0d1-7c9bc749c584
 ---
 # Linker Tools Error LNK1306
 
 > DLL entry point function cannot be managed; compile to native
 
+## Remarks
+
 `DllMain` cannot be compiled to MSIL; it must be compiled to native.
 
 To resolve this issue,
@@ -30,7 +31,7 @@ For more information, see:
 
 ## Example
 
-The following sample generates LNK1306.
+The following example generates LNK1306.
 
 ```cpp
 // LNK1306.cpp

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

@@ -1,10 +1,9 @@
 ---
-description: "Learn more about: Linker Tools Error LNK1309"
 title: "Linker Tools Error LNK1309"
-ms.date: "11/04/2016"
+description: "Learn more about: Linker Tools Error LNK1309"
+ms.date: 11/04/2016
 f1_keywords: ["LNK1309"]
 helpviewer_keywords: ["LNK1309"]
-ms.assetid: 10146071-883f-4849-97d1-c7468f90efbb
 ---
 # Linker Tools Error LNK1309