Merge branch 'main' of https://github.com/MicrosoftDocs/cpp-docs-pr into arm

Author: TylerMSFT

docs/build/creating-and-managing-visual-cpp-projects.md

@@ -1,49 +1,53 @@
 ---
-description: "Learn more about: creating and configuring Visual Studio C++ projects"
-title: "Visual Studio Projects - C++"
-ms.date: 10/4/2023
+title: "Create and Configure Visual Studio C++ Projects"
+description: "Learn how to create a Visual Studio C++ project, and then add code and build your project."
+ms.date: 03/24/2025
+ms.topic: concept-article
 helpviewer_keywords: ["Visual Studio C++ projects, creating", "projects [C++], creating", "Visual Studio C++ projects"]
 ---
-# Visual Studio projects - C++
+# Visual Studio C++ projects
 
-A *Visual Studio project* is a collection of code files and assets such as icons, images, and so on, that are built together using the MSBuild build system. MSBuild is the native build system for Visual Studio and is generally the best build system to use for Windows-specific programs. MSBuild is tightly integrated with Visual Studio, but you can also use it from the command line.
+A *Visual Studio project* is a collection of code files and assets such as icons, images, and so on, that are built together using the MSBuild system. MSBuild is the native build system for Visual Studio and is generally the best build system to use for Windows-specific programs. MSBuild is tightly integrated with Visual Studio, but you can also use it from the command line.
 
-For information about upgrading MSBuild projects from older versions of Visual Studio, see the [Microsoft C++ Porting and Upgrading Guide](../porting/visual-cpp-porting-and-upgrading-guide.md).
+For information about upgrading MSBuild projects from older versions of Visual Studio, see the [Microsoft C++ porting and upgrading guide](../porting/visual-cpp-porting-and-upgrading-guide.md).
 
-For cross-platform projects, or projects that use open-source libraries, we recommend using [CMake projects in Visual Studio](cmake-projects-in-visual-studio.md) in Visual Studio 2017 and later.
+For cross-platform projects, or projects that use open-source libraries, we recommend using [CMake projects in Visual Studio](cmake-projects-in-visual-studio.md).
 
 ## Create a Visual Studio C++ project
 
 ::: moniker range=">=msvc-160"
 
 1. Create a C++ project by choosing **File** > **New** > **Project**.
+
 1. In the **Create a new project** dialog, set the **Language** dropdown to **C++**. This filters the list of project templates to C++ projects. You can filter the templates by setting the **Platform**, **Project Type**, or by entering keywords in the search box.
 
-   ![Screenshot of the Create a new project wizard. The Console App project template is selected.](../build/media/vs2019-choose-console-app.png)
+    :::image type="content" source="../build/media/vs2019-choose-console-app.png" alt-text="Screenshot of the Create a new project wizard. The Console App project template is selected.":::
 
 1. Select a project template, then choose **Next**.
+
 1. On the **Configure your new project page**, enter project-specific settings such as the project name or location and then choose **Create** to create your project.
 
 ::: moniker-end
 
 ::: moniker range="msvc-150"
 
 1. Create a C++ project by choosing **File** > **New** > **Project**.
+
 1. Choose **Visual C++** in the left pane. In the center pane, a list of project templates appears:
 
-   ![Screenshot of the New Project dialog, showing available project templates for C++ such as Windows Console Application.](../overview/media/vs2017-new-project.png "Visual Studio 2017 New Project Dialog")
+    :::image type="content" source="../overview/media/vs2017-new-project.png" alt-text="Screenshot of the New Project dialog, showing available project templates for C++ such as Windows Console Application.":::
 
 ::: moniker-end
 
 For more information about the default project templates included in Visual Studio, see [C++ project templates in Visual Studio](reference/visual-cpp-project-types.md).
 
-You can create your own project templates. For more information, see [How to: Create project templates](/visualstudio/ide/how-to-create-project-templates).
+You can create your own project templates. For more information, see [Create project templates](/visualstudio/ide/how-to-create-project-templates).
 
 After you create a project, it appears in the [Solution Explorer](/visualstudio/ide/solutions-and-projects-in-visual-studio) window:
 
