Merge pull request #6229 from MicrosoftDocs/FromPublicMasterBranch

Confirm merge from FromPublicMasterBranch to main to sync with https://github.com/MicrosoftDocs/cpp-docs (branch main)

Author: Albertyang0

docs/build/projects-and-build-systems-cpp.md

@@ -1,57 +1,56 @@
 ---
 title: "C/C++ projects and build systems in Visual Studio"
 description: "Use Visual Studio to compile and build C++ projects for Windows, ARM, or Linux based on any project system."
-ms.date: "07/17/2019"
-helpviewer_keywords: ["builds [C++]", "C++ projects, building", "projects [C++], building", "builds [C++], options", "C++, build options"]
-ms.assetid: fa6ed4ff-334a-4d99-b5e2-a1f83d2b3008
+ms.date: 07/17/2019
 ms.topic: "overview"
 ms.custom: intro-overview
+helpviewer_keywords: ["builds [C++]", "C++ projects, building", "projects [C++], building", "builds [C++], options", "C++, build options"]
 ---
 # C/C++ projects and build systems in Visual Studio
 
 You can use Visual Studio to edit, compile, and build any C++ code base with full IntelliSense support without having to convert that code into a Visual Studio project or compile with the Microsoft C++ (MSVC) Build Tools. For example, you can edit a cross-platform CMake project in Visual Studio on a Windows machine, then compile it for Linux using g++ on a remote Linux machine.
 
 ## C++ compilation
 
-To *build* a C++ program means to compile source code from one or more files and then link those files into an executable file (.exe), a dynamic-load library (.dll) or a static library (.lib).
+To *build* a C++ program means to compile source code from one or more files and then link those files into an executable file (`.exe`), a dynamic-link library (`.dll`) or a static library (`.lib`).
 
 Basic C++ compilation involves three main steps:
 
 - The C++ preprocessor transforms all the #directives and macro definitions in each source file. This creates a *translation unit*.
