@@ -1,15 +1,19 @@
 ---
-description: "Learn more about: .Ilk Files as Linker Input"
-title: ".Ilk Files as Linker Input"
-ms.date: "11/04/2016"
-helpviewer_keywords: ["ILK files", ".ilk files"]
+description: "Learn more about: .ilk files as linker input"
+title: ".ilk files as linker input"
+ms.date: 09/07/2022
+helpviewer_keywords: [".ilk files", ".ilk files"]
 ms.assetid: 7324c104-9e5d-423d-b268-b59f92607bf2
 ---
-# .Ilk Files as Linker Input
+# `.ilk` files as linker input
 
-When linking incrementally, LINK updates the .ilk status file that it created during the first incremental link. This file has the same base name as the .exe file or the .dll file, and it has the extension .ilk. During subsequent incremental links, LINK updates the .ilk file. If the .ilk file is missing, LINK performs a full link and creates a new .ilk file. If the .ilk file is unusable, LINK performs a nonincremental link. For details about incremental linking, see the [Link Incrementally (/INCREMENTAL)](incremental-link-incrementally.md) option.
+The linker creates and uses a *`.ilk`* database file for incremental link information.
+
+## Remarks
+
+When linking incrementally, LINK updates the *`.ilk`* status file that it created during the first incremental link. This file has the same base name as the target EXE or DLL file, and it has the extension *`.ilk`*. During subsequent incremental links, LINK updates the *`.ilk`* file. If the *`.ilk`* file is missing, LINK performs a full link and creates a new *`.ilk`* file. If the *`.ilk`* file is unusable, LINK performs a non-incremental link. For more information about incremental linking, see the [`/INCREMENTAL` (Link incrementally)](incremental-link-incrementally.md) linker option. For information about how to specify the name and location of the file, see [`/ILK` (Name incremental database file)](./ilk-name-incremental-database-file.md).
 
 ## See also
 
-[LINK Input Files](link-input-files.md)<br/>
-[MSVC Linker Options](linker-options.md)
+[LINK input files](link-input-files.md)\
+[MSVC linker options](linker-options.md)
@@ -0,0 +1,41 @@
+---
+title: "/ILK (Name incremental database file)"
+description: "The MSVC linker option /ILK specifies the incremental link database file pathname."
+ms.date: 09/07/2022
+f1_keywords: ["VC.Project.VCLinkerTool.IncrementalLinkDatabaseFile", "/ilk", "ilk"]
+helpviewer_keywords: ["Name incremental database file in C++ linker", "/ILK linker option", "-ILK linker option", "ILK linker option"]
+---
+# `/ILK` (Name incremental database file)
+
+The **`/ILK`** linker option tells the linker where to put the *`.ilk`* database file for incremental link information ([`/INCREMENTAL`](./incremental-link-incrementally.md)).
+
+## Syntax
+
+> **`/ILK:`**\[*`pathname`*]
+
+### Arguments
+
+*`pathname`*\
+The destination directory and filename for the generated *`.ilk`* file. If the **`/ILK`** option isn't specified when **`/INCREMENTAL`** is used, the filename is created by appending *`.ilk`* to the target base filename.
+
+## Remarks
+
+The **`/ILK`** linker option tells the linker the path and filename to use for the *`.ilk`* incremental database file when you specify [`/INCREMENTAL`](./incremental-link-incrementally.md).
+
+### To set this compiler option in the Visual Studio development environment
+
+1. Open the project **Property Pages** dialog box. For more information, see [Set compiler and build properties](../working-with-project-properties.md).
+
+1. Select the **Configuration Properties** > **Linker** > **General** property page.
+
+1. Modify the **Incremental Link Database File** property. The default value is `$(IntDir)$(TargetName).ilk`.
+
+### To set this compiler option programmatically
+
+- See <xref:Microsoft.VisualStudio.VCProjectEngine.VCLinkerTool.AdditionalOptions%2A>.
+
+## See also
+
+[`/INCREMENTAL`](./incremental-link-incrementally.md)\
+[MSVC linker reference](linking.md)\
+[MSVC linker options](linker-options.md)
@@ -1,24 +1,26 @@
 ---
