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

Author: PatAltimore

docs/code-quality/c26865.md

@@ -0,0 +1,54 @@
+---
+description: "Learn more about: Warning C26865"
+title: Warning C26865 
+ms.date: 10/03/2022
+f1_keywords: ["C26865", "ALLOCATION_DEALLOCATION_MISMATCH", "__WARNING_ALLOCATION_DEALLOCATION_MISMATCH"]
+helpviewer_keywords: ["C26865"]
+ms.assetid: 2fbe9dc5-fa43-47b9-97a7-3f8215da1d40
+---
+# Warning C26865
+
+> Memory allocated with '\<allocation-function\>' is being deallocated with '\<wrong-deallocation-function\>'. Use '\<correct-deallocation-function\>' instead.
+
+This rule was added in Visual Studio 2026 18.0.
+
+## Remarks
+
+This warning indicates that the memory was allocated with one family of allocation functions, but was freed with a deallocation function from a different family. This usage results in undefined behavior according to C/C++ and the Microsoft MSVC implementation.
+
+The exact ramifications of this defect are difficult to predict. It might result in leaks for classes with destructors that perform memory deallocation. It could cause inconsistent behavior for classes with destructors that perform semantically significant operations, or memory corruptions and crashes. In other cases the mismatch might be unimportant, depending on the implementation of the compiler and its libraries. Analysis tools can't always distinguish between these situations.
+
+If memory is allocated with one family of allocation functions, it should be freed with a matching deallocation function.
+
+C26865 covers the following allocation/deallocation pairs:
+
+- C++ scalar new (`new`) must be deallocated with scalar delete (`delete`).
+- C++ array new (`new[]`) must be deallocated with array delete (`delete[]`).
+- C/C++ `malloc`/`calloc`/`realloc` must be deallocated with `free` (or `realloc`).
+- Windows `HeapAlloc` must be deallocated with `HeapFree`.
+- Windows `GlobalAlloc` must be deallocated with `GlobalFree`.
+- Windows `LocalAlloc` must be deallocated with `LocalFree`.
+- Windows `MIDL_user_allocate` must be deallocated with `MIDL_user_free`.
+- Component Object Model (COM) `CoTaskMemAlloc` must be deallocated with `CoTaskMemFree`.
+
+Code analysis name: `ALLOCATION_DEALLOCATION_MISMATCH`
+
+## Example
+
+The following sample code generates warning C26865:
+
+```cpp
+void f() {
+    int *pInt = (int *)calloc(10, sizeof(int));
+    // code ...
+    delete pInt; // C26865: Memory allocated with 'calloc' is being deallocated with 'delete'. Use 'free' instead.
+}
+
+void g() {
+    char * str = new char[50];
+    // code ...
+    delete str; // C26865: Memory allocated with 'new[]' is being deallocated with 'delete'. Use 'delete[]' instead.
+}
+```
+
+Manual memory management has many pitfalls in terms of memory leaks and exceptions. To avoid these kinds of potential leaks altogether, use the mechanisms that are provided by the C++ Standard Library (STL). These mechanisms include [`shared_ptr`](../standard-library/shared-ptr-class.md), [`unique_ptr`](../standard-library/unique-ptr-class.md), and containers such as [`vector`](../standard-library/vector.md). For more information, see [Smart pointers](../cpp/smart-pointers-modern-cpp.md) and [C++ Standard Library](../standard-library/cpp-standard-library-reference.md).

docs/code-quality/c6278.md

@@ -9,6 +9,10 @@ helpviewer_keywords: ["C6278"]
 
 > '*variable*' is allocated with array new [], but deleted with scalar delete. Destructors will not be called.
 
+## Notice
+
+Warning C6278 was removed in Visual Studio 2026. Use the more generic warning [`C26865`](../code-quality/C26865.md) instead.
+
 ## Remarks
 
 This warning appears only in C++ code and indicates that the calling function has inconsistently allocated memory with the array **`new []`** operator, but freed it with the scalar **`delete`** operator. This usage is undefined behavior according to the C++ standard and the Microsoft C++ implementation.