-- The C++ compiler compiles each translation unit into object files (.obj), applying whatever compiler options have been set.
+- The C++ compiler compiles each translation unit into object files (`.obj`), applying whatever compiler options have been set.
 - The *linker* merges the object files into a single executable, applying the linker options that have been set.
 
 ## The Microsoft C++ (MSVC) Build Tools
 
 The Microsoft C++ compiler, linker, standard libraries, and related utilities make up the Microsoft C++ (MSVC) Build Tools (also called a toolchain or toolset). These are included in Visual Studio. You can also download and use the command-line toolset as a free standalone package. For more information, see [Build Tools for Visual Studio](https://visualstudio.microsoft.com/downloads/#build-tools-for-visual-studio-2022) on the Visual Studio Downloads page.
 
-You can build simple programs by invoking the MSVC compiler (cl.exe) directly from the command line. The following command accepts a single source code file, and invokes cl.exe to build an executable called *hello.exe*:
+You can build simple programs by invoking the MSVC compiler (`cl.exe`) directly from the command line. The following command accepts a single source code file, and invokes `cl.exe` to build an executable called *`hello.exe`*:
 
 ```cmd
 cl /EHsc hello.cpp
 ```
 
-Here the compiler (cl.exe) automatically invokes the C++ preprocessor and the linker to produce the final output file. For more information, see [Building on the command line](building-on-the-command-line.md).
+Here the compiler (`cl.exe`) automatically invokes the C++ preprocessor and the linker to produce the final output file. For more information, see [Building on the command line](building-on-the-command-line.md).
 
 ## Build systems and projects
 
 Most real-world programs use some kind of *build system* to manage complexities of compiling multiple source files for multiple configurations (debug vs. release), multiple platforms (x86, x64, ARM, and so on), custom build steps, and even multiple executables that must be compiled in a certain order. You make settings in a build configuration file(s), and the build system accepts that file as input before it invokes the compiler. The set of source code files and build configuration files needed to build an executable file is called a *project*.
 
 The following list shows various options for Visual Studio Projects - C++:
 
-- create a Visual Studio project by using the Visual Studio IDE and configure it by using property pages. Visual Studio projects produce programs that run on Windows. For an overview, see [Compiling and Building](/visualstudio/ide/compiling-and-building-in-visual-studio) in the Visual Studio documentation.
+- Create a Visual Studio project by using the Visual Studio IDE and configure it by using property pages. Visual Studio projects produce programs that run on Windows. For an overview, see [Compiling and Building](/visualstudio/ide/compiling-and-building-in-visual-studio) in the Visual Studio documentation.
 
-- open a folder that contains a CMakeLists.txt file. CMake support is integrated into Visual Studio. You can use the IDE to edit, test, and debug without modifying the CMake files in any way. This enables you to work in the same CMake project as others who might be using different editors. CMake is the recommended approach for cross-platform development. For more information, see [CMake projects](cmake-projects-in-visual-studio.md).
+- Open a folder that contains a `CMakeLists.txt` file. CMake support is integrated into Visual Studio. You can use the IDE to edit, test, and debug without modifying the CMake files in any way. This enables you to work in the same CMake project as others who might be using different editors. CMake is the recommended approach for cross-platform development. For more information, see [CMake projects](cmake-projects-in-visual-studio.md).
 
-- open a loose folder of source files with no project file. Visual Studio will use heuristics to build the files. This is an easy way to compile and run small console applications. For more information, see [Open Folder projects](open-folder-projects-cpp.md).
+- Open a loose folder of source files with no project file. Visual Studio will use heuristics to build the files. This is an easy way to compile and run small console applications. For more information, see [Open Folder projects](open-folder-projects-cpp.md).
 
-- open a folder that contains a makefile, or any other build system configuration file. You can configure Visual Studio to invoke any arbitrary build commands by adding JSON files to the folder. For more information, see [Open Folder projects](open-folder-projects-cpp.md).
+- Open a folder that contains a makefile, or any other build system configuration file. You can configure Visual Studio to invoke any arbitrary build commands by adding JSON files to the folder. For more information, see [Open Folder projects](open-folder-projects-cpp.md).
 
 - Open a Windows makefile in Visual Studio. For more information, see [NMAKE Reference](reference/nmake-reference.md).
 
 ## MSBuild from the command line
 
-You can invoke MSBuild from the command line by passing it a .vcxproj file along with command-line options. This approach requires a good understanding of MSBuild, and is recommended only when necessary. For more information, see [MSBuild](msbuild-visual-cpp.md).
+You can invoke MSBuild from the command line by passing it a `.vcxproj` file along with command-line options. This approach requires a good understanding of MSBuild, and is recommended only when necessary. For more information, see [MSBuild](msbuild-visual-cpp.md).
 
 ## In This Section
 
@@ -74,7 +73,7 @@ Discusses how to use the C/C++ compiler and build tools directly from the comman
 How to create, debug, and deploy C/C++ DLLs (shared libraries) in Visual Studio.
 
 [Walkthrough: Creating and Using a Static Library](walkthrough-creating-and-using-a-static-library-cpp.md)\
-How to create a **.lib** binary file.
+How to create a `.lib` binary file.
 
 [Building C/C++ Isolated Applications and Side-by-side Assemblies](building-c-cpp-isolated-applications-and-side-by-side-assemblies.md)\
 Describes the deployment model for Windows Desktop applications, based on the idea of isolated applications and side-by-side assemblies.
@@ -86,7 +85,7 @@ How to target 64-bit x64 hardware with the MSVC build tools.
 How to use the MSVC Build Tools to target ARM hardware.
 
 [Optimizing Your Code](optimizing-your-code.md)\
-How to optimize your code in various ways including program guided optimizations.
+How to optimize your code in various ways including profile-guided optimization (PGO).
 
 [Configuring Programs for Windows XP](configuring-programs-for-windows-xp.md)\
 How to target Windows XP with the MSVC build tools.

docs/build/reference/zc-conformance.md

@@ -30,7 +30,7 @@ Here are the **`/Zc`** compiler options:
 | [`/Zc:checkGwOdr[-]`](zc-check-gwodr.md) | Enforce Standard C++ ODR violations under `/Gw`. |
 | [`/Zc:enumTypes[-]`](zc-enumtypes.md) | Enable Standard C++ rules for `enum` type deduction. Off by default. |
 | [`/Zc:externC[-]`](zc-externc.md) | Enforce Standard C++ rules for `extern "C"` functions. Off by default unless **`/permissive-`** is specified. |
-| [`/Zc:externConstexpr[-]`](zc-externconstexpr.md) | Enable external linkage for **`constexpr`** variables. Off by default. |
+| [`/Zc:externConstexpr[-]`](zc-externconstexpr.md) | Enable external linkage for **`constexpr`** variables. Off by default unless **`/permissive-`** is specified. |
 | [`/Zc:forScope[-]`](zc-forscope-force-conformance-in-for-loop-scope.md) | Enforce Standard C++ **`for`** scoping rules. On by default. |
 | [`/Zc:gotoScope[-]`](zc-gotoscope.md) | Enforce Standard C++ **`goto`** rules around local variable initialization. Off by default unless **`/permissive-`** is specified. |
 | [`/Zc:hiddenFriend[-]`](zc-hiddenfriend.md) | Enforce Standard C++ hidden friend rules. Off by default unless **`/permissive-`**  is specified. |

docs/data/odbc/recordset-fetching-records-in-bulk-odbc.md

@@ -1,9 +1,8 @@
 ---
-description: "Learn more about: Recordset: Fetching Records in Bulk (ODBC)"
 title: "Recordset: Fetching Records in Bulk (ODBC)"
-ms.date: "11/04/2016"
+description: "Learn more about: Recordset: Fetching Records in Bulk (ODBC)"
+ms.date: 11/04/2016
 helpviewer_keywords: ["bulk row fetching, implementing", "ODBC recordsets, bulk row fetching", "bulk record field exchange", "bulk row fetching", "bulk RFX functions", "recordsets, bulk row fetching", "DoBulkFieldExchange method", "fetching ODBC records in bulk", "RFX (ODBC), bulk", "rowsets, bulk row fetching", "RFX (ODBC), bulk row fetching"]
-ms.assetid: 20d10fe9-c58a-414a-b675-cdf9aa283e4f
 ---
 # Recordset: Fetching Records in Bulk (ODBC)
 
@@ -74,7 +73,7 @@ public:
    .
    .
    .
-}
+};
 ```
 
 You can either allocate these storage buffers manually or have the framework do the allocation. To allocate the buffers yourself, you must specify the `CRecordset::userAllocMultiRowBuffers` option of the *dwOptions* parameter in the `Open` member function. Be sure to set the sizes of the arrays at least equal to the rowset size. If you want to have the framework do the allocation, you should initialize your pointers to NULL. This is typically done in the recordset object's constructor:

docs/error-messages/compiler-errors-1/compiler-error-c2135.md

@@ -1,33 +1,38 @@
 ---
 title: "Compiler Error C2135"
 description: "Learn more about: Compiler Error C2135"
-ms.date: 11/04/2016
+ms.date: 08/13/2025
 f1_keywords: ["C2135"]
 helpviewer_keywords: ["C2135"]
 ---
 # Compiler Error C2135
 
-> 'bit operator' : illegal bit field operation
+> '*identifier*': you cannot apply '*operator*' to a bit-field
 
 ## Remarks
 
-The address-of operator (`&`) cannot be applied to a bit field.
+The [address-of operator (`&`)](../../cpp/address-of-operator-amp.md), [unary plus operator (`+`)](../../cpp/unary-plus-and-negation-operators-plus-and.md), [unary negation operator (`-`)](../../cpp/unary-plus-and-negation-operators-plus-and.md), [logical negation operator (`!`)](../../cpp/logical-negation-operator-exclpt.md), [one's complement operator (`~`)](../../cpp/one-s-complement-operator-tilde.md), and [indirection operator (`*`)](../../cpp/indirection-operator-star.md) cannot be applied to a bit-field in this context.
 
 ## Example
 
 The following example generates C2135:
 
 ```cpp
 // C2135.cpp