-description: "Learn more about: /INCREMENTAL (Link Incrementally)"
-title: "/INCREMENTAL (Link Incrementally)"
-ms.date: "11/04/2016"
+description: "Learn more about: /INCREMENTAL (Link incrementally)"
+title: "/INCREMENTAL (Link incrementally)"
+ms.date: 09/07/2022
 f1_keywords: ["/incremental", "VC.Project.VCLinkerTool.LinkIncremental"]
 helpviewer_keywords: ["/INCREMENTAL linker option", "-INCREMENTAL linker option", "INCREMENTAL linker option", "link incrementally option", "LINK tool [C++], options for full linking", "incremental linking"]
 ms.assetid: 135656ff-94fa-4ad4-a613-22e1a2a5d16b
 ---
-# /INCREMENTAL (Link Incrementally)
+# `/INCREMENTAL` (Link incrementally)
 
-```
-/INCREMENTAL[:NO]
-```
+Specifies whether to link incrementally or always perform a full link.
+
+## Syntax
+
+> **`/INCREMENTAL`**\[**`:NO`**]
 
 ## Remarks
 
-Controls how the linker handles incremental linking.
+The **`/INCREMENTAL`** linker option controls how the linker handles incremental linking.
 
-By default, the linker runs in incremental mode. To override a default incremental link, specify /INCREMENTAL:NO.
+By default, the linker runs in incremental mode. To override a default incremental link, specify **`/INCREMENTAL:NO`**.
 
-An incrementally linked program is functionally equivalent to a program that is non-incrementally linked. However, because it is prepared for subsequent incremental links, an incrementally linked executable, static library, or dynamic-link library file:
+An incrementally linked program is functionally equivalent to a program that is non-incrementally linked. However, because it's prepared for subsequent incremental links, an incrementally linked executable, static library, or dynamic-link library file:
 
 - Is larger than a non-incrementally linked program because of padding of code and data. Padding enables the linker to increase the size of functions and data without recreating the file.
 
@@ -27,35 +29,37 @@ An incrementally linked program is functionally equivalent to a program that is
    > [!NOTE]
    > To ensure that your final release build does not contain padding or thunks, link your program non-incrementally.
 
-To link incrementally regardless of the default, specify /INCREMENTAL. When this option is selected, the linker issues a warning if it cannot link incrementally, and then links the program non-incrementally. Certain options and situations override /INCREMENTAL.
+To link incrementally regardless of the default, specify **`/INCREMENTAL`**. When this option is selected, the linker issues a warning if it can't link incrementally, and then links the program non-incrementally. Certain options and situations override **`/INCREMENTAL`**.
 
 Most programs can be linked incrementally. However, some changes are too great, and some options are incompatible with incremental linking. LINK performs a full link if any of the following options are specified:
 
-- Link Incrementally is not selected (/INCREMENTAL:NO)
+- Link Incrementally isn't selected (**`/INCREMENTAL:NO`**)
 
-- /OPT:REF is selected
+- **`/OPT:REF`** is selected
 
-- /OPT:ICF is selected
+- **`/OPT:ICF`** is selected
 
-- /OPT:LBR is selected
+- **`/OPT:LBR`** is selected
 
-- /ORDER is selected
+- **`/ORDER`** is selected
 
-/INCREMENTAL is implied when [/DEBUG](debug-generate-debug-info.md) is specified.
+**`/INCREMENTAL`** is implied when [`/DEBUG`](debug-generate-debug-info.md) is specified.
 
 Additionally, LINK performs a full link if any of the following situations occur:
 
-- The incremental status (.ilk) file is missing. (LINK creates a new .ilk file in preparation for subsequent incremental linking.)
+- The incremental status (*`.ilk`*) file is missing. (LINK creates a new *`.ilk`* file in preparation for subsequent incremental linking.)
 
