11/3/2021 AM Publish (#3877)

* draft

* updates

* draft content

* Change incorrect link for logical AND

This commit changes the link for logical AND from incorrectly linking to the bitwise AND to the correct logical AND.

* draft

* acrolinx and add to toc

* rename existing file back to original filename

* tech review

* fix code sample (#3676)

* fix code sample

* acrolinx

Co-authored-by: TylerMSFT <[email protected]>

* Update fsanitize.md

* Add mention in asan-building and add fsanitize-coverage options.

* Expand /fsanitize=fuzzer description. Unify table format used on page.

* Reference fsanitize-coverage.md in toc + full option lists.

* Fix warnings

* every relevant edge

* Add OneFuzz mention

* Fix mistaken deletion in chrono.md

* Fpcontract docs (#3691)

* Update fp-specify-floating-point-behavior.md

Add details on /fp:contract flag

* Update float-control.md

Update float_control pragma behavior with respect to contractions.

* small update

* Update fenv-access.md

* Update fp-contract.md

* Update predefined-macros.md

* fix typo and PR comments

* leave definition of contractions

* Add /fp:contract to the main list

* fix line break

* Add link to fp:contract

* Add reference to fp:contract

* Call out changes by compiler version.

Co-authored-by: [email protected] <[email protected]>

* Edit pass for i18n, grammar, and style

* Respond to feedback

* Add LibFuzzer link, consistency fixes

* add new classes: ambiguous_local_time & nonexistent_local_time

* acrolinx

* fix links

* finish descriptions

* fix more links

* smoothing out

* proofing

* add some better linking

* tune description

* update descriptions

* needed to update local-info-struct.md to reflect changes to descriptions for nonexistent and ambiguous

* add chrono functions

* rounding out duration links

* Add documentation for IntelliSense linter for C++ (#3821)

* Add first draft of linter check documentation

* WIP overview.

Signed-off-by: Kyle Reed <[email protected]>

* Update toc. First draft of the linter overview.

* Add screenshots, move files, code samples are stand-alone.

Signed-off-by: Kyle Reed <[email protected]>

* Style and Acrolinx grammar checker pass

* Add missing Options cues for checks

* Update to use latest option names

Co-authored-by: [email protected] <[email protected]>

* connecting duration up to it's non-member pieces and doing some general updates

* fix links

* cleanup

* Split out VS2019 content for linter (#3824)

* Update working-with-project-properties.md

* cleanup

* cleanup

* cleanup

* cleanup

* cleanup

* cleanup

* cleanup

* fix function signature

* fix line ending

* remove duplicate

* Address /profile issues per Paddy McD (#3834)

* Fixed documentation that destroy dialogs

* Update void-cpp for cpp-docs 3441

Reported in MicrosoftDocs/cpp-docs/issues/3441
Clarify kinds of class member where you can't use `void*`.
Fix styles.
Acrolinx a few things.

* More clarity on void pointers to members

* zoned_traits (#3831)

* add zoned_traits

* draft clock_cast and clock_time_conversion

* first draft

* draft

* draft

* fix heading

* cleanup

* add tzdb and tzdb-list

* draft

* draft

* pull examples

* draft cleanup

* acrolinx

* draft cleanup

* draft cleanup

* incorp tech review

* tech review

* cleanup

* cleanup

* acrolinx

* fix casing

* add example descriptions

* wording

* last adjustments

* wording

Co-authored-by: TylerMSFT <[email protected]>

* Update 16.1 conformance per J Emmett

* Update docs/error-messages/compiler-errors-2/compiler-error-c2666.md

* draft

* acrolinx, links

* links

* Fix typo in page title

* acrolinx

* fix link

* Fix TOC schema before VS2022 changes

* cleanup the port

* add additional info

* Address 3449 typo in /analyze

* update see also

* Address 3462 add C5033 warning

* Include link update

* Typo

* Add TOC entry

* Update how-to-marshal-callbacks-and-delegates-by-using-cpp-interop.md

typo: underlaying -> underlying

* Fix typo in toc for tzdb_list

* fix github issue #3469 (#3852)

Co-authored-by: TylerMSFT <[email protected]>

* remove constexpr, prevent machine translation of code elements, and bring closer to current doc style (#3854)

* remove constexpr

* add remark

* acrolinx

* update casing

* cleanup

Co-authored-by: TylerMSFT <[email protected]>

* VS2022 update for what's new content

* Acrolinx update

* Fix validation, links, typos

* Revert a styling quirk on headers

* Validation error fix

* Acrolinx and validation fixes

* Conformance fix updates

* Adding missing intrinsic.

* Fix intrinsic signature.

* Fix wrong argument type.

* Add headers, requirements

* VS2022 features, C17, walkthroughs (#3863)

* VS2022 features, C17, walkthroughs

* fix indentation to correct list step numbering

* fix indentation to correct list step numbering

* replace numbers with bold headings

Co-authored-by: Beth Harvey <[email protected]>

* tech review feedback

* cleanup

* Frontrun bulk fixes for VS2022

* Fixes #3484

* Docs/corob/cpp docs 3481 d8049 (#3865)

* Add D8049 error message

* Acrolinx tweak

* Update toc.yml

fix apparent typo in TOC

Co-authored-by: Jeff Borsecnik <[email protected]>

* More VS2022 non-bulk fixes. (#3867)

* Bulk update VS2022 content (#3860)

* Bulk fix to update msvc-160 and msvc-170

* Fix stray moniker tags

* incorp review

* update wording around closing the folder

* typos

* fix typo introduced while fixing typos...

* update formatting

* update steps and formatting

* Update working-with-resource-files.md

* Update symbols-resource-identifiers.md

* Update CMake landing page (#3864)

* intro, installation, configure

* config notifications

* IDE integration

* Building CMake projects

* Debugging CMake projects

* Open an existing cache

* Edit CMakeLists.txt files

* Configure IntelliSense

* Troubleshooting, repro from CLI

* Switch 17/19 CLI sections

* edits

* Fix code block

* more edits

* move images from docs/media to docs/build/media

* Address feedback

* Fix link style

* Final edits

* fix spelling per Acrolinx

Co-authored-by: Beth Harvey <[email protected]>

* Broken link fixed

* De-emphasize codeplex archive

* Add gray border (#3876)

* Correct or remove links: validation issues

Co-authored-by: Colin Robertson <[email protected]>
Co-authored-by: TylerMSFT <[email protected]>
Co-authored-by: Weston McNamara <[email protected]>
Co-authored-by: Tyler Whitney <[email protected]>
Co-authored-by: Steve Wishnousky <[email protected]>
Co-authored-by: Gautham Beeraka <[email protected]>
Co-authored-by: Kyle Reed <[email protected]>
Co-authored-by: Chai Wei Jie <[email protected]>
Co-authored-by: opbld15 <[email protected]>
Co-authored-by: PRMerger19 <[email protected]>
Co-authored-by: Laura Brenner <[email protected]>
Co-authored-by: Courtney Wales <[email protected]>
Co-authored-by: Andrea Courtright <[email protected]>
Co-authored-by: PRMerger15 <[email protected]>
Co-authored-by: opbld16 <[email protected]>
Co-authored-by: PRMerger8 <[email protected]>
Co-authored-by: Anju Del Moral Gonzalez <[email protected]>
Co-authored-by: opbld17 <[email protected]>
Co-authored-by: Miya Natsuhara <[email protected]>
Co-authored-by: Kristine Toliver <[email protected]>
Co-authored-by: PRMerger7 <[email protected]>
Co-authored-by: Avraham <[email protected]>
Co-authored-by: Paula Miller <[email protected]>
Co-authored-by: Jose Rivero <[email protected]>
Co-authored-by: Beth Harvey <[email protected]>
Co-authored-by: PRMerger5 <[email protected]>
Co-authored-by: Red Team Rover <[email protected]>
Co-authored-by: Jeff Borsecnik <[email protected]>
Co-authored-by: mohammad-ghasemi-2549 <[email protected]>
Co-authored-by: Erika <[email protected]>
Co-authored-by: Atik Mapari (Lionbridge Technologies Inc) <[email protected]>
Co-authored-by: PRMerger Service account 2 <[email protected]>

Author: 33 people

docs/build/cmake-presets-json-reference.md

@@ -16,7 +16,7 @@ CMake supports two files, *`CMakePresets.json`* and *`CMakeUserPresets.json`*, t
 
 For more information about how to use *`CMakePresets.json`* in Visual Studio, see [Configure and build with CMake Presets in Visual Studio](cmake-presets-vs.md)
 
-For more information about how to use *`CMakePresets.json`* in Visual Studio Code, see [Configure and build with CMake Presets in VS Code](https://github.com/microsoft/vscode-cmake-tools/blob/develop/docs/cmake-presets.md)
+For more information about how to use *`CMakePresets.json`* in Visual Studio Code, see [Configure and build with CMake Presets in VS Code](https://github.com/microsoft/vscode-cmake-tools/blob/main/docs/cmake-presets.md)
 
 ## Visual Studio Settings vendor map
 

docs/build/cmake-presets-vs.md

@@ -15,7 +15,7 @@ This article contains information about *`CMakePresets.json`* integration with V
 
 - For more information about the format of *`CMakePresets.json`*, see the official [CMake documentation](https://cmake.org/cmake/help/latest/manual/cmake-presets.7.html#id1).
 - For more information about the Microsoft vendor maps and macro expansion, see [`CMakePresets.json` and `CMakeUserPresets.json` Microsoft vendor maps](cmake-presets-json-reference.md).
-- For more information about how to use *`CMakePresets.json`* in Visual Studio Code, see [Configure and build with CMake Presets](https://github.com/microsoft/vscode-cmake-tools/tree/develop/docs/cmake-presets.md).
+- For more information about how to use *`CMakePresets.json`* in Visual Studio Code, see [Configure and build with CMake Presets](https://github.com/microsoft/vscode-cmake-tools/blob/main/docs/cmake-presets.md).
 
 We recommend *`CMakePresets.json`* as an alternative to *`CMakeSettings.json`*. Visual Studio will never read 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).
 
@@ -446,7 +446,7 @@ cmake --build --preset <buildPreset-name>
 
 ## Example *`CMakePresets.json`* file
 
-The *`CMakePresets.json`* file in [box2d-lite](https://github.com/esweet431/box2d-lite/blob/main/CMakePresets.json) contains examples of Configure Presets, Build Presets, and Test Presets.
+The *`CMakePresets.json`* file in [box2d-lite](https://github.com/esweet431/box2d-lite/blob/vs-launch/CMakePresets.json) contains examples of Configure Presets, Build Presets, and Test Presets.
 
 ## Next steps
 

docs/build/media/cmake-find-all-refs.png

@@ -7,7 +7,7 @@ helpviewer_keywords: ["/fsanitize-coverage [C++]", "sanitizer compiler option [C
 ---
 # `/fsanitize-coverage` (Configure sanitizer coverage)
 
-The **`/fsanitize-coverage`** compiler options instruct the compiler to add various kinds of instrumentation points where user-defined functions are called. These options are useful for fuzzing scenarios that use **`/fsanitize=fuzzer`**, like OneFuzz. For more information, see the [OneFuzz documentation](https://www.microsoft.com/en-us/research/project/project-onefuzz/) and [OneFuzz GitHub project](https://github.com/microsoft/onefuzz).
+The **`/fsanitize-coverage`** compiler options instruct the compiler to add various kinds of instrumentation points where user-defined functions are called. These options are useful for fuzzing scenarios that use **`/fsanitize=fuzzer`**, like OneFuzz. For more information, see the [OneFuzz documentation](https://www.microsoft.com/research/project/project-onefuzz/) and [OneFuzz GitHub project](https://github.com/microsoft/onefuzz).
 
 ## Syntax
 

docs/build/media/start-window.png

@@ -20,7 +20,7 @@ Use the **`/fsanitize`** compiler options to enable sanitizers.
 
 The **`/fsanitize=address`** compiler option enables [AddressSanitizer](../../sanitizers/asan.md), a powerful compiler and runtime technology to uncover [hard-to-find bugs](../../sanitizers/asan.md#error-types). Support for the **`/fsanitize=address`** option is available starting in Visual Studio 2019 version 16.9.
 
-The **`/fsanitize=fuzzer`** compiler option enables experimental support for [LibFuzzer](https://releases.llvm.org/3.8.0/docs/LibFuzzer.html). LibFuzzer is a coverage-guided fuzzing library that can be used to find bugs and crashes caused by user-provided input. We recommended you use **`/fsanitize=address`** with LibFuzzer. This option is useful for fuzzing tools such as OneFuzz. For more information, see the [OneFuzz documentation](https://www.microsoft.com/en-us/research/project/project-onefuzz/) and [OneFuzz GitHub project](https://github.com/microsoft/onefuzz). Support for the **`/fsanitize=fuzzer`** option is available starting in Visual Studio 2022 version 17.0.
+The **`/fsanitize=fuzzer`** compiler option enables experimental support for [LibFuzzer](https://releases.llvm.org/3.8.0/docs/LibFuzzer.html). LibFuzzer is a coverage-guided fuzzing library that can be used to find bugs and crashes caused by user-provided input. We recommended you use **`/fsanitize=address`** with LibFuzzer. This option is useful for fuzzing tools such as OneFuzz. For more information, see the [OneFuzz documentation](https://www.microsoft.com/research/project/project-onefuzz/) and [OneFuzz GitHub project](https://github.com/microsoft/onefuzz). Support for the **`/fsanitize=fuzzer`** option is available starting in Visual Studio 2022 version 17.0.
 
 The **`/fsanitize`** option doesn't allow comma-separated syntax, for example: **`/fsanitize=address,fuzzer`**. These options must be specified individually.
 

docs/build/reference/fsanitize-coverage.md

@@ -96,7 +96,7 @@ There are several ways to specify the Spectre-mitigated libraries to the build c
 
 ### Additional information
 
-For more information, see the official [Microsoft Security Advisory ADV180002, Guidance to mitigate speculative execution side-channel vulnerabilities](https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/ADV180002). Guidance is also available from Intel, [Speculative Execution Side Channel Mitigations](https://software.intel.com/sites/default/files/managed/c5/63/336996-Speculative-Execution-Side-Channel-Mitigations.pdf), and ARM, [Cache Speculation Side-channels](https://developer.arm.com/-/media/Files/pdf/Cache_Speculation_Side-channels.pdf).
+For more information, see the official [Microsoft Security Advisory ADV180002, Guidance to mitigate speculative execution side-channel vulnerabilities](https://msrc.microsoft.com/update-guide/vulnerability/ADV180002). Guidance is also available from Intel, [Speculative Execution Side Channel Mitigations](https://software.intel.com/sites/default/files/managed/c5/63/336996-Speculative-Execution-Side-Channel-Mitigations.pdf), and ARM, [Cache Speculation Side-channels](https://developer.arm.com/-/media/Files/pdf/Cache_Speculation_Side-channels.pdf).
 
 For a Windows-specific overview of Spectre and Meltdown mitigations, see [Understanding the performance impact of Spectre and Meltdown mitigations on Windows Systems](https://www.microsoft.com/security/blog/2018/01/09/understanding-the-performance-impact-of-spectre-and-meltdown-mitigations-on-windows-systems/).
 

docs/build/reference/fsanitize.md

@@ -73,7 +73,7 @@ int main()
 
 Compile with [`/std:c11`](../build/reference/std-specify-language-standard-version.md).
 
-Windows SDK 10.0.20348.0 (version 2104) or later. See [Windows SDK](https://developer.microsoft.com/windows/downloads/windows-sdk/) to download the latest SDK. For instructions to install and use the SDK for C11 and C17 development, see [Install C11 and C17 support in Visual Studio](../overview/install-c17-support.md).
+Windows SDK 10.0.20348.0 (version 2104) or later. For more information on installing the Windows SDK for C11 and C17 development, see [Install C11 and C17 support in Visual Studio](../overview/install-c17-support.md).
 
 ## See also
 

docs/build/reference/qspectre.md

@@ -57,4 +57,4 @@ void f( int n )
 
 ## See also
 
-[C++ Bitwise Operators](https://www.microsoft.com/download/details.aspx?id=55979)
+[Bitwise AND operator: `&`](../cpp/bitwise-and-operator-amp.md)

docs/c-language/static-assert-c.md

@@ -14,8 +14,6 @@ The *command line* command formed from input in the **Property Pages** dialog bo
 
 Possible reasons for this error include:
 
-- Your project depends on ATL Server. Beginning in Visual Studio 2008, ATL Server is no longer included as part of Visual Studio, but has been released as a shared-source project at CodePlex. To download the ATL Server source code and tools, go to [ATL Server Library and Tools](https://archive.codeplex.com/?p=atlserver).
-
 - Low system resources. Close some applications to resolve this.
 
 - Insufficient security privileges. Verify that you have sufficient security privileges.
@@ -24,6 +22,8 @@ Possible reasons for this error include:
 
 - For makefile projects, you are missing a command to run on either **Build Command Line** or **Rebuild Command Line**.
 
+- Your project depends on ATL Server. Beginning in Visual Studio 2008, ATL Server is no longer included as part of Visual Studio.
+
 ## See also
 
 [Project Build Errors and Warnings (PRJxxxx)](../../error-messages/tool-errors/project-build-errors-and-warnings-prjxxxx.md)

docs/code-quality/c6236.md

@@ -1,7 +1,7 @@
 ---
 description: "Learn more about: Upgrading an Existing ActiveX Control"
 title: "Upgrading an Existing ActiveX Control"
-ms.date: "09/12/2018"
+ms.date: 11/03/2021
 helpviewer_keywords: ["ActiveX controls [MFC], Internet", "LPK files for Internet controls", "safe for scripting and initialization (controls)", "OLE controls [MFC], upgrading to ActiveX", "CAB files, for ActiveX controls", "Internet applications [MFC], ActiveX controls", "Internet applications [MFC], packaging code for download", "upgrading ActiveX controls", "licensing ActiveX controls"]
 ms.assetid: 4d12ddfa-b491-4f9f-a0b7-b51458e05651
 ---
@@ -10,7 +10,7 @@ ms.assetid: 4d12ddfa-b491-4f9f-a0b7-b51458e05651
 Existing ActiveX controls (formerly OLE controls) can be used on the Internet without modification. However, you may want to modify controls to improve their performance.
 
 > [!IMPORTANT]
-> ActiveX is a legacy technology that should not be used for new development. For more information about modern technologies that supersede ActiveX, see [ActiveX Controls](activex-controls.md).
+> ActiveX is a legacy technology that should not be used for new development. For more information about modern technologies that supersede ActiveX, see [ActiveX Controls](activex-controls.md). Support for ActiveX controls was deprecated in later versions of Internet Explorer, and is not supported by modern browsers. Microsoft no longer supplies web-accessible ActiveX components.
 
 When using your control on a Web page, there are additional considerations. The .ocx file and all supporting files must be on the target machine or be downloaded across the Internet. This makes code size and download time an important consideration. Downloads can be packaged in a signed .cab file. You can mark your control as safe for scripting, and as safe for initializing.
 
@@ -41,7 +41,7 @@ ActiveX controls are embedded in Web pages using the `<OBJECT>` tag. The `CODEBA
 ### Using the CODEBASE Tag with an OCX File
 
 ```
-CODEBASE="http://example.microsoft.com/mycontrol.ocx#version=4,
+CODEBASE="http://example.contoso.com/mycontrol.ocx#version=4,
     70,
     0,
     1086"
@@ -52,15 +52,15 @@ This solution downloads only the control's .ocx file, and requires any supportin
 ### Using the CODEBASE Tag with an INF File
 
 ```
-CODEBASE="http://example.microsoft.com/trustme.inf"
+CODEBASE="http://example.contoso.com/trustme.inf"
 ```
 
 An .inf file will control the installation of an .ocx and its supporting files. This method is not recommended because it is not possible to sign an .inf file (see [Signing Code](#_core_signing_code) for pointers on code signing).
 
 ### Using the CODEBASE Tag with a CAB File
 
 ```
-CODEBASE="http://example.microsoft.com/acontrol.cab#version=1,
+CODEBASE="http://example.contoso.com/acontrol.cab#version=1,
     2,
     0,
     0"
@@ -78,12 +78,12 @@ For details on how to create a CAB file, see [Creating a CAB File](/windows/win3
 
 ### The INF File
 
-The following example, spindial.inf, lists the supporting files and the version information needed for the MFC Spindial control. Notice the location for the MFC DLLs is a Microsoft Web site. The mfc42.cab is provided and signed by Microsoft.
+The following example, spindial.inf, lists the supporting files and the version information needed for the MFC Spindial control. The mfc42.cab is provided and signed by Microsoft.
 
 ```
 Contents of spindial.inf:
 [mfc42installer]
-file-win32-x86=http://activex.microsoft.com/controls/vc/mfc42.cab
+file-win32-x86=http://example.contoso.com/controls/vc/mfc42.cab
 [Olepro32.dll] - FileVersion=5,
     0,
     4261,
@@ -105,7 +105,7 @@ The following example illustrates using the `<OBJECT>` tag to package the MFC Sp
 ```
 <OBJECT ID="Spindial1" WIDTH=100 HEIGHT=51
     CLASSID="CLSID:06889605-B8D0-101A-91F1-00608CEAD5B3"
-    CODEBASE="http://example.microsoft.com/spindial.cab#Version=1,0,0,001">
+    CODEBASE="http://example.contoso.com/spindial.cab#Version=1,0,0,001">
 <PARAM NAME="_Version" VALUE="65536">
 <PARAM NAME="_ExtentX" VALUE="2646">
 <PARAM NAME="_ExtentY" VALUE="1323">

docs/error-messages/tool-errors/project-build-error-prj0003.md

@@ -15,8 +15,6 @@ Samples for Visual Studio C++ are available on the web. Microsoft has produced m
 
 - [Windows Dev Center code samples](https://developer.microsoft.com/windows/samples)
 
-- [CodePlex sample archive](https://archive.codeplex.com/)
-
 - [ADO code samples](/office/client-developer/access/desktop-database-reference/ado-code-examples-in-microsoft-visual-c)
 
 - [Windows Hardware development samples](/samples/browse/?products=windows-wdk)

docs/mfc/upgrading-an-existing-activex-control.md

@@ -87,7 +87,7 @@ For more information on open issues and available workarounds for C++ in Visual
 
 ## Feedback and suggestions
 
-We'd love to hear from you! You can [Report a Problem or Suggest a Feature](/visualstudio/ide/visualstudio/ide/how-to-report-a-problem-with-visual-studio) by using the Send Feedback icon in the upper right-hand corner of either the installer or the Visual Studio IDE, or from **Help** > **Send Feedback**. You can track your issues by using [Visual Studio Developer Community](https://developercommunity.visualstudio.com/), where you add comments or find solutions. You can also get free installation help through our [Live Chat support](https://visualstudio.microsoft.com/vs/support/#talktous).
+We'd love to hear from you! You can [Report a Problem or Suggest a Feature](/visualstudio/ide/how-to-report-a-problem-with-visual-studio) by using the Send Feedback icon in the upper right-hand corner of either the installer or the Visual Studio IDE, or from **Help** > **Send Feedback**. You can track your issues by using [Visual Studio Developer Community](https://developercommunity.visualstudio.com/), where you add comments or find solutions. You can also get free installation help through our [Live Chat support](https://visualstudio.microsoft.com/vs/support/#talktous).
 
 ## Blogs