specify MAX_PATH limitation

Author: TylerMSFT

docs/build/reference/base-base-address.md

@@ -1,10 +1,9 @@
 ---
 description: "Learn more about: /BASE (Base address)"
 title: "/BASE (Base address)"
-ms.date: 05/11/2022
+ms.date: 03/24/2025
 f1_keywords: ["/base", "VC.Project.VCLinkerTool.BaseAddress"]
 helpviewer_keywords: ["base addresses [C++]", "programs [C++], preventing relocation", "semicolon [C++], specifier", "-BASE linker option", "key address size", "environment variables [C++], LIB", "programs [C++], base address", "LIB environment variable", "BASE linker option", "DLLs [C++], linking", "/BASE linker option", "@ symbol for base address", "executable files [C++], base address", "at sign symbol for base address"]
-ms.assetid: 00b9f6fe-0bd2-4772-a69c-7365eb199069
 ---
 # `/BASE` (Base address)
 
@@ -23,7 +22,7 @@ The **`/BASE`** linker option sets a base address for the program. It overrides
 
 The linker issues an error if *`address`* isn't a multiple of 64K. You can optionally specify the size of the program. The linker issues a warning if the program can't fit in the size you specified.
 
-On the command line, another way to specify the base address is by using a *base address response file*. A base address response file is a text file that contains the base addresses and optional sizes of all the DLLs your program uses, and a unique text key for each base address. To specify a base address by using a response file, use an at sign (**`@`**) followed by the name of the response file, *`filename`*, followed by a comma, then the *`key`* value for the base address to use in the file. The linker looks for *`filename`* in either the specified path, or if no path is specified, in the directories specified in the `LIB` environment variable. Each line in *`filename`* represents one DLL and has the following syntax:
+On the command line, another way to specify the base address is by using a *base address response file*. A base address response file is a text file that contains the base addresses and optional sizes of all the DLLs your program uses, and a unique text key for each base address. To specify a base address by using a response file, use an at sign (**`@`**) followed by the name of the response file, *`filename`*, followed by a comma, then the *`key`* value for the base address to use in the file. The linker looks for *`filename`* in either the specified path, or if no path is specified, in the directories specified in the `LIB` environment variable. The *`filename`* can't contain more than `MAX_PATH` (260) characters. Each line in *`filename`* represents one DLL and has the following syntax:
 
 > *`key`* *`address`* \[*`size`*] **`;`** *`comment`*
 
