Skip to content

Commit 1b69bc2

Browse files
authored
Merge pull request #5982 from MicrosoftDocs/main
6/25/2025 AM Publish
2 parents b6aaa0c + 5efa224 commit 1b69bc2

File tree

115 files changed

+451
-520
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

115 files changed

+451
-520
lines changed

.openpublishing.redirection.json

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -21,7 +21,7 @@
2121
"redirect_document_id": true
2222
},
2323
{
24-
"source_path": "docs/supported-platforms-visual-cpp.md.md",
24+
"source_path": "docs/supported-platforms-visual-cpp.md",
2525
"redirect_url": "/cpp/overview/supported-platforms-visual-cpp",
2626
"redirect_document_id": true
2727
},
@@ -7436,7 +7436,7 @@
74367436
"redirect_document_id": false
74377437
},
74387438
{
7439-
"source_path": "docs/dotnet/how-to-enumerate-data-types-in-assemblies-using-reflection-cpp-cli.md.md",
7439+
"source_path": "docs/dotnet/how-to-enumerate-data-types-in-assemblies-using-reflection-cpp-cli.md",
74407440
"redirect_url": "/cpp/dotnet/reflection-cpp-cli#enumerate",
74417441
"redirect_document_id": false
74427442
},
@@ -13752,12 +13752,12 @@
1375213752
},
1375313753
{
1375413754
"source_path": "docs/c-runtime-library/operator-delete-crt.md",
13755-
"redirect_url": "docs/c-runtime-library/delete-operator-crt",
13755+
"redirect_url": "/cpp/c-runtime-library/delete-operator-crt",
1375613756
"redirect_document_id": false
1375713757
},
1375813758
{
1375913759
"source_path": "docs/c-runtime-library/operator-new-crt.md",
13760-
"redirect_url": "docs/c-runtime-library/new-operator-crt",
13760+
"redirect_url": "/cpp/c-runtime-library/new-operator-crt",
1376113761
"redirect_document_id": false
1376213762
},
1376313763
{
Lines changed: 20 additions & 24 deletions
Original file line numberDiff line numberDiff line change
@@ -1,59 +1,55 @@
11
---
2-
description: "Learn more about: Adding Connection Points to an Object"
32
title: "Adding Connection Points to an Object"
4-
ms.date: "11/04/2016"
3+
description: "Learn more about: Adding Connection Points to an Object"
4+
ms.date: 11/04/2016
55
helpviewer_keywords: ["connection points [C++], adding to ATL objects", "Implement Connection Point ATL wizard"]
6-
ms.assetid: 843531be-4a36-4db0-9d54-e029b1a72a8b
76
ms.topic: how-to
87
---
98
# Adding Connection Points to an Object
109

11-
The [ATL Tutorial](../atl/active-template-library-atl-tutorial.md) demonstrates how to create a control with support for connection points, how to add events, and then how to implement the connection point. ATL implements connection points with the [IConnectionPointImpl](../atl/reference/iconnectionpointimpl-class.md) class.
10+
The [ATL Tutorial](active-template-library-atl-tutorial.md) demonstrates how to create a control with support for connection points, how to add events, and then how to implement the connection point. ATL implements connection points with the [`IConnectionPointImpl`](reference/iconnectionpointimpl-class.md) class.
1211

1312
To implement a connection point, you have two choices:
1413

1514
- Implement your own outgoing event source, by adding a connection point to the control or object.
16-
1715
- Reuse a connection point interface defined in another type library.
1816

19-
In either case, the Implement Connection Point Wizard uses a type library to do its work.
17+
In either case, the **Implement Connection Point Wizard** uses a type library to do its work.
2018

21-
### To add a connection point to a control or object
19+
### Add a connection point to a control or object
2220

23-
1. Define a dispinterface in the library block of the .idl file. If you enabled support for connection points when you created the control with the ATL Control Wizard, the dispinterface will already be created. If you did not enable support for connection points when you created the control, you must manually add a dispinterface to the .idl file. The following is an example of a dispinterface. Outgoing interfaces are not required to be dispatch interfaces but many scripting languages such as VBScript and JScript require this, so this example uses two dispinterfaces:
21+
1. Define a dispinterface in the library block of the `.idl` file. If you enabled support for connection points when you created the control with the **ATL Control Wizard**, the dispinterface will already be created. If you did not enable support for connection points when you created the control, you must manually add a dispinterface to the `.idl` file. The following is an example of a dispinterface. Outgoing interfaces are not required to be dispatch interfaces but many scripting languages such as VBScript and JScript require this, so this example uses two dispinterfaces:
2422

25-
[!code-cpp[NVC_ATL_Windowing#81](../atl/codesnippet/cpp/adding-connection-points-to-an-object_1.idl)]
23+
[!code-cpp[NVC_ATL_Windowing#81](codesnippet/cpp/adding-connection-points-to-an-object_1.idl)]
2624

27-
Use either the uuidgen.exe or guidgen.exe utility to generate a GUID.
25+
Use either the `uuidgen.exe` or `guidgen.exe` utility to generate a GUID.
2826

29-
2. Add the dispinterface as the `[default,source]` interface in the coclass for the object in the project's .idl file. Again, if you enabled support for connection points when you created the control, the ATL Control Wizard will create the `[default,source`] entry. To manually add this entry, add the line in bold:
27+
2. Add the dispinterface as the `[default,source]` interface in the coclass for the object in the project's `.idl` file. Again, if you enabled support for connection points when you created the control, the ATL Control Wizard will create the `[default,source]` entry. To manually add this entry, add the line in bold:
3028

31-
[!code-cpp[NVC_ATL_Windowing#82](../atl/codesnippet/cpp/adding-connection-points-to-an-object_2.idl)]
29+
[!code-cpp[NVC_ATL_Windowing#82](codesnippet/cpp/adding-connection-points-to-an-object_2.idl)]
3230

33-
See the .idl file in the [Circ](../overview/visual-cpp-samples.md) ATL sample for an example.
31+
See the `.idl` file in the [Circ](../overview/visual-cpp-samples.md) ATL sample for an example.
3432

35-
3. Use Class View to add methods and properties to the event interface. Right-click the class in Class View, point to **Add** on the shortcut menu, and click **Add Connection Point**.
33+
3. Use **Class View** to add methods and properties to the event interface. Right-click the class in **Class View**, point to **Add** on the shortcut menu, and select **Add Connection Point**.
3634

37-
4. In the **Source Interfaces** list box of the Implement Connection Point Wizard, select **Project's interfaces**. If you choose an interface for your control and press **OK**, you will:
35+
4. In the **Source Interfaces** list box of the **Implement Connection Point Wizard**, select **Project's interfaces**. If you choose an interface for your control and select **OK**, you:
3836

3937
- Generate a header file with an event proxy class that implements the code that will make the outgoing calls for the event.
40-
4138
- Add an entry to the connection point map.
4239

43-
You will also see a list of all of the type libraries on your computer. You should only use one of these other type libraries to define your connection point if you want to implement the exact same outgoing interface found in another type library.
44-
45-
### To reuse a connection point interface defined in another type library
40+
You also see a list of all of the type libraries on your computer. Only use one of these other type libraries to define your connection point if you want to implement the exact same outgoing interface found in another type library.
4641

47-
1. In Class View, right-click a class that implements a **BEGIN_COM_MAP** macro, point to **Add** on the shortcut menu, and click **Add Connection Point**.
42+
### Reuse a connection point interface defined in another type library
4843

49-
2. In the Implement Connection Point Wizard, select a type library and an interface in the type library and click **Add**.
44+
1. In **Class View**, right-click a class that implements a `BEGIN_COM_MAP` macro, point at **Add** on the shortcut menu, and select **Add Connection Point**.
5045

51-
3. Edit the .idl file to either:
46+
2. In the **Implement Connection Point Wizard**, select a type library and an interface in the type library and select **Add**.
5247

53-
- Copy the dispinterface from the .idl file for the object whose event-source is being used.
48+
3. Edit the `.idl` file to either:
5449

50+
- Copy the dispinterface from the `.idl` file for the object whose event-source is being used.
5551
- Use the **importlib** instruction on that type library.
5652

5753
## See also
5854

59-
[Connection Point](../atl/atl-connection-points.md)
55+
[Connection Point](atl-connection-points.md)

docs/atl/reference/catltransactionmanager-class.md

Lines changed: 3 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,9 @@
11
---
2-
description: "Learn more about: CAtlTransactionManager Class"
32
title: "CAtlTransactionManager Class"
4-
ms.date: "11/04/2016"
3+
description: "Learn more about: CAtlTransactionManager Class"
4+
ms.date: 11/04/2016
55
f1_keywords: ["CAtlTransactionManager", "ATLTRANSACTIONMANAGER/ATL::CAtlTransactionManager", "ATLTRANSACTIONMANAGER/ATL::Close", "ATLTRANSACTIONMANAGER/ATL::Commit", "ATLTRANSACTIONMANAGER/ATL::Create", "ATLTRANSACTIONMANAGER/ATL::CreateFile", "ATLTRANSACTIONMANAGER/ATL::DeleteFile", "ATLTRANSACTIONMANAGER/ATL::FindFirstFile", "ATLTRANSACTIONMANAGER/ATL::GetFileAttributes", "ATLTRANSACTIONMANAGER/ATL::GetFileAttributesEx", "ATLTRANSACTIONMANAGER/ATL::GetHandle", "ATLTRANSACTIONMANAGER/ATL::IsFallback", "ATLTRANSACTIONMANAGER/ATL::MoveFile", "ATLTRANSACTIONMANAGER/ATL::RegCreateKeyEx", "ATLTRANSACTIONMANAGER/ATL::RegDeleteKey", "ATLTRANSACTIONMANAGER/ATL::RegOpenKeyEx", "ATLTRANSACTIONMANAGER/ATL::Rollback", "ATLTRANSACTIONMANAGER/ATL::SetFileAttributes", "ATLTRANSACTIONMANAGER/ATL::m_bFallback", "ATLTRANSACTIONMANAGER/ATL::m_hTransaction"]
66
helpviewer_keywords: ["CAtlTransactionManager class"]
7-
ms.assetid: b01732dc-1d16-4b42-bfac-b137fca2b740
87
---
98
# CAtlTransactionManager Class
109

@@ -66,7 +65,7 @@ class CAtlTransactionManager;
6665

6766
**Header:** atltransactionmanager.h
6867

69-
## <a name="dtor"></a> ~CAtlTransactionManager
68+
## <a name="dtor"></a> ~CAtlTransactionManager
7069

7170
CAtlTransactionManager destructor.
7271

docs/atl/reference/ccomdynamicunkarray-class.md

Lines changed: 3 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,9 @@
11
---
2-
description: "Learn more about: CComDynamicUnkArray Class"
32
title: "CComDynamicUnkArray Class"
4-
ms.date: "11/04/2016"
3+
description: "Learn more about: CComDynamicUnkArray Class"
4+
ms.date: 11/04/2016
55
f1_keywords: ["CComDynamicUnkArray", "ATLCOM/ATL::CComDynamicUnkArray", "ATLCOM/ATL::CComDynamicUnkArray::CComDynamicUnkArray", "ATLCOM/ATL::CComDynamicUnkArray::Add", "ATLCOM/ATL::CComDynamicUnkArray::begin", "ATLCOM/ATL::CComDynamicUnkArray::clear", "ATLCOM/ATL::CComDynamicUnkArray::end", "ATLCOM/ATL::CComDynamicUnkArray::GetAt", "ATLCOM/ATL::CComDynamicUnkArray::GetCookie", "ATLCOM/ATL::CComDynamicUnkArray::GetSize", "ATLCOM/ATL::CComDynamicUnkArray::GetUnknown", "ATLCOM/ATL::CComDynamicUnkArray::Remove"]
66
helpviewer_keywords: ["connection points [C++], managing", "CComDynamicUnkArray class"]
7-
ms.assetid: 202470d7-9a1b-498f-b96d-659d681acd65
87
---
98
# CComDynamicUnkArray Class
109

@@ -194,7 +193,7 @@ int GetSize() const;
194193

195194
The number of elements the array can store. `GetSize() == end() - begin()`.
196195

197-
## <a name="getunknown"></a> CComDynamicUnkArray::GetUnknown
196+
## <a name="getunknown"></a> CComDynamicUnkArray::GetUnknown
198197

199198
Call this method to get the `IUnknown` pointer associated with a given cookie.
200199

docs/build/cmake-presets-vs.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -19,7 +19,7 @@ This article contains information about *`CMakePresets.json`* integration with V
1919

2020
We recommend *`CMakePresets.json`* as an alternative to *`CMakeSettings.json`*. Visual Studio never reads from both *`CMakePresets.json`* and *`CMakeSettings.json`* at the same time. To enable or disable *`CMakePresets.json`* integration in Visual Studio, see [Enable `CMakePresets.json` in Visual Studio 2019](#enable-cmakepresets-json-integration).
2121

22-
## Supported CMake and *`CMakePresets.json`* versions
22+
## Supported CMake and *`CMakePresets.json`* versions
2323

2424
The supported *`CMakePresets.json`* and *`CMakeUserPresets.json`* schema versions depend on your version of Visual Studio:
2525
- Visual Studio 2019 version 16.10 and later support schema versions 2 and 3.
@@ -391,7 +391,7 @@ Instead, set the path to `vcpkg.cmake` by using the `VCPKG_ROOT` environment var
391391

392392
If you're already using a CMake toolchain file and want to enable vcpkg integration, see [Using multiple toolchain files](/vcpkg/users/buildsystems/cmake-integration#using-multiple-toolchain-files). Follow those instructions to use an external toolchain file with a project by using vcpkg.
393393

394-
## Variable substitution in *`launch.vs.json`* and *`tasks.vs.json`*
394+
## Variable substitution in *`launch.vs.json`* and *`tasks.vs.json`*
395395

396396
*`CMakePresets.json`* supports variable substitution in *`launch.vs.json`* and *`tasks.vs.json`*. Here are some considerations:
397397

docs/build/open-folder-projects-cpp.md

Lines changed: 3 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,9 +1,8 @@
11
---
2-
description: "Learn more about: Open Folder support for C++ build systems in Visual Studio"
32
title: "Open Folder support for C++ build systems in Visual Studio"
4-
ms.date: "12/02/2019"
3+
description: "Learn more about: Open Folder support for C++ build systems in Visual Studio"
4+
ms.date: 12/02/2019
55
helpviewer_keywords: ["Open Folder Projects in Visual Studio"]
6-
ms.assetid: abd1985e-3717-4338-9e80-869db5435175
76
ms.topic: how-to
87
---
98
# Open Folder support for C++ build systems in Visual Studio
@@ -106,7 +105,7 @@ If you add the MinGW-W64 configuration, the JSON looks this:
106105
}
107106
```
108107

109-
Note the `environments` block. It defines properties that behave like environment variables and are available not only in the *CppProperties.json* file, but also in the other configuration files *task.vs.json* and *launch.vs.json*. The `Mingw64` configuration inherits the `mingw_w64` environment, and uses its `INCLUDE` property to specify the value for `includePath`. You can add other paths to this array property as needed.`
108+
Note the `environments` block. It defines properties that behave like environment variables and are available not only in the *CppProperties.json* file, but also in the other configuration files *task.vs.json* and *launch.vs.json*. The `Mingw64` configuration inherits the `mingw_w64` environment, and uses its `INCLUDE` property to specify the value for `includePath`. You can add other paths to this array property as needed.
110109

111110
The `intelliSenseMode` property is set to a value appropriate for GCC. For more information on all these properties, see [CppProperties schema reference](cppproperties-schema-reference.md).
112111

docs/c-runtime-library/reference/asctime-s-wasctime-s.md

Lines changed: 3 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,14 +1,13 @@
11
---
2-
description: "Learn more about: asctime_s, _wasctime_s"
32
title: "asctime_s, _wasctime_s"
4-
ms.date: "4/2/2020"
3+
description: "Learn more about: asctime_s, _wasctime_s"
4+
ms.date: 4/2/2020
55
api_name: ["_wasctime_s", "asctime_s", "_o__wasctime_s", "_o_asctime_s"]
66
api_location: ["msvcrt.dll", "msvcr80.dll", "msvcr90.dll", "msvcr100.dll", "msvcr100_clr0400.dll", "msvcr110.dll", "msvcr110_clr0400.dll", "msvcr120.dll", "msvcr120_clr0400.dll", "ucrtbase.dll", "api-ms-win-crt-time-l1-1-0.dll"]
77
api_type: ["DLLExport"]
88
topic_type: ["apiref"]
99
f1_keywords: ["asctime_s", "_wasctime_s", "_tasctime_s"]
1010
helpviewer_keywords: ["tasctime_s function", "_tasctime_s function", "time structure conversion", "wasctime_s function", "time, converting", "_wasctime_s function", "asctime_s function"]
11-
ms.assetid: 17ad9b2b-a459-465d-976a-42822897688a
1211
---
1312
# `asctime_s`, `_wasctime_s`
1413

@@ -24,7 +23,7 @@ errno_t asctime_s(
2423
);
2524
errno_t _wasctime_s(
2625
wchar_t* buffer,
27-
size_t numberOfElements
26+
size_t numberOfElements,
2827
const struct tm *tmSource
2928
);
3029
template <size_t size>

docs/c-runtime-library/reference/crtsetdebugfillthreshold.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -60,7 +60,7 @@ Here's a list of the affected functions:
6060
- [`_strset_s`, `_strset_s_l`, `_wcsset_s`, `_wcsset_s_l`, `_mbsset_s`, `_mbsset_s_l`](strset-s-strset-s-l-wcsset-s-wcsset-s-l-mbsset-s-mbsset-s-l.md)
6161
- [`_strtime_s`, `_wstrtime_s`](strtime-s-wstrtime-s.md)
6262
- [`_strupr_s`, `_strupr_s_l`, `_mbsupr_s`, `_mbsupr_s_l`, `_wcsupr_s`, `_wcsupr_s_l`](strupr-s-strupr-s-l-mbsupr-s-mbsupr-s-l-wcsupr-s-wcsupr-s-l.md)
63-
- [`vsnprintf_s`, `_vsnprintf_s`, `_vsnprintf_s_l`, `_vsnwprintf_s`, _vsnwpr`intf_s_l](vsnprintf-s-vsnprintf-s-vsnprintf-s-l-vsnwprintf-s-vsnwprintf-s-l.md)
63+
- [`vsnprintf_s`, `_vsnprintf_s`, `_vsnprintf_s_l`, `_vsnwprintf_s`, `_vsnwprintf_s_l`](vsnprintf-s-vsnprintf-s-vsnprintf-s-l-vsnwprintf-s-vsnwprintf-s-l.md)
6464
6565
## Requirements
6666

docs/c-runtime-library/reference/itoa-s-itow-s.md

Lines changed: 3 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,16 +1,15 @@
11
---
2-
description: "Learn more about: _itoa_s, _ltoa_s, _ultoa_s, _i64toa_s, _ui64toa_s, _itow_s, _ltow_s, _ultow_s, _i64tow_s, _ui64tow_s"
32
title: "_itoa_s, _itow_s functions"
4-
ms.date: "4/2/2020"
3+
description: "Learn more about: _itoa_s, _ltoa_s, _ultoa_s, _i64toa_s, _ui64toa_s, _itow_s, _ltow_s, _ultow_s, _i64tow_s, _ui64tow_s"
4+
ms.date: 4/2/2020
55
api_name: ["_itoa_s", "_ltoa_s", "_ultoa_s", "_i64toa_s", "_ui64toa_s", "_itow_s", "_ltow_s", "_ultow_s", "_i64tow_s", "_ui64tow_s", "_o__i64toa_s", "_o__i64tow_s", "_o__itoa_s", "_o__itow_s", "_o__ltoa_s", "_o__ltow_s", "_o__ui64toa_s", "_o__ui64tow_s", "_o__ultoa_s", "_o__ultow_s"]
66
api_location: ["msvcrt.dll", "msvcr80.dll", "msvcr90.dll", "msvcr100.dll", "msvcr100_clr0400.dll", "msvcr110.dll", "msvcr110_clr0400.dll", "msvcr120.dll", "msvcr120_clr0400.dll", "ucrtbase.dll", "api-ms-win-crt-convert-l1-1-0.dll", "ntoskrnl.exe"]
77
api_type: ["DLLExport"]
88
topic_type: ["apiref"]
99
f1_keywords: ["_itoa_s", "_ltoa_s", "_ultoa_s", "_i64toa_s", "_ui64toa_s", "_itow_s", "_ltow_s", "_ultow_s", "_i64tow_s", "_ui64tow_s", "_itot_s", "_ltot_s", "_ultot_s", "_i64tot_s", "_ui64tot_s", "itoa_s", "ltoa_s", "ultoa_s", "i64toa_s", "ui64toa_s", "itow_s", "ltow_s", "ultow_s", "i64tow_s", "ui64tow_s", "itot_s", "ltot_s", "ultot_s", "i64tot_s", "ui64tot_s"]
1010
helpviewer_keywords: ["_ui64toa_s function", "_itow_s function", "_i64tow_s function", "_itot_s function", "converting integers", "itow_s function", "i64toa_s function", "_ui64tow_s function", "integers, converting", "_i64tot_s function", "itoa_s function", "_itoa_s function", "ui64toa_s function", "i64tow_s function", "converting numbers, to strings", "_ui64tot_s function", "_i64toa_s function"]
11-
ms.assetid: eb746581-bff3-48b5-a973-bfc0a4478ecf
1211
---
13-
# `_itoa_s`, `_ltoa_s`, `_ultoa_s`, `_i64toa_s`, `_ui64toa_s`, `_itow_s`, `_ltow_s`, `_ultow_s`, `_i64tow_s`, `_ui64tow_s`
12+
# `_itoa_s`, `_ltoa_s`, `_ultoa_s`, `_i64toa_s`, `_ui64toa_s`, `_itow_s`, `_ltow_s`, `_ultow_s`, `_i64tow_s`, `_ui64tow_s`
1413

1514
Converts an integer to a string. These functions are versions of the [`_itoa`, `_itow` functions](itoa-itow.md) with security enhancements as described in [Security features in the CRT](../security-features-in-the-crt.md).
1615

0 commit comments

Comments
 (0)