-struct S {
-   int i : 1;
-};
 
-struct T {
-   int j;
+struct S
+{
+    int bit_field : 1;
+    int integer;
 };
-int main() {
-   &S::i;   // C2135 address of a bit field
-   &T::j;   // OK
+
+int main()
+{
+    &S::bit_field;   // C2135
+    &S::integer;     // OK
 }
 ```
+
+## See also
+
+[C2104](compiler-error-c2104.md)

docs/error-messages/compiler-errors-1/compiler-error-c2178.md

@@ -1,7 +1,7 @@
 ---
 title: "Compiler Error C2178"
 description: "Learn more about: Compiler Error C2178"
-ms.date: 05/08/2017
+ms.date: 08/11/2025
 f1_keywords: ["C2178"]
 helpviewer_keywords: ["C2178"]
 ---
@@ -11,23 +11,41 @@ helpviewer_keywords: ["C2178"]
 
 ## Remarks
 
-A **`mutable`** specifier was used in a declaration, but the specifier is not allowed in this context.
+A **`mutable`** specifier was used in a declaration, but the specifier is not allowed in this context. It can only be applied to non-static, non-const, and non-reference data members. For more information, see [Mutable Data Members](../../cpp/mutable-data-members-cpp.md).
 
-The **`mutable`** specifier can be applied only to names of class data members, and cannot be applied to names declared **`const`** or **`static`**, and cannot be applied to reference members.
+A **`consteval`** specifier was used on a [destructor](../../cpp/destructors-cpp.md), allocation function, or deallocation function.
 
-## Example
+## Example: `mutable`
 
-The following example shows how C2178 may occur, and how to fix it.
+The following example shows how C2178 may occur with the **`mutable`** specifier, and how to resolve it:
 
 ```cpp
-// C2178.cpp
-// compile with: cl /c /W4 C2178.cpp
+// C2178_mutable.cpp
+// compile with: /c
 
-class S {
-    mutable const int i; // C2178
-    // To fix, declare either const or mutable, not both.
+struct S
+{
+    mutable const int i;   // C2178, remove mutable or const to resolve
 };
 
-mutable int x = 4; // C2178
-// To fix, remove mutable keyword
+mutable int x = 4;   // C2178, remove mutable to resolve
+```
+
+## Example: `consteval`
+
+The following example shows how C2178 may occur with the **`consteval`** specifier. To resolve this error, remove all **`consteval`** specifiers:
+
+```cpp
+// C2178_consteval.cpp
+// compile with: /c /std:c++20
+
+#include <cstddef>
+
+struct S
+{
+    consteval ~S() {}   // C2178
+
+    consteval static void* operator new(std::size_t size);   // C2178
+    consteval static void operator delete(void* ptr);        // C2178
+};
 ```

docs/error-messages/compiler-errors-1/compiler-error-c2190.md

@@ -1,7 +1,7 @@
 ---
 title: "Compiler Error C2190"
 description: "Learn more about: Compiler Error C2190"
-ms.date: 11/04/2016
+ms.date: 08/22/2025
 f1_keywords: ["C2190"]
 helpviewer_keywords: ["C2190"]
 ---
@@ -11,7 +11,7 @@ helpviewer_keywords: ["C2190"]
 
 ## Remarks
 
-A C function was declared a second time with a shorter parameter list. C does not support overloaded functions.
+A C function was declared a second time with a shorter parameter list. C does not support overloaded functions. Without [`/Za`](../../build/reference/za-ze-disable-language-extensions.md), the compiler emits [Compiler Warning (level 1) C4030](../compiler-warnings/compiler-warning-level-1-c4030.md) instead.
 
 ## Example
 
@@ -20,7 +20,13 @@ The following example generates C2190:
 ```c
 // C2190.c
 // compile with: /Za /c
-void func( int, float );
-void func( int  );   // C2190, different parameter list
-void func2( int  );   // OK
+
+void func1(int, float);
+void func1(int);   // C2190, shorter parameter list
+
+void func2(int);   // OK
 ```
+
+## See also
+
+[Compiler Error C2191](compiler-error-c2191.md)

docs/error-messages/compiler-errors-1/compiler-error-c2191.md

@@ -1,7 +1,7 @@
 ---
 title: "Compiler Error C2191"
 description: "Learn more about: Compiler Error C2191"
-ms.date: 11/04/2016
+ms.date: 08/22/2025
 f1_keywords: ["C2191"]
 helpviewer_keywords: ["C2191"]
 ---
@@ -11,7 +11,7 @@ helpviewer_keywords: ["C2191"]
 
 ## Remarks
 
-A C function was declared a second time with a longer parameter list. C does not support overloaded functions.
+A C function was declared a second time with a longer parameter list. C does not support overloaded functions. Without [`/Za`](../../build/reference/za-ze-disable-language-extensions.md), the compiler emits [Compiler Warning (level 1) C4031](../compiler-warnings/compiler-warning-level-1-c4031.md) instead.
 
 ## Example
 
@@ -20,7 +20,13 @@ The following example generates C2191:
 ```c
 // C2191.c
 // compile with: /Za /c
-void func( int );
-void func( int, float );   // C2191 different parameter list
-void func2( int, float );   // OK
+
+void func1(int);
+void func1(int, float);   // C2191, longer parameter list
+
+void func2(int, float);   // OK
 ```
+
+## See also
+
+[Compiler Error C2190](compiler-error-c2190.md)

docs/error-messages/compiler-errors-1/compiler-error-c2277.md

@@ -1,27 +1,29 @@
 ---
 title: "Compiler Error C2277"
 description: "Learn more about: Compiler Error C2277"
-ms.date: 11/04/2016
+ms.date: 08/27/2025
 f1_keywords: ["C2277"]
 helpviewer_keywords: ["C2277"]
 ---
 # Compiler Error C2277
 
-> 'identifier' : cannot take address of this member function
+> '*function*': cannot take address of this member function
 
 ## Remarks
 
-You cannot take the address of a member function.
+You cannot take the address of a [constructor](../../cpp/constructors-cpp.md) or [destructor](../../cpp/destructors-cpp.md). For more information, see [Address-of operator: `&`](../../cpp/address-of-operator-amp.md) and [Pointers to Members](../../cpp/pointers-to-members.md).
 
 ## Example
 
 The following example generates C2277:
 
 ```cpp
-// C2277.cpp
-class A {
+// compile with: /c
+
+class A
+{
 public:
    A();
 };
-(*pctor)() = &A::A;   // C2277
+(*pctor)() = &A::A; // C2277
 ```

docs/error-messages/compiler-errors-2/compiler-error-c2698.md

@@ -30,5 +30,5 @@ struct B {
 struct C : A, B {
    using A::x;
    using B::x;   // C2698
-}
+};
 ```

docs/error-messages/compiler-errors-2/compiler-error-c3083.md

@@ -1,32 +1,31 @@
 ---
-description: "Learn more about: Compiler Error C3083"
 title: "Compiler Error C3083"
-ms.date: "11/04/2016"
+description: "Learn more about: Compiler Error C3083"
+ms.date: 08/14/2025
 f1_keywords: ["C3083"]
 helpviewer_keywords: ["C3083"]
-ms.assetid: 05ff791d-52bb-41eb-9511-3ef89d7f4710
 ---
 # Compiler Error C3083
 
-'function': the symbol to the left of a '::' must be a type
+> '*identifier*': the symbol to the left of a '::' must be a type
 
-A function was called incorrectly.
+## Remarks
+
+The qualification used is invalid. Ensure that no extra symbols were used in the qualification and that you included all required headers.
 
 ## Example
 
-The following sample generates C3083.
+The following example generates C3083:
 
 ```cpp
 // C3083.cpp
 // compile with: /c
-struct N {
-   ~N();
-};
 
-struct N1 {
-   ~N1();
+struct S
+{
+    S();
 };
 
-N::N::~N() {}   // C3083
-N1::~N1() {}   // OK
+S::Extra::S() {}   // C3083
+S::S() {}          // OK
 ```