docs/code-quality/c6279.md

@@ -9,6 +9,12 @@ helpviewer_keywords: ["C6279"]
 
 > '*variable-name*' is allocated with scalar new, deleted with array delete []
 
+This warning appears only in C++ code and indicates that the calling function has inconsistently allocated memory with the scalar `new` operator, but freed it with the array `delete[]` operator. If memory is allocated with scalar `new`, it should typically be freed with scalar `delete`.
+
+## Notice
+
+Warning C6279 was removed in Visual Studio 2026. Use the more generic warning [`C26865`](../code-quality/C26865.md) instead.
+
 ## Remarks
 
 This warning appears only in C++ code and indicates that the calling function has inconsistently allocated memory with the scalar `new` operator, but freed it with the array `delete[]` operator. If memory is allocated with scalar `new`, it should typically be freed with scalar `delete`.

docs/code-quality/c6280.md

@@ -9,6 +9,12 @@ helpviewer_keywords: ["C6280"]
 
 > '*variable-name*' is allocated with '*function-name-1*', but deleted with '*function-name-2*'
 
+This warning indicates that the calling function has inconsistently allocated memory by using a function from one family and freed it by using a function from another.
+
+## Notice
+
+Warning C6280 was removed in Visual Studio 2026. Use the more generic warning [`C26865`](../code-quality/C26865.md) instead.
+
 ## Remarks
 
 This warning indicates that the calling function has inconsistently allocated memory by using a function from one family and freed it by using a function from another.

docs/code-quality/c6283.md

@@ -9,6 +9,12 @@ helpviewer_keywords: ["C6283"]
 
 > '*variable-name*' is allocated with array new [], but deleted with scalar delete
 
+This warning appears only in C++ code and indicates that the calling function has inconsistently allocated memory with the array `new []` operator, but freed it with the scalar `delete` operator.
+
+## Notice
+
+Warning C6283 was removed in Visual Studio 2026. Use the more generic warning [`C26865`](../code-quality/C26865.md) instead.
+
 ## Remarks
 
 This warning appears only in C++ code and indicates that the calling function has inconsistently allocated memory with the array `new []` operator, but freed it with the scalar `delete` operator.

docs/code-quality/toc.yml

@@ -661,6 +661,8 @@ items:
     href: ../code-quality/c26863.md
   - name: Warning C26864
     href: ../code-quality/c26864.md
+  - name: Warning C26865
+    href: ../code-quality/c26865.md
   - name: Warning C28020
     href: ../code-quality/c28020.md
   - name: Warning C28021

docs/cross-platform/build-an-opengl-es-application-on-android-and-ios.md

@@ -8,13 +8,14 @@ ms.custom: sfi-image-nochange
 
 # Build an OpenGL ES application on Android and iOS
 
+> [!IMPORTANT]
+> Starting with Visual Studio 2026 (version 18.0), the Mobile development with C++ workload for iOS and Android, as well as the Embedded and IoT tools (RTOS Viewer, Serial Monitor, Peripheral Viewer, and ST Project Import), are no longer supported and will be removed in a future update. The Android NDKs included in the Mobile development with C++ workload remain supported.
+> OpenGL support is no longer available. It was last available in Visual Studio 17.3.
+
 You can create Visual Studio solutions and projects for iOS apps and Android apps that share common code. This article guides you through a combined solution template. It creates both an iOS app, and an Android Native Activity app. The apps have C++ code in common that uses OpenGL ES to display the same animated rotating cube on each platform. OpenGL ES (OpenGL for Embedded Systems or GLES) is a 2D and 3D graphics API. It's supported on many mobile devices.
 
 ## Requirements
 