-   ![Screenshot of the Solution Explorer window, showing source files, header files, and resource files.](media/mathlibrary-solution-explorer-153.png)
+:::image type="content" source="media/mathlibrary-solution-explorer-153.png" alt-text="Screenshot of the Solution Explorer window, showing source files, header files, and resource files.":::
 
-When you create a new project, a solution file (.sln) is also created. A *Visual Studio solution* is a collection of one or more projects. You can add another project to the solution by right-clicking the solution name in **Solution Explorer** > **Add** > **New project**.
+When you create a new project, a solution file (*`.sln`*) is also created. A *Visual Studio solution* is a collection of one or more projects. You can add another project to the solution by right-clicking the solution name in **Solution Explorer** > **Add** > **New project**.
 
 The solution file coordinates build dependencies when you have multiple related projects. Compiler options are set at the project level.
 
@@ -61,28 +65,28 @@ For more information about consuming a library that you have downloaded by using
 - [vcpkg in MSBuild projects](/vcpkg/users/buildsystems/msbuild-integration)
 - [Tutorial: Install and use packages with MSBuild in Visual Studio](/vcpkg/get_started/get-started-msbuild)
 
-They're also commercial third-party libraries that you can install. Follow their installation instructions.
+There are also commercial third-party libraries that you can install. Follow their installation instructions.
 
 ## Set compiler options and build properties
 
-To configure build settings for a project, right-click on the project in **Solution Explorer** and choose **Properties**. For more information, see [Set C++ compiler and build properties in Visual Studio](working-with-project-properties.md).
+To configure build settings for a project, right-click on the project in **Solution Explorer** and choose **Properties**. For more information, see [Set compiler and build properties](working-with-project-properties.md).
 
 ## Compile and run a project
 
-To compile and run the new project, press **F5** or click the *debug dropdown* with the green arrow on the main toolbar. The *configuration dropdown* is where you choose whether to perform a *Debug* or *Release* build (or some other custom configuration).
+To compile and run the new project, press **F5** or select the *debug dropdown* with the green arrow on the main toolbar. The *configuration dropdown* is where you choose whether to perform a *Debug* or *Release* build (or some other custom configuration).
 
 A new project compiles without errors. When adding your own code, you might occasionally introduce an error or trigger a warning. An error prevents the build from completing; a warning doesn't. All errors and warnings appear both in the Output Window and in the Error List when you build the project.
 
-   ![Screenshot of the Output window and Error list, showing a syntax error for a misplaced colon.](../overview/media/vs2017-output-error-list.png)
+:::image type="content" source="../overview/media/vs2017-output-error-list.png" alt-text="Screenshot of the Output window and Error list, showing a syntax error for a misplaced colon.":::
 
 In the **Error List**, you can press **F1** on the highlighted error to go to its documentation topic.
 
-## See also
+## Related content
 
-[Create a project from existing code](how-to-create-a-cpp-project-from-existing-code.md)\
-[Set C++ compiler and build properties in Visual Studio](working-with-project-properties.md)\
-[Custom build steps and build events](understanding-custom-build-steps-and-build-events.md)\
-[Reference libraries and components at build time](adding-references-in-visual-cpp-projects.md)\
-[Organize project output files](how-to-organize-project-output-files-for-builds.md)\
-[Projects and build systems](projects-and-build-systems-cpp.md)\
-[Microsoft C++ porting and upgrade guide](../porting/visual-cpp-porting-and-upgrading-guide.md)
+- [Create a project from existing code](how-to-create-a-cpp-project-from-existing-code.md)
+- [Set C++ compiler and build properties in Visual Studio](working-with-project-properties.md)
+- [Custom build steps and build events](understanding-custom-build-steps-and-build-events.md)
+- [Reference libraries and components at build time](adding-references-in-visual-cpp-projects.md)
+- [Organize project output files](how-to-organize-project-output-files-for-builds.md)
+- [Projects and build systems](projects-and-build-systems-cpp.md)
+- [Microsoft C++ porting and upgrade guide](../porting/visual-cpp-porting-and-upgrading-guide.md)