-- There is no write permission for the .ilk file. (LINK ignores the .ilk file and links non-incrementally.)
+- There's no write permission for the *`.ilk`* file. (LINK ignores the *`.ilk`* file and links non-incrementally.)
 
-- The .exe or .dll output file is missing.
+- The *`.exe`* or *`.dll`* output file is missing.
 
-- The timestamp of the .ilk, .exe, or .dll is changed.
+- The timestamp of the *`.ilk`*, *`.exe`*, or *`.dll`* is changed.
 
 - A LINK option is changed. Most LINK options, when changed between builds, cause a full link.
 
-- An object (.obj) file is added or omitted.
+- An object (*`.obj`*) file is added or omitted.
+
+An incremental link creates or updates an incremental link database *`.ilk`* file. You can specify the name and location of this file by using the [`/ILK` (Name incremental database file)](./ilk-name-incremental-database-file.md) linker option. For more information about the *`.ilk`* file, see [`.ilk` files as linker input](./dot-ilk-files-as-linker-input.md).
 
 ### To set this linker option in the Visual Studio development environment
 
@@ -71,5 +75,6 @@ Additionally, LINK performs a full link if any of the following situations occur
 
 ## See also
 
-[MSVC linker reference](linking.md)<br/>
-[MSVC Linker Options](linker-options.md)
+[MSVC linker reference](linking.md)\
+[MSVC linker options](linker-options.md)\
+[`.ilk` files as linker input](./dot-ilk-files-as-linker-input.md)
@@ -1,42 +1,42 @@
 ---
 description: "Learn more about: LINK Input Files"
 title: "LINK Input Files"
-ms.date: "11/04/2016"
+ms.date: 09/01/2022
 helpviewer_keywords: ["files [C++], LINK", "module definition files", "resources [C++], linker files", "LINK tool [C++], input files", "module definition files, linker files", "input files [C++], LINK", "linker [C++], input files", "import libraries [C++], linker files", "command input to linker files [C++]"]
 ms.assetid: bb26fcc5-509a-4620-bc3e-b6c6e603a412
 ---
-# LINK Input Files
+# LINK input files
 
-You provide the linker with files that contain objects, import and standard libraries, resources, module definitions, and command input. LINK does not use file extensions to make assumptions about the contents of a file. Instead, LINK examines each input file to determine what kind of file it is.
+You provide the linker with files that contain objects, import and standard libraries, resources, module definitions, and command input. LINK doesn't use file extensions to make assumptions about the contents of a file. Instead, LINK examines each input file to determine what kind of file it is.
 
-Object files on the command line are processed in the order they appear on the command line. Libraries are searched in command line order as well, with the following caveat: Symbols that are unresolved when bringing in an object file from a library are searched for in that library first, and then the following libraries from the command line and [/DEFAULTLIB (Specify Default Library)](defaultlib-specify-default-library.md) directives, and then to any libraries at the beginning of the command line.
+Object files on the command line are processed in the order they appear on the command line. Libraries are searched in command line order as well, with the following caveat: Symbols that are unresolved when bringing in an object file from a library are searched for in that library first, and then the following libraries from the command line and [`/DEFAULTLIB` (Specify default library)](defaultlib-specify-default-library.md) directives, and then to any libraries at the beginning of the command line.
 
 > [!NOTE]
-> LINK no longer accepts a semicolon (or any other character) as the start of a comment in response files and order files. Semicolons are recognized only as the start of comments in module-definition files (.def).
+> LINK no longer accepts a semicolon (or any other character) as the start of a comment in response files and order files. Semicolons are recognized only as the start of comments in module-definition files (`.def`).
 
 LINK uses the following types of input files:
 
-- [.obj files](dot-obj-files-as-linker-input.md)
+- [`.obj` files](dot-obj-files-as-linker-input.md)
 
-- [.netmodule files](netmodule-files-as-linker-input.md)
+- [`.netmodule` files](netmodule-files-as-linker-input.md)
 
-- [.lib files](dot-lib-files-as-linker-input.md)
+- [`.lib` files](dot-lib-files-as-linker-input.md)
 