-> [!IMPORTANT]
-> OpenGL support is no longer available. It was last available in Visual Studio 17.3.
-
 Here are the system requirements to create an OpenGL ES app for iOS and Android. If you haven't already, install the Mobile Development with C++ workload in the Visual Studio Installer. To get the OpenGL ES templates, and to build for iOS, include the optional C++ iOS development tools. To build for Android, install the C++ Android development tools and the required third-party tools: Android NDK, Apache Ant, and Google Android Emulator.
 
 For better emulator performance on Intel platforms, one option is to install the Intel Hardware Accelerated Execution Manager (HAXM). For detailed instructions, see [Install cross-platform mobile development with C++](../cross-platform/install-visual-cpp-for-cross-platform-mobile-development.md).

docs/cross-platform/create-an-android-native-activity-app.md

@@ -2,11 +2,13 @@
 description: "Learn more about: Create an Android Native Activity App"
 title: "Create an Android Native Activity App"
 ms.date: "10/17/2019"
-ms.assetid: 884014b1-5208-45ec-b0da-ad0070d2c24d
 ms.topic: how-to
 ---
 # Create an Android Native Activity App
 
+> [!IMPORTANT]
+> Starting with Visual Studio 2026 (version 18.0), the Mobile development with C++ workload for iOS and Android, as well as the Embedded and IoT tools (RTOS Viewer, Serial Monitor, Peripheral Viewer, and ST Project Import), are no longer supported and will be removed in a future update. The Android NDKs included in the Mobile development with C++ workload remain supported.
+
 When you install the cross-platform **Mobile development with C++** workload, Visual Studio can be used to create fully functional Android Native Activity apps. The Android Native Development Kit (NDK) is a toolset that allows you to implement the majority of your Android app using pure C/C++ code. Some Java JNI code acts as glue to allow your C/C++ code to interact with Android. The Android NDK introduced the ability to create Native Activity apps with Android API Level 9. Native Activity code is popular for creating gaming and graphic intensive apps that use Unreal Engine or OpenGL. This topic will guide you through creation of a simple Native Activity app that uses OpenGL. Additional topics walk through the developer lifecycle of editing, building, debugging and deploying Native Activity code.
 
 ## Requirements

docs/cross-platform/cross-platform-mobile-development-examples.md

@@ -5,6 +5,9 @@ ms.date: 03/04/2024
 ---
 # Cross-platform mobile development examples
 
+> [!IMPORTANT]
+> Starting with Visual Studio 2026 (version 18.0), the Mobile development with C++ workload for iOS and Android, as well as the Embedded and IoT tools (RTOS Viewer, Serial Monitor, Peripheral Viewer, and ST Project Import), are no longer supported and will be removed in a future update. The Android NDKs included in the Mobile development with C++ workload remain supported.
+
 Several of the templates installed by the **Mobile development with C++** workload generate complete examples that you can use to learn from. Additionally, here are some example applications that you can download and try out in Visual Studio.
 
 - [hello-jni Android Application Sample](https://github.com/android/ndk-samples/tree/master/hello-jni)

docs/cross-platform/general-android-prop-page.md

@@ -2,7 +2,6 @@
 description: "Learn more about: General Project Properties (Android C++)"
 title: "General Project Properties (Android C++)"
 ms.date: "10/23/2017"
-ms.assetid: 65f4868b-b864-4989-a275-1e51869ef599
 f1_keywords:
   - VC.Project.VCConfiguration.Android.OutputDirectory
   - VC.Project.VCConfiguration.Android.IntermediateDirectory
@@ -17,6 +16,9 @@ f1_keywords:
 ---
 # General Project Properties (Android C++)
 
+> [!IMPORTANT]
+> Starting with Visual Studio 2026 (version 18.0), the Mobile development with C++ workload for iOS and Android, as well as the Embedded and IoT tools (RTOS Viewer, Serial Monitor, Peripheral Viewer, and ST Project Import), are no longer supported and will be removed in a future update. The Android NDKs included in the Mobile development with C++ workload remain supported.
+
 | Property | Description | Choices |
 |--|--|--|
 | Output Directory | Specifies a relative path to the output file directory; can include environment variables. |