Merge pull request #4519 from MicrosoftDocs/main638175216022942982sync_temp

For protected CLA branch, push strategy should use PR and merge to target branch method to work around git push error

Author: learn-build-service-prod[bot]

docs/atl/reference/caxwindow-class.md

@@ -5,6 +5,12 @@ ms.date: "11/04/2016"
 f1_keywords: ["CAxWindow", "ATLWIN/ATL::CAxWindow", "ATLWIN/ATL::AttachControl", "ATLWIN/ATL::CreateControl", "ATLWIN/ATL::CreateControlEx", "ATLWIN/ATL::GetWndClassName", "ATLWIN/ATL::QueryControl", "ATLWIN/ATL::QueryHost", "ATLWIN/ATL::SetExternalDispatch", "ATLWIN/ATL::SetExternalUIHandler"]
 helpviewer_keywords: ["CAxWindow class", "ATL, hosting ActiveX controls"]
 ms.assetid: 85e79261-43e4-4770-bde0-1ff87f222b0f
+api_type:
+- DllExport
+api_location:
+- atlhost.dll
+api_name:
+- CAxWindow::CreateControlEx
 ---
 # CAxWindow Class
 

docs/preprocessor/predefined-macros.md

@@ -277,6 +277,9 @@ MSVC supports these additional predefined macros.
    | Visual Studio 2022 RTW (17.0) | 1930 |
    | Visual Studio 2022 version 17.1 | 1931 |
    | Visual Studio 2022 version 17.2 | 1932 |
+   | Visual Studio 2022 version 17.3 | 1933 |
+   | Visual Studio 2022 version 17.4 | 1934 |
+   | Visual Studio 2022 version 17.5 | 1935 |
 
    To test for compiler releases or updates in a given version of Visual Studio or after, use the `>=` operator. You can use it in a conditional directive to compare `_MSC_VER` against that known version. If you have several mutually exclusive versions to compare, order your comparisons in descending order of version number. For example, this code checks for compilers released in Visual Studio 2017 and later. Next, it checks for compilers released in or after Visual Studio 2015. Then it checks for all compilers released before Visual Studio 2015: