Update screenshot borders

Author: Colin Robertson

docs/sanitizers/asan-offline-crash-dumps.md

@@ -52,17 +52,17 @@ The following steps are for local or distributed scenarios that lead to creation
 
 1. Open Visual Studio and select **Continue without code**. Then select **File** > **Open** > **File** to open the File Open dialog. Make sure the file name suffix is **.dmp**.
 
-   ![Screenshot of the File Open File menu in Visual Studio](./media/asan-open-crash-dump-file.png)
+   :::image type="content" source="./media/asan-open-crash-dump-file.png" alt-text="Screenshot of the File Open File menu in Visual Studio.":::
 
    The screen shown here needs one more step to enable the IDE access to symbols and source.
 
 1. Set the symbol paths, and then choose **Debug with Native Only**.
 
-   ![Screenshot of the Minidump Summary display in Visual Studio](./media/asan-dump-file-open.png)
+   :::image type="content" source="./media/asan-dump-file-open.png" alt-text="Screenshot of the Minidump Summary display in Visual Studio.":::
 
 This screenshot shows the final loaded dump file, with sources and AddressSanitizer metadata loaded.
 
-![Screenshot of the debugger showing source files and AddressSanitizer metadata](./media/asan-view-crash-metadata.png)
+:::image type="content" source="./media/asan-view-crash-metadata.png" alt-text="Screenshot of the debugger showing source files and AddressSanitizer metadata.":::
 
 ## <a name="source"></a> Source and symbols
 

docs/sanitizers/asan-shadowbytes.md

@@ -23,7 +23,7 @@ One shadow byte describes how many bytes are currently accessible as follows:
 
 Consider this shadow byte legend where all negative numbers are defined:
 
-![Screenshot of the AddressSanitizer shadow-byte legend](./media/asan-shadow-byte-legend.png)
+:::image type="content" source="./media/asan-shadow-byte-legend.png" alt-text="Screenshot of the AddressSanitizer shadow-byte legend.":::
 
 ## Mapping - describing your address space
 

docs/sanitizers/asan.md

@@ -36,7 +36,7 @@ Microsoft's AddressSanitizer technology enables integration with the Visual Stud
 
 The AddressSanitizer is installed by default with C++ workloads in the Visual Studio Installer. However, if you're upgrading from an older version of Visual Studio 2019, you'll need to use the Installer to enable ASan support after the upgrade:
 
-![Visual Studio Installer screenshot highlighting the C++ AddressSanitizer component](media/asan-installer-option.png)
+:::image type="content" source="media/asan-installer-option.png" alt-text="Visual Studio Installer screenshot highlighting the C++ AddressSanitizer component":::
 
 You can choose **Modify** on your existing Visual Studio installation from the Visual Studio Installer to get to the screen above.
 