docs/build/creating-precompiled-header-files.md

@@ -140,7 +140,7 @@ This table lists compiler options that might trigger an inconsistency warning wh
 
 | Option | Name | Rule |
 |--|--|--|
-| **`/D `**| Define constants and macros | Must be the same between the compilation that created the precompiled header and the current compilation. The state of defined constants isn't checked. However, unpredictable results can occur if your files depend on the values of the changed constants. |
+| **`/D`**| Define constants and macros | Must be the same between the compilation that created the precompiled header and the current compilation. The state of defined constants isn't checked. However, unpredictable results can occur if your files depend on the values of the changed constants. |
 | **`/E`** or **`/EP`** | Copy preprocessor output to standard output | Precompiled headers don't work with the **`/E`** or **`/EP`** option. |
 | **`/Fr`** or **`/FR`** | Generate Microsoft Source Browser information | For the **`/Fr`** and **`/FR`** options to be valid with the **`/Yu`** option, they must also have been in effect when the precompiled header was created. Subsequent compilations that use the precompiled header also generate Source Browser information. Browser information is placed in a single *`.sbr`* file and is referenced by other files in the same manner as CodeView information. You can't override the placement of Source Browser information. |
 | **`/GA`**, **`/GD`**, **`/GE`**, **`/Gw`**, or **`/GW`** | Windows protocol options | Must be the same between the compilation that created the precompiled header and the current compilation. The compiler emits a warning if these options differ. |
@@ -161,7 +161,6 @@ The code base of a software project is often contained in multiple C or C++ sour
 
 The figure uses three diagrammatic devices to show the flow of the build process. Named rectangles represent each file or macro; the three macros represent one or more files. Shaded areas represent each compile or link action. Arrows show which files and macros are combined during the compilation or linking process.
 
-![ The diagram is described in the text following the diagram.]()\
 Structure of a makefile that uses a precompiled header file:
 
 :::image type="complex" source="media/vc30ow1.gif" alt-text="Diagram showing example inputs and outputs of a makefile that uses a precompiled header file.":::

docs/build/media/visual-c---project-defaults.png

@@ -1,10 +1,9 @@
 ---
 description: "Learn more about: /BASE (Base address)"
 title: "/BASE (Base address)"
-ms.date: 05/11/2022
+ms.date: 03/27/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 fully qualified *`filename`* must not exceed `MAX_PATH` (260 characters). Each line in *`filename`* represents one DLL and has the following syntax:
 
 > *`key`* *`address`* \[*`size`*] **`;`** *`comment`*
 
@@ -35,7 +34,7 @@ one    0x28000000    0x00100000    ; for DLLONE.DLL
 two    0x28100000    0x00300000    ; for DLLTWO.DLL
 ```
 
-If the file that contains these lines is called DLLS.txt, the following example command applies this information:
+If the file that contains these lines is called `DLLS.txt`, the following example command applies this information:
 
 ```cmd
 link dlltwo.obj /dll /base:@dlls.txt,two
@@ -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/media/visual-c---property-pages-showing-active-configuration.png

@@ -1,10 +1,9 @@
 ---
 description: "Learn more about: /DEF (Specify module-definition file)"
 title: "/DEF (Specify module-definition file)"
-ms.date: 09/09/2022
+ms.date: 03/27/2025
 f1_keywords: ["VC.Project.VCLinkerTool.ModuleDefinitionFile", "/def"]
 helpviewer_keywords: ["module definition files, specifying", "DEF linker option", "-DEF linker option", "module definition files", "/DEF linker option"]
-ms.assetid: 6497fa68-65f0-48ca-8f66-b87166fc631a
 ---
 # `/DEF` (Specify module-definition file)
 
@@ -17,7 +16,7 @@ Specifies a module-definition file to the linker.
 ## Arguments
 
 *`filename`*\
-The name of a module-definition file (*`.def`*) to be passed to the linker.
+The name of a module-definition file (*`.def`*) to be passed to the linker. When expanded, the fully qualified filename must not exceed `MAX_PATH` (260 characters).
 
 ## Remarks
 
@@ -28,9 +27,7 @@ To specify a *`.def`* file from within the development environment, add it to th
 ### To set this linker option in the Visual Studio development environment
 
 1. Open the project's **Property Pages** dialog box. For more information, see [Set compiler and build properties](../working-with-project-properties.md).
-
 1. Select the **Configuration Properties** > **Linker** > **Input** property page.
-
 1. Modify the **Module Definition File** property. Choose **OK** or **Apply** to save your changes.
 
 ### To set this linker option programmatically

docs/build/media/visual-c---property-pages-showing-release-config.png

@@ -33,6 +33,9 @@ Builds the deoptimized output after building the optimized output instead of in
 
 This preview flag, available starting with Visual Studio 2022 Version 17.14 Preview 2, applies only to x64 projects.
 
+IncrediBuild 10.24 supports C++ Dynamic Debugging builds.\
+FastBuild v1.15 supports C++ Dynamic Debugging builds.
+
 ### 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).

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

@@ -1,7 +1,7 @@
 ---
 title: "/dynamicdeopt (Enable C++ Dynamic Debugging (Preview))"
 description: "Enable the Microsoft C++ compiler option /dynamicdeopt to use C++ Dynamic Debugging."
-ms.date: 03/20/2025
+ms.date: 04/01/2025
 f1_keywords: ["/dynamicdeopt"]
 helpviewer_keywords: ["-dynamicdeopt compiler option [C++]", "dynamicdeopt compiler option [C++]"]
 ---
@@ -41,6 +41,9 @@ Compiling with `/dynamicdeopt` generates other binaries that are used for debugg
 If you specify `/INCREMENTAL`, the compiler generates a warning and automatically turns off `/INCREMENTAL`.
 If you specify `/OPT:ICF`, the compiler generates a warning that the debug experience isn't as good. This is because ICF can cause functions to be removed from the alt file, which means you can't step into them.
 
+IncrediBuild 10.24 supports C++ Dynamic Debugging builds.\
+FastBuild v1.15 supports C++ Dynamic Debugging builds.
+
 `/dynamicdeopt` is incompatible with edit-and-continue and the following compiler switches:
 
 ```cpp

docs/build/reference/def-specify-module-definition-file.md

@@ -1,7 +1,7 @@
 ---
 title: "/GENPROFILE, /FASTGENPROFILE (Generate Profiling Instrumented Build)"
 description: "Learn more about: /GENPROFILE, /FASTGENPROFILE (Generate Profiling Instrumented Build)"
-ms.date: 04/14/2021
+ms.date: 03/27/2025
 f1_keywords: ["GENPROFILE", "FASTGENPROFILE", "/GENPROFILE", "/FASTGENPROFILE"]
 helpviewer_keywords: ["GENPROFILE", "FASTGENPROFILE"]
 ---
@@ -43,7 +43,7 @@ Use **`PATH`**  to specify a separate set of PGO counters for each unique path t
 Specifies whether to use extra counters to keep an accurate count when exceptions are thrown during training. Use **`TRACKEH`**  to specify extra counters for an exact count. Use **`NOTRACKEH`**  to specify single counters for code that doesn't use exception handling or that doesn't run into exceptions in your training scenarios.  When you specify **`/GENPROFILE`**, the default is **`TRACKEH`** . When you specify **`/FASTGENPROFILE`**, the default is **`NOTRACKEH`** .
 
 **`PGD`**=*filename*\
-Specifies a base file name for the *`.pgd`* file. By default, the linker uses the base executable image file name with a *`.pgd`* extension.
+Specifies a base filename for the *`.pgd`* file. By default, the linker uses the base executable image filename with a *`.pgd`* extension. When expanded, the fully qualified filename must not exceed `MAX_PATH` (260 characters).
 
 ## Remarks