-- [.exp files](dot-exp-files-as-linker-input.md)
+- [`.exp` files](dot-exp-files-as-linker-input.md)
 
-- [.def files](dot-def-files-as-linker-input.md)
+- [`.def` files](dot-def-files-as-linker-input.md)
 
-- [.pdb files](dot-pdb-files-as-linker-input.md)
+- [`.pdb` files](dot-pdb-files-as-linker-input.md)
 
-- [.res files](dot-res-files-as-linker-input.md)
+- [`.res` files](dot-res-files-as-linker-input.md)
 
-- [.exe files](dot-exe-files-as-linker-input.md)
+- [`.exe` files](dot-exe-files-as-linker-input.md)
 
-- [.txt files](dot-txt-files-as-linker-input.md)
+- [`.txt` files](dot-txt-files-as-linker-input.md)
 
-- [.ilk files](dot-ilk-files-as-linker-input.md)
+- [`.ilk` files](dot-ilk-files-as-linker-input.md)
 
 ## See also
 
-[MSVC linker reference](linking.md)<br/>
-[MSVC Linker Options](linker-options.md)
+[MSVC linker reference](linking.md)\
+[MSVC linker options](linker-options.md)
@@ -965,14 +965,16 @@ items:
               href: ../build/reference/ignore-ignore-specific-warnings.md
             - name: /IGNOREIDL (Don't process attributes into MIDL)
               href: ../build/reference/ignoreidl-don-t-process-attributes-into-midl.md
-            - name: /INFERASANLIBS (Use inferred sanitizer libs)
-              href: ../build/reference/inferasanlibs.md
+            - name: /ILK (Name incremental database file)
+              href: ../build/reference/ilk-name-incremental-database-file.md
             - name: /IMPLIB (Name import library)
               href: ../build/reference/implib-name-import-library.md
             - name: /INCLUDE (Force symbol references)
               href: ../build/reference/include-force-symbol-references.md
             - name: /INCREMENTAL (Link incrementally)
               href: ../build/reference/incremental-link-incrementally.md
+            - name: /INFERASANLIBS (Use inferred sanitizer libs)
+              href: ../build/reference/inferasanlibs.md
             - name: /INTEGRITYCHECK (Require signature check)
               href: ../build/reference/integritycheck-require-signature-check.md
             - name: /KEYCONTAINER (Specify a key container to sign an assembly)
 
@@ -42,8 +42,9 @@ int main()
     // Member initialization (in order of declaration):
     TempData td{ 45978, time(&time_to_set), 28.9, 37.0, 16.7 };
 
-    // Default initialization = {0,0,0,0,0}
-    TempData td_default{};
+    // When there's no constructor, an empty brace initializer does
+    // value initialization = {0,0,0,0,0}
+    TempData td_emptyInit{};
 
     // Uninitialized = if used, emits warning C4700 uninitialized local variable
     TempData td_noInit;
@@ -55,7 +56,7 @@ int main()
 }
 ```
 
-When a `class` or `struct` has no constructor, you provide the list elements in the order that the members are declared in the `class`. If the `class` has a constructor, provide the elements in the order of the parameters. If a type has a default constructor, either implicitly or explicitly declared, you can use default brace initialization (with empty braces). For example, the following `class` may be initialized by using both default and non-default brace initialization:
+When a `class` or `struct` has no constructor, you provide the list elements in the order that the members are declared in the `class`. If the `class` has a constructor, provide the elements in the order of the parameters. If a type has a default constructor, either implicitly or explicitly declared, you can use brace initialization with empty braces to invoke it. For example, the following `class` may be initialized by using both empty and non-empty brace initialization:
 
 ```cpp
 #include <string>
@@ -106,7 +107,7 @@ int main()
 }
 ```
 
-If the default constructor is explicitly declared but marked as deleted, default brace initialization can't be used:
+If the default constructor is explicitly declared but marked as deleted, empty brace initialization can't be used:
 
 ```cpp
 class class_f {