@@ -95,13 +95,13 @@ int main() {
 
 Using a developer command prompt for Visual Studio 2019, compile *`main.cpp`* using `/fsanitize=address /Zi`
 
-![Screenshot of a command prompt showing the command to compile with AddressSanitizer options](media/asan-command-basic-global-overflow.png)
+:::image type="content" source="media/asan-command-basic-global-overflow.png" alt-text="Screenshot of a command prompt showing the command to compile with AddressSanitizer options.":::
 
 When you run the resulting *`main.exe`* at the command line, it creates the formatted error report seen below.
 
 Consider the overlaid, red boxes that highlight seven key pieces of information:
 
-![Screenshot of the debugger showing a basic global overflow error](media/asan-basic-global-overflow.png)
+:::image type="content" source="media/asan-basic-global-overflow.png" alt-text="Screenshot of the debugger showing a basic global overflow error.":::
 
 ### Red highlights, from top to bottom
 
@@ -120,7 +120,7 @@ Consider the overlaid, red boxes that highlight seven key pieces of information:
 
 AddressSanitizer is integrated with the Visual Studio IDE. To turn on the AddressSanitizer for an MSBuild project, right-click on the project in Solution Explorer and choose Properties. In the Property Pages dialog, select **Configuration Properties** > **C/C++** > **General**, then modify the **Enable AddressSanitizer** property. Choose **OK** to save your changes.
 
-![Screenshot of the Property Pages dialog showing the Enable AddressSanitizer property](media/asan-project-system-dialog.png)
+:::image type="content" source="media/asan-project-system-dialog.png" alt-text="Screenshot of the Property Pages dialog showing the Enable AddressSanitizer property.":::
 
 To build from the IDE, opt out of [these incompatible options](./asan-known-issues.md#incompatible-options). For an existing project compiled by using **`/Od`** (or Debug mode), you may need to turn off these options:
 
@@ -130,15 +130,15 @@ To build from the IDE, opt out of [these incompatible options](./asan-known-issu
 
 To build and run the debugger, enter **F5**. You'll see this window in Visual Studio:
 
-![Screenshot of the debugger showing a global buffer overflow error](media/asan-global-buffer-overflow-F5.png)
+:::image type="content" source="media/asan-global-buffer-overflow-F5.png" alt-text="Screenshot of the debugger showing a global buffer overflow error.":::
 
 ## <a name="ide-cmake"></a> Using the AddressSanitizer from Visual Studio: CMake
 
 To enable the AddressSanitizer for [a CMake project created to target Windows](../build/cmake-projects-in-visual-studio.md), take these steps:
 
 1. Open the **Configurations** dropdown in the toolbar at the top of the IDE and select **Manage Configurations**.
 
-   ![Screenshot of the CMake configuration dropdown](media/asan-cmake-configuration-dropdown.png)
+   :::image type="content" source="media/asan-cmake-configuration-dropdown.png" alt-text="Screenshot of the CMake configuration dropdown.":::
 
    That selection opens the CMake Project Settings UI, which is saved in a CMakeSettings.json file.
 
@@ -148,13 +148,13 @@ To enable the AddressSanitizer for [a CMake project created to target Windows](.
 
    This image is of CMakeSettings.json after that change:
 
-   ![Screenshot of the text editor view of CMakeSettings.json](media/asan-cmake-json.png)
+   :::image type="content" source="media/asan-cmake-json.png" alt-text="Screenshot of the text editor view of CMakeSettings.json.":::
 
 1. Enter **Ctrl+S** to save this JSON file, then enter **F5** to recompile and run under the debugger.
 
 This screenshot captures the error from the CMake build.
 
-![Screenshot of the CMake build error message](media/asan-cmake-error-f5.png)
+:::image type="content" source="media/asan-cmake-error-f5.png" alt-text="Screenshot of the CMake build error message.":::
 
 ## <a name="crash-dumps"></a> AddressSanitizer crash dumps
 
@@ -164,11 +164,11 @@ These new dump files can lead to efficiencies when analyzing a bug. You don't ne
 
 To produce a new type of dump file that can be viewed in Visual Studio on another machine at a later date:
 
-```makefile
+```cmd
 set ASAN_SAVE_DUMPS=MyFileName.dmp
 ```
 
-Starting with Visual Studio 16.9 you can display **a precisely diagnosed error**, stored in MyFileName.dmp, on top of your source code.
+Starting with Visual Studio 16.9 you can display **a precisely diagnosed error**, stored in your *`*.dmp`* file, on top of your source code.
 
 [This new crash dump functionality](./asan-offline-crash-dumps.md) enables cloud-based workflows, or distributed testing. It can also be used to file a detailed, actionable bug in any scenario.
 

docs/sanitizers/error-alloc-dealloc-mismatch.md

@@ -50,7 +50,7 @@ devenv /debugexe example1.exe 2
 
 ### Resulting error
 
-![Screenshot of debugger displaying alloc-dealloc-mismatch error in example 1.](media/alloc-dealloc-mismatch-example-1.png)
+:::image type="content" source="media/alloc-dealloc-mismatch-example-1.png" alt-text="Screenshot of debugger displaying alloc-dealloc-mismatch error in example 1.":::
 
 ## See also
 

docs/sanitizers/error-allocation-size-too-big.md

@@ -46,7 +46,7 @@ devenv /debugexe example1.exe
 
 ### Resulting error
 
-![Screenshot of debugger displaying allocation-size-too-big error in example 1.](media/allocation-size-too-big-example-1.png)
+:::image type="content" source="media/allocation-size-too-big-example-1.png" alt-text="Screenshot of debugger displaying allocation-size-too-big error in example 1.":::
 
 ## See also
 

docs/sanitizers/error-calloc-overflow.md

@@ -41,7 +41,7 @@ devenv /debugexe example1.exe
 
 ### Resulting error
 
-![Screenshot of debugger displaying calloc-overflow error in example 1.](media/calloc-overflow-example-1.png)
+:::image type="content" source="media/calloc-overflow-example-1.png" alt-text="Screenshot of debugger displaying calloc-overflow error in example 1.":::
 
 ## See also
 

docs/sanitizers/error-double-free.md

@@ -38,7 +38,7 @@ devenv /debugexe example1.exe
 
 ### Resulting error - double `operator delete`
 
-![Screenshot of debugger displaying double-free error in example 1.](media/double-free-example-1.png)
+:::image type="content" source="media/double-free-example-1.png" alt-text="Screenshot of debugger displaying double-free error in example 1.":::
 
 ## Example 'C' - double `free`
 
@@ -71,7 +71,7 @@ devenv /debugexe example2.exe
 
 ### Resulting error - double `free`
 
-![Screenshot of debugger displaying double-free error in example 2.](media/double-free-example-2.png)
+:::image type="content" source="media/double-free-example-2.png" alt-text="Screenshot of debugger displaying double-free error in example 2.":::
 
 ## Example - Windows `HeapCreate` double `HeapFree`
 
@@ -101,7 +101,7 @@ devenv /debugexe example3.exe
 
 ### Resulting error - Windows `HeapCreate` double `HeapFree`
 
-![Screenshot of debugger displaying double-free error in example 3.](media/double-free-example-3.png)
+:::image type="content" source="media/double-free-example-3.png" alt-text="Screenshot of debugger displaying double-free error in example 3.":::
 
 ## See also
 

docs/sanitizers/error-dynamic-stack-buffer-overflow.md

@@ -44,7 +44,7 @@ devenv /debugexe example1.exe
 
 ### Resulting error
 
-![Screenshot of debugger displaying dynamic-stack-buffer-overflow error in example 1.](media/dynamic-stack-buffer-overflow-example-1.png)
+:::image type="content" source="media/dynamic-stack-buffer-overflow-example-1.png" alt-text="Screenshot of debugger displaying dynamic-stack-buffer-overflow error in example 1.":::
 
 ## Example - `alloca` overflow (left)
 
@@ -76,7 +76,7 @@ devenv /debugexe example2.exe
 
 ### Resulting error - `alloca` overflow (left)
 
-![Screenshot of debugger displaying dynamic-stack-buffer-overflow error in example 2.](media/dynamic-stack-buffer-overflow-example-2.png)
+:::image type="content" source="media/dynamic-stack-buffer-overflow-example-2.png" alt-text="Screenshot of debugger displaying dynamic-stack-buffer-overflow error in example 2.":::
 
 ## Example - several calls to `alloca`
 
@@ -166,7 +166,7 @@ devenv /debugexe example3.exe
 
 ### Resulting error - several calls to alloca
 
-![Screenshot of debugger displaying dynamic-stack-buffer-overflow error in example 3.](media/dynamic-stack-buffer-overflow-example-3.png)
+:::image type="content" source="media/dynamic-stack-buffer-overflow-example-3.png" alt-text="Screenshot of debugger displaying dynamic-stack-buffer-overflow error in example 3.":::
 
 ## See also
 

docs/sanitizers/error-global-buffer-overflow.md

@@ -59,7 +59,7 @@ devenv /debugexe example1-main.exe
 
 ### Resulting error
 
-![Screenshot of debugger displaying global-buffer-overflow error in example 1.](media/global-overflow-example-1.png)
+:::image type="content" source="media/global-overflow-example-1.png" alt-text="Screenshot of debugger displaying global-buffer-overflow error in example 1.":::
 
 ## Example - simple function level static
 
@@ -93,7 +93,7 @@ devenv /debugexe example2.exe
 
 ### Resulting error - simple function level static
 
-![Screenshot of debugger displaying global-buffer-overflow error in example 2.](media/global-overflow-example-2.png)
+:::image type="content" source="media/global-overflow-example-2.png" alt-text="Screenshot of debugger displaying global-buffer-overflow error in example 2.":::
 
 ## Example - all global scopes in C++
 
@@ -149,7 +149,7 @@ devenv /debugexe example3.exe -l
 
 ### Resulting error - all global scopes in C++
 
-![Screenshot of debugger displaying global-buffer-overflow error in example 3.](media/global-overflow-example-3.png)
+:::image type="content" source="media/global-overflow-example-3.png" alt-text="Screenshot of debugger displaying global-buffer-overflow error in example 3.":::
 
 ## See also
 

docs/sanitizers/error-heap-buffer-overflow.md

@@ -39,7 +39,7 @@ devenv /debugexe example1.exe
 
 ### Resulting error
 
-![Screenshot of debugger displaying heap-buffer-overflow error in example 1.](media/heap-buffer-overflow-example-1.png)
+:::image type="content" source="media/heap-buffer-overflow-example-1.png" alt-text="Screenshot of debugger displaying heap-buffer-overflow error in example 1.":::
 
 ## Example - improper down cast
 
@@ -74,7 +74,7 @@ devenv /debugexe example2.exe
 
 ### Resulting error - improper down cast
 
-![Screenshot of debugger displaying heap-buffer-overflow error in example 2.](media/heap-buffer-overflow-example-2.png)
+:::image type="content" source="media/heap-buffer-overflow-example-2.png" alt-text="Screenshot of debugger displaying heap-buffer-overflow error in example 2.":::
 
 ## Example - strncpy into heap
 
@@ -105,7 +105,7 @@ devenv /debugexe example3.exe
 
 ### Resulting error - strncpy into heap
 
-![Screenshot of debugger displaying heap-buffer-overflow error in example 3.](media/heap-buffer-overflow-example-3.png)
+:::image type="content" source="media/heap-buffer-overflow-example-3.png" alt-text="Screenshot of debugger displaying heap-buffer-overflow error in example 3.":::
 
 ## See also
 

docs/sanitizers/error-heap-use-after-free.md

@@ -37,7 +37,7 @@ devenv /debugexe example1.exe
 
 ### Resulting error
 
-![Screenshot of debugger displaying heap-use-after-free error in example 1.](media/heap-use-after-free-example-1.png)
+:::image type="content" source="media/heap-use-after-free-example-1.png" alt-text="Screenshot of debugger displaying heap-use-after-free error in example 1.":::
 
 ## Example - `operator new`
 
@@ -66,7 +66,7 @@ devenv /debugexe example2.exe
 
 ### Resulting error - operator new
 
-![Screenshot of debugger displaying heap-use-after-free error in example 2.](media/heap-use-after-free-example-2.png)
+:::image type="content" source="media/heap-use-after-free-example-2.png" alt-text="Screenshot of debugger displaying heap-use-after-free error in example 2.":::
 
 ## Example - `realloc`
 
@@ -95,7 +95,7 @@ devenv /debugexe example3.exe
 
 ### Resulting error - realloc
 
-![Screenshot of debugger displaying heap-use-after-free error in example 3.](media/heap-use-after-free-example-3.png)
+:::image type="content" source="media/heap-use-after-free-example-3.png" alt-text="Screenshot of debugger displaying heap-use-after-free error in example 3.":::
 
 ## Example - volatile
 
@@ -124,7 +124,7 @@ devenv /debugexe example4.exe
 
 ### Resulting error - volatile
 
-![Screenshot of debugger displaying error in example 4.](media/heap-use-after-free-example-4.png)
+:::image type="content" source="media/heap-use-after-free-example-4.png" alt-text="Screenshot of debugger displaying error in example 4.":::
 
 ## See also
 

docs/sanitizers/error-invalid-allocation-alignment.md

@@ -38,7 +38,7 @@ devenv /debugexe example1.exe
 
 ### Resulting error
 
-![Screenshot of debugger displaying invalid-allocation-alignment error in example 1.](media/invalid-allocation-alignment-example-1.png)
+:::image type="content" source="media/invalid-allocation-alignment-example-1.png" alt-text="Screenshot of debugger displaying invalid-allocation-alignment error in example 1.":::
 
 ## See also
 

docs/sanitizers/error-memcpy-param-overlap.md

@@ -43,7 +43,7 @@ devenv /debugexe example1.exe
 
 ### Resulting error
 
-![Screenshot of debugger displaying memcpy-param-overlap error in example 1.](media/memcpy-param-overlap-example-1.png)
+:::image type="content" source="media/memcpy-param-overlap-example-1.png" alt-text="Screenshot of debugger displaying memcpy-param-overlap error in example 1.":::
 
 ## See also
 

docs/sanitizers/error-new-delete-type-mismatch.md

@@ -60,7 +60,7 @@ devenv /debugexe example1.exe
 
 ### Resulting error
 
-![Screenshot of debugger displaying new-delete-type-mismatch error in example 1.](media/new-delete-type-mismatch-example-1.png)
+:::image type="content" source="media/new-delete-type-mismatch-example-1.png" alt-text="Screenshot of debugger displaying new-delete-type-mismatch error in example 1.":::
 
 ## See also
 

docs/sanitizers/error-stack-buffer-overflow.md

@@ -36,7 +36,7 @@ devenv /debugexe example1.exe
 
 ### Resulting error
 
-![Screenshot of debugger displaying stack-buffer-overflow error in example 1.](media/stack-buffer-overflow-example-1.png)
+:::image type="content" source="media/stack-buffer-overflow-example-1.png" alt-text="Screenshot of debugger displaying stack-buffer-overflow error in example 1.":::
 
 ## Example - Stack buffer math
 
@@ -72,7 +72,7 @@ devenv /debugexe example2.exe 9
 
 ### Resulting error - Stack buffer math
 
-![Screenshot of debugger displaying stack-buffer-overflow error in example 2.](media/stack-buffer-overflow-example-2.png)
+:::image type="content" source="media/stack-buffer-overflow-example-2.png" alt-text="Screenshot of debugger displaying stack-buffer-overflow error in example 2.":::
 
 ## Example - improper down cast on stack
 
@@ -108,7 +108,7 @@ devenv /debugexe example3.exe
 
 ### Resulting error - improper down cast on stack
 
-![Screenshot of debugger displaying stack-buffer-overflow error in example 3.](media/stack-buffer-overflow-example-3.png)
+:::image type="content" source="media/stack-buffer-overflow-example-3.png" alt-text="Screenshot of debugger displaying stack-buffer-overflow error in example 3.":::
 
 ## See also
 

docs/sanitizers/error-stack-buffer-underflow.md

@@ -37,7 +37,7 @@ devenv /debugexe example1.exe
 
 ### Resulting error
 
-![Screenshot of debugger displaying stack-buffer-underflow error in example 1.](media/stack-buffer-underflow-example-1.png)
+:::image type="content" source="media/stack-buffer-underflow-example-1.png" alt-text="Screenshot of debugger displaying stack-buffer-underflow error in example 1.":::
 
 ## Example - stack underflow on thread
 
@@ -74,7 +74,7 @@ devenv /debugexe example2.exe
 
 ### Resulting error  - stack underflow on thread
 
-![Screenshot of debugger displaying stack-buffer-underflow error in example 2.](media/stack-buffer-underflow-example-2.png)
+:::image type="content" source="media/stack-buffer-underflow-example-2.png" alt-text="Screenshot of debugger displaying stack-buffer-underflow error in example 2.":::
 
 ## See also
 

docs/sanitizers/error-stack-use-after-return.md

@@ -49,7 +49,7 @@ devenv /debugexe example1.exe
 
 ### Resulting error - Simple C
 
-![Screenshot of debugger displaying stack-use-after-return error in example 1.](media/stack-use-after-return-example-1.png)
+:::image type="content" source="media/stack-use-after-return-example-1.png" alt-text="Screenshot of debugger displaying stack-use-after-return error in example 1.":::
 
 ## Example - C++ and templates
 
@@ -105,7 +105,7 @@ devenv /debugexe example2.exe 1
 
 ### Resulting error - C++ and templates
 
-![Screenshot of debugger displaying stack-use-after-return error in example 2.](media/stack-use-after-return-example-2.png)
+:::image type="content" source="media/stack-use-after-return-example-2.png" alt-text="Screenshot of debugger displaying stack-use-after-return error in example 2.":::
 
 ## See also