Skip to content

Commit 1d14830

Browse files
TylerMSFTTylerMSFT
authored andcommitted
fix image tags
1 parent 4459c96 commit 1d14830

File tree

4 files changed

+8
-9
lines changed

4 files changed

+8
-9
lines changed

docs/build/cmake-presets-vs.md

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -42,8 +42,7 @@ We recommend using at least CMake version 3.14 or later.
4242
4343
In some older versions of Visual Studio, **Tools** > **Options** > **CMake** > **General** only has a single option to enable *`CMakePresets.json`* integration:
4444

45-
:::image type="content" source="./media/enable-cmakepresets.png" alt-text="Screenshot of older Visual Studio enable CMakePresets.json checkbox which is labeled: Use C Make Presets .json to drive CMake configure, build, and test."
46-
:::image-end:::
45+
:::image type="content" source="./media/enable-cmakepresets.png" alt-text="Screenshot of older Visual Studio enable CMakePresets.json checkbox which is labeled: Use C Make Presets .json to drive CMake configure, build, and test.":::
4746

4847
The following table indicates when *`CMakePresets.json`* is used instead of *`CMakeSettings.json`* to drive CMake configuration and build in Visual Studio 2022 and Visual Studio 2019 version 16.10 and later. If no configuration file is present, default Configure Presets are used.
4948

docs/mfc/reference/creating-an-mfc-application.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
description: "Learn more about: Creating an MFC Application"
33
title: "Creating an MFC Application"
4-
ms.date: "08/28/2019"
4+
ms.date: 02/11/2023
55
helpviewer_keywords: ["applications [MFC]", "MFC, creating applications", "MFC applications"]
66
---
77
# Creating an MFC Application
@@ -33,7 +33,7 @@ The easiest way to create an MFC application is to use the MFC Application Wizar
3333

3434
For more information, see [Creating a forms-based MFC application](creating-a-forms-based-mfc-application.md).
3535

36-
:::image type="complex" source="media/mfc-app-wizard.png" alt-text="Screenshot of the MFC Application wizard in Visual Studios 2022.":::
36+
:::image type="complex" source="./media/mfc-app-wizard.png" alt-text="Screenshot of the MFC Application wizard in Visual Studios 2022.":::
3737
The dialog shows options for the application type which is set to single document. Application type options include tabbed documents, which is checked, and document/view architecture support, which is checked. There are other options for project style, resource language, and so on that are set to their default values.
3838
:::image-end
3939

docs/sanitizers/asan-runtime.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -74,7 +74,7 @@ Microsoft C/C++ (MSVC) uses a runtime based on the [Clang AddressSanitizer runti
7474
> [!NOTE]
7575
> The AddressSanitizer runtime option `halt_on_error` doesn't function the way you might expect. In both the Clang and the MSVC runtime libraries, many error types are considered **non-continuable**, including most memory corruption errors.
7676
77-
For more information, see the [Differences with Clang 12.0](./asan.md#differences) section.
77+
For more information, see the [Differences with Clang 12.0](asan.md#differences) section.
7878

7979
### MSVC-specific AddressSanitizer runtime options
8080

docs/sanitizers/asan.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -111,9 +111,9 @@ When you run the resulting *`main.exe`* at the command line, it creates the form
111111

112112
Consider the overlaid, red boxes that highlight seven key pieces of information:
113113

114-
:::image type="complex" source="media/asan-basic-global-overflow.png" alt-text="Screenshot of the debugger showing a basic global overflow error."
114+
:::image type="complex" source="media/asan-basic-global-overflow.png" alt-text="Screenshot of the debugger showing a basic global overflow error.":::
115115
There are seven red highlights identifying key pieces of information in the error report. They map to the numbered list that follows this screenshot. The numbered boxes highlight the following text: 1) global-buffer-overflow 2) WRITE of size 4 3) basic-global-overflow.cpp 7 4) to the right of global variable 'x' defined in 'basic-global-overflow.cpp:3:8' 5) of size 400 6) 00 00[f9]f9 f9 7) Box is in the shadow byte legend area and contains Global redzone: f9
116-
:::image-end
116+
:::image-end:::
117117

118118
### Red highlights, from top to bottom
119119

@@ -158,13 +158,13 @@ To enable AddressSanitizer for [a CMake project created to target Windows](../bu
158158

159159
This image is of `CMakePresets.json` after that change: ========= JTW THIS LOOKS BROKEN-UPDATE ==========
160160

161-
:::image type="content" source="media/asan-cmake-json.png" alt-text="Screenshot of the text editor view of CMakePresets.json.":::
161+
:::image type="content" source="./media/asan-cmake-json.png" alt-text="Screenshot of the text editor view of CMakePresets.json.":::
162162

163163
1. Enter **Ctrl+S** to save this JSON file, then enter **F5** to recompile and run under the debugger.
164164

165165
This screenshot captures the error from the CMake build.
166166

167-
:::image type="content" source="media/asan-cmake-error-f5.png" alt-text="Screenshot of the CMake build error message.":::
167+
:::image type="content" source="./media/asan-cmake-error-f5.png" alt-text="Screenshot of the CMake build error message.":::
168168

169169
## <a name="crash-dumps"></a> AddressSanitizer crash dumps
170170

0 commit comments

Comments
 (0)