@@ -46,9 +45,7 @@ Another way to set the base address is by using the *`BASE`* argument in a [`NAM
 ### To set this linker option in the Visual Studio development environment
 
 1. Open the project's **Property Pages** dialog box. For details, see [Set C++ compiler and build properties in Visual Studio](../working-with-project-properties.md).
-
 1. Select the **Configuration Properties** > **Linker** > **Advanced** property page.
-
 1. Modify the **Base Address** property.
 
 ### To set this linker option programmatically

docs/build/reference/idlout-name-midl-output-files.md

@@ -4,41 +4,37 @@ title: "/IDLOUT (Name MIDL Output Files)"
 ms.date: "11/04/2016"
 f1_keywords: ["/idlout", "VC.Project.VCLinkerTool.MergedIDLBaseFileName"]
 helpviewer_keywords: ["MIDL, output file names", ".idl files, path", "MIDL", "/IDLOUT linker option", "IDL files, path", "-IDLOUT linker option", "IDLOUT linker option"]
-ms.assetid: 10d00a6a-85b4-4de1-8732-e422c6931509
 ---
 # /IDLOUT (Name MIDL Output Files)
 
-```
+```cmd
 /IDLOUT:[path\]filename
 ```
 
 ## Parameters
 
-*path*<br/>
+*`path`*\
 An absolute or relative path specification. By specifying a path, you affect only the location of an .idl file; all other files are placed in the project directory.
 
-*filename*<br/>
-Specifies the name of the .idl file created by the MIDL compiler. No file extension is assumed; specify *filename*.idl if you want an .idl extension.
+*`filename`*\
+Specifies the name of the .idl file created by the MIDL compiler. No file extension is assumed; specify *filename*.idl if you want an .idl extension. The path and filename must not exceed `MAX_PATH` (260) characters.
 
 ## Remarks
 
-The /IDLOUT option specifies the name and extension of the .idl file.
+The `/IDLOUT` option specifies the name and extension of the .idl file.
 
-The MIDL compiler is called by the MSVC linker when linking projects that have the [module](../../windows/attributes/module-cpp.md) attribute.
+The MIDL compiler is called by the MSVC linker when linking projects that have the [`module`](../../windows/attributes/module-cpp.md) attribute.
 
-/IDLOUT also specifies the file names of the other output files associated with the MIDL compiler:
+`/IDLOUT` also specifies the file names of the other output files associated with the MIDL compiler:
 
 - *filename*.tlb
-
 - *filename*_p.c
-
 - *filename*_i.c
-
 - *filename*.h
 
-*filename* is the parameter that you pass to /IDLOUT. If [/TLBOUT](tlbout-name-dot-tlb-file.md) is specified, the .tlb file will get its name from /TLBOUT *filename*.
+*`filename`* is the parameter that you pass to `/IDLOUT`. If [`/TLBOUT`](tlbout-name-dot-tlb-file.md) is specified, the .tlb file will get its name from `/TLBOUT` *`filename`*.
 
-If you specify neither /IDLOUT nor /TLBOUT, the linker will create vc70.tlb, vc70.idl, vc70_p.c, vc70_i.c, and vc70.h.
+If you specify neither `/IDLOUT` nor `/TLBOUT`, the linker will create vc70.tlb, vc70.idl, vc70_p.c, vc70_i.c, and vc70.h.
 
 ### To set this linker option in the Visual Studio development environment
 
@@ -54,8 +50,8 @@ If you specify neither /IDLOUT nor /TLBOUT, the linker will create vc70.tlb, vc7
 
 ## See also
 
-[MSVC linker reference](linking.md)<br/>
-[MSVC Linker Options](linker-options.md)<br/>
-[/IGNOREIDL (Don't Process Attributes into MIDL)](ignoreidl-don-t-process-attributes-into-midl.md)<br/>
-[/MIDL (Specify MIDL Command Line Options)](midl-specify-midl-command-line-options.md)<br/>
+[MSVC linker reference](linking.md)\
+[MSVC Linker Options](linker-options.md)\
+[/IGNOREIDL (Don't Process Attributes into MIDL)](ignoreidl-don-t-process-attributes-into-midl.md)\
+[/MIDL (Specify MIDL Command Line Options)](midl-specify-midl-command-line-options.md)\
 [Building an Attributed Program](../../windows/attributes/cpp-attributes-com-net.md)

docs/build/reference/ilk-name-incremental-database-file.md

@@ -16,7 +16,7 @@ The **`/ILK`** linker option tells the linker where to put the *`.ilk`* database
 ### 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.
+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. The *`pathname`* must not exceed `MAX_PATH` (260) characters.
 
 ## Remarks
 

docs/build/reference/libpath-additional-libpath.md

@@ -1,25 +1,24 @@
 ---
 description: "Learn more about: /LIBPATH (Additional Libpath)"
 title: "/LIBPATH (Additional Libpath)"
-ms.date: "11/04/2016"
+ms.date: 03/24/2025
 f1_keywords: ["/libpath", "VC.Project.VCLinkerTool.AdditionalLibraryDirectories"]
 helpviewer_keywords: ["LIBPATH linker option", "/LIBPATH linker option", "Additional Libpath linker option", "environment library path override", "-LIBPATH linker option", "library path linker option"]
-ms.assetid: 7240af0b-9a3d-4d53-8169-2a92cd6958ba
 ---
-# /LIBPATH (Additional Libpath)
+# `/LIBPATH` (Additional Libpath)
 
-```
+```cmd
 /LIBPATH:dir
 ```
 
 ## Parameters
 
-*dir*<br/>
-Specifies a path that the linker will search before it searches the path specified in the LIB environment option.
+*`dir`*\
+Specifies a path that the linker will search before it searches the path specified in the LIB environment option. Must not exceed `MAX_PATH` (260) characters.
 
 ## Remarks
 
-Use the /LIBPATH option to override the environment library path. The linker will first search in the path specified by this option, and then search in the path specified in the LIB environment variable. You can specify only one directory for each /LIBPATH option you enter. If you want to specify more than one directory, you must specify multiple /LIBPATH options. The linker will then search the specified directories in order.
+Use the `/LIBPATH` option to override the environment library path. The linker will first search in the path specified by this option, and then search in the path specified in the LIB environment variable. You can specify only one directory for each `/LIBPATH` option you enter. If you want to specify more than one directory, you must specify multiple `/LIBPATH` options. The linker will then search the specified directories in order.
 
 ### To set this linker option in the Visual Studio development environment
 
@@ -35,5 +34,5 @@ Use the /LIBPATH option to override the environment library path. The linker wil
 
 ## See also
 
-[MSVC linker reference](linking.md)<br/>
+[MSVC linker reference](linking.md)\
 [MSVC Linker Options](linker-options.md)

docs/build/reference/link-repro-full-path-rsp.md

@@ -17,7 +17,7 @@ This flag was introduced in Visual Studio 2022 version 17.11.
 
 ## Remarks
 
-Rather than generating a full link repro like `/LINKREPRO` which copies all the files to a directory and creating a response file with relative paths to that directory, this option writes the names of the files used during linking to the specified file.
+The *`filename`* argument specifies the name of the response file to create. The linker will write the fully qualified paths of all input files to this file. The file will be created in the current working directory unless a full path is specified. The *`filename`* must not exceed `MAX_PATH` (260) characters.
 
 For example, given:
 - a directory `c:\temp\test` that contains the files `test.cpp`, `f1.cpp`, `f2.cpp`

docs/build/reference/linking.md

@@ -1,7 +1,7 @@
 ---
 description: "Learn more about: Linking"
 title: "MSVC linker reference"
-ms.date: "12/10/2018"
+ms.date: 03/24/2025
 ---
 # Linking
 
@@ -36,7 +36,7 @@ The `arguments` include options and filenames and can be specified in any order.
 
 On the command line, an option consists of an option specifier, either a dash (`-`) or a forward slash (`/`), followed by the name of the option. Option names can't be abbreviated. Some options take an argument, specified after a colon (`:`). No spaces or tabs are allowed within an option specification, except within a quoted string in the `/COMMENT` option. Specify numeric arguments in decimal or C-language notation. Option names and their keyword or filename arguments aren't case sensitive, but identifiers as arguments are case sensitive.
 
-To pass a file to the linker, specify the filename on the command line after the `link.exe` command. You can specify an absolute or relative path with the filename, and you can use wildcards in the filename. If you omit the dot (`.`) and filename extension, the linker assumes an extension of `.obj` to find the file. The linker doesn't use filename extensions or the lack of them to make assumptions about the contents of files. It determines the type of file by examining it, and processes it accordingly.
+To pass a file to the linker, specify the filename on the command line after the `link.exe` command. You can specify an absolute or relative path with the filename, and you can use wildcards in the filename. The filename must not contain more than `MAX_PATH` (260) characters. If you omit the dot (`.`) and filename extension, the linker assumes an extension of `.obj` to find the file. The linker doesn't use filename extensions or the lack of them to make assumptions about the contents of files. It determines the type of file by examining it, and processes it accordingly.
 
 The linker returns zero for success (no errors). Otherwise, it returns the error number that stopped the link. For example, if the linker generates `LNK1104`, the linker returns 1104. Accordingly, the lowest error number returned on an error by the linker is 1000. A return value of 128 represents a configuration problem with either the operating system or a .config file; the loader didn't load either `link.exe` or `c2.dll`.
 
@@ -46,7 +46,7 @@ You can pass command-line arguments to `link.exe` in the form of a command file.
 
 > `link @commandfile`
 
-The *`commandfile`* is the name of a text file. No space or tab is allowed between the at sign (**\@**) and the filename. There's no default extension; you must specify the full filename, including any extension. Wildcards can't be used. You can specify an absolute or relative path with the filename. The linker doesn't use an environment variable to search for the file.
+The *`commandfile`* is the name of a text file. No space or tab is allowed between the at sign (**\@**) and the filename. There's no default extension; you must specify the full filename, including any extension. Wildcards can't be used. You can specify an absolute or relative path with the filename. Must not contain more than `MAX_PATH` (260) characters. The linker doesn't use an environment variable to search for the file.
 
 In the command file, arguments are separated by spaces or tabs (as on the command line) and by newline characters.
 

docs/build/reference/linkrepro.md

@@ -1,7 +1,7 @@
 ---
 title: "/LINKREPRO (Link repro directory name)"
 description: Linker or library tool option to set the directory for a link repro.
-ms.date: "09/24/2019"
+ms.date: 03/24/2025
 f1_keywords: ["/LINKREPRO"]
 helpviewer_keywords: ["LINKREPRO linker option", "/LINKREPRO linker option", "-LINKREPRO linker option", "linker repro reporting"]
 ---
@@ -16,7 +16,7 @@ Tells the linker or library tool to generate a link repro in a specified directo
 ### Arguments
 
 **/LINKREPRO:**_directory-name_\
-The user-specified directory to store the link repro in. Directory names that include spaces must be enclosed in double quotes.
+The user-specified directory to store the link repro in. Directory names that include spaces must be enclosed in double quotes. The *`_directory-name_`* must not exceed `MAX_PATH` (260) characters.
 
 ## Remarks
 

docs/build/reference/manifestinput-specify-manifest-input.md

@@ -3,7 +3,6 @@ description: "Learn more about: /MANIFESTINPUT (Specify Manifest Input)"
 title: "/MANIFESTINPUT (Specify Manifest Input)"
 ms.date: 09/09/2022
 f1_keywords: ["VC.Project.VCLinkerTool.ManifestInput"]
-ms.assetid: a0b0c21e-1f9b-4d8c-bb3f-178f57fa7f1b
 ---
 # /MANIFESTINPUT (Specify Manifest Input)
 
@@ -16,7 +15,7 @@ Specifies a manifest input file to include in the manifest that's embedded in th
 ### Parameters
 
 *`filename`*\
-The manifest file to include in the embedded manifest.
+The manifest file to include in the embedded manifest. Must not exceed `MAX_PATH` (260) characters.
 
 ## Remarks
 
@@ -26,5 +25,5 @@ This option can't be set directly in Visual Studio. Instead, use the **Additiona
 
 ## See also
 
-[MSVC linker reference](linking.md)<br/>
+[MSVC linker reference](linking.md)\
 [MSVC Linker Options](linker-options.md)

docs/build/reference/natvis-add-natvis-to-pdb.md

@@ -1,10 +1,9 @@
 ---
 description: "Learn more about: /NATVIS (Add Natvis to PDB)"
 title: "/NATVIS (Add Natvis to PDB)"
-ms.date: 09/08/2022
+ms.date: 03/24/2025
 f1_keywords: ["/natvis", "natvis"]
 helpviewer_keywords: ["NATVIS linker option", "/NATVIS linker option", "-NATVIS linker option", "Add Natvis file to PDB"]
-ms.assetid: 8747fc0c-701a-4796-bb4d-818ab4465cca
 ---
 # `/NATVIS` (Add Natvis to PDB)
 
@@ -17,7 +16,7 @@ Specifies a debugger visualization file (a Natvis file) to embed in the PDB file
 ## Parameters
 
 *`filename`*\
-The pathname for a Natvis file to add to the PDB file. It embeds the debugger visualizations in the Natvis file into the PDB.
+The pathname for a Natvis file to add to the PDB file. It embeds the debugger visualizations in the Natvis file into the PDB. The *`filename`* must not exceed `MAX_PATH` (260) characters.
 
 ## Remarks
 

docs/build/reference/pdbaltpath-use-alternate-pdb-path.md

@@ -1,29 +1,28 @@
 ---
 description: "Learn more about: /PDBALTPATH (Use Alternate PDB Path)"
 title: "/PDBALTPATH (Use Alternate PDB Path)"
-ms.date: "11/04/2016"
+ms.date: 03/24/2025
 f1_keywords: ["/pdbaltpath"]
 helpviewer_keywords: [".pdb files, path", "PDBALTPATH dumpbin option", "-PDBALTPATH dumpbin option", "/PDBALTPATH dumpbin option", "PDB files, path"]
-ms.assetid: 72e200aa-e2c3-4ad8-b687-25528da1aaaf
 ---
 # /PDBALTPATH (Use Alternate PDB Path)
 
-```
+```cmd
 /PDBALTPATH:pdb_file_name
 ```
 
 ## Arguments
 
-*pdb_file_name*<br/>
-The path and file name for the .pdb file.
+*pdb_file_name*\
+The path and file name for the `.pdb` file. The *`pdb_file_name`* must not exceed `MAX_PATH` (260) characters.
 
 ## Remarks
 
-Use this option to provide an alternate location for the Program Database (.pdb) file in a compiled binary file. Normally, the linker records the location of the .pdb file in the binaries that it produces. You can use this option to provide a different path and file name for the .pdb file. The information provided with /PDBALTPATH does not change the location or name of the actual .pdb file; it changes the information that the linker writes in the binary file. This enables you to provide a path that is independent of the file structure of the build computer. Two common uses for this option are to provide a network path or a file that has no path information.
+Use this option to provide an alternate location for the Program Database (`.pdb`) file in a compiled binary file. Normally, the linker records the location of the `.pdb` file in the binaries that it produces. You can use this option to provide a different path and file name for the `.pdb` file. The information provided with `/PDBALTPATH` does not change the location or name of the actual `.pdb` file; it changes the information that the linker writes in the binary file. This enables you to provide a path that is independent of the file structure of the build computer. Two common uses for this option are to provide a network path or a file that has no path information.
 
-The value of *pdb_file_name* can be an arbitrary string, an environment variable, or **%_PDB%**. The linker will expand an environment variable, such as **%SystemRoot%**, to its value. The linker defines the environment variables **%_PDB%** and **%_EXT%**. **%_PDB%** expands to the file name of the actual .pdb file without any path information and **%_EXT%** is the extension of the generated executable.
+The value of *pdb_file_name* can be an arbitrary string, an environment variable, or **%_PDB%**. The linker will expand an environment variable, such as **%SystemRoot%**, to its value. The linker defines the environment variables **%_PDB%** and **%_EXT%**. **%_PDB%** expands to the file name of the actual `.pdb` file without any path information and **%_EXT%** is the extension of the generated executable.
 
 ## See also
 
-[DUMPBIN Options](dumpbin-options.md)<br/>
+[DUMPBIN Options](dumpbin-options.md)\
 [/PDBPATH](pdbpath.md)