From 715cfc074fd87f71b0a9ee3687a66a9c26ced407 Mon Sep 17 00:00:00 2001 From: Taojunshen Date: Sat, 30 Oct 2021 01:43:34 +0800 Subject: [PATCH] 10/29/2021 AM Publish (#3869) * 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 * 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: 3836425+corob-msft@users.noreply.github.com * 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 * Update toc. First draft of the linter overview. * Add screenshots, move files, code samples are stand-alone. Signed-off-by: Kyle Reed * Style and Acrolinx grammar checker pass * Add missing Options cues for checks * Update to use latest option names Co-authored-by: 3836425+corob-msft@users.noreply.github.com * 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 * Update 16.1 conformance per J Emmett * Update docs/error-messages/compiler-errors-2/compiler-error-c2666.md * Fix typo in page title * Fix TOC schema before VS2022 changes * Address 3449 typo in /analyze * 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 * 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 * 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 * Frontrun bulk fixes for VS2022 * 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 <36546697+jborsecnik@users.noreply.github.com> * More VS2022 non-bulk fixes. (#3867) * Bulk update VS2022 content (#3860) * Bulk fix to update msvc-160 and msvc-170 * Fix stray moniker tags Co-authored-by: Colin Robertson Co-authored-by: TylerMSFT Co-authored-by: Weston McNamara Co-authored-by: Tyler Whitney Co-authored-by: Steve Wishnousky Co-authored-by: Gautham Beeraka <58992211+Gautham-Beeraka1@users.noreply.github.com> Co-authored-by: Kyle Reed Co-authored-by: Chai Wei Jie Co-authored-by: opbld15 Co-authored-by: PRMerger19 Co-authored-by: Laura Brenner <90344170+laurabren@users.noreply.github.com> Co-authored-by: Courtney Wales <62625502+Court72@users.noreply.github.com> Co-authored-by: Andrea Courtright <74212614+v-andreaco@users.noreply.github.com> Co-authored-by: PRMerger15 Co-authored-by: opbld16 Co-authored-by: PRMerger8 Co-authored-by: Anju Del Moral Gonzalez Co-authored-by: opbld17 Co-authored-by: Miya Natsuhara <46756417+mnatsuhara@users.noreply.github.com> Co-authored-by: Kristine Toliver Co-authored-by: PRMerger7 Co-authored-by: Avraham Co-authored-by: Paula Miller Co-authored-by: Jose Rivero Co-authored-by: Beth Harvey Co-authored-by: PRMerger5 Co-authored-by: Jeff Borsecnik <36546697+jborsecnik@users.noreply.github.com> --- .../example-implementing-a-property-page.md | 2 +- docs/atl/implementing-property-pages.md | 2 +- ...ing-an-atl-active-server-page-component.md | 2 +- .../adding-an-atl-com-plus-1-0-component.md | 2 +- .../adding-an-atl-ole-db-consumer.md | 2 +- .../adding-an-atl-ole-db-provider.md | 2 +- ...atl-active-server-page-component-wizard.md | 2 +- .../atl-com-plus-1-0-component-wizard.md | 2 +- .../reference/atl-ole-db-consumer-wizard.md | 2 +- .../reference/atl-ole-db-provider-wizard.md | 2 +- .../atl/reference/atl-property-page-wizard.md | 2 +- ...s-1-0-atl-com-plus-1-0-component-wizard.md | 2 +- .../options-atl-property-page-wizard.md | 2 +- .../strings-atl-property-page-wizard.md | 2 +- .../get-started-with-cpp-build-insights.md | 4 +- .../c-event-data-types/cl-pass-data-struct.md | 2 +- .../event-collection-data-struct.md | 2 +- .../c-event-data-types/event-data-struct.md | 2 +- .../sdk/c-event-data-types/event-id-enum.md | 2 +- .../c-event-data-types/file-data-struct.md | 2 +- .../c-event-data-types/file-type-code-enum.md | 2 +- .../front-end-file-data-struct.md | 2 +- .../function-data-struct.md | 2 +- .../function-force-inlinee-data-struct.md | 2 +- .../invocation-data-struct.md | 2 +- .../invocation-version-data-struct.md | 2 +- .../c-event-data-types/msvc-tool-code-enum.md | 2 +- .../name-value-pair-data-struct.md | 2 +- .../symbol-name-data-struct.md | 2 +- .../template-instantiation-data-struct.md | 2 +- .../template-instantiation-kind-code-enum.md | 2 +- .../trace-info-data-struct.md | 2 +- .../translation-unit-pass-code-enum.md | 2 +- .../translation-unit-type-data.md | 2 +- .../translation-unit-type.md | 2 +- .../sdk/cpp-event-data-types/activity.md | 2 +- .../sdk/cpp-event-data-types/back-end-pass.md | 2 +- .../sdk/cpp-event-data-types/bottom-up.md | 2 +- .../sdk/cpp-event-data-types/c1-dll.md | 2 +- .../sdk/cpp-event-data-types/c2-dll.md | 2 +- .../cpp-event-data-types/code-generation.md | 2 +- .../sdk/cpp-event-data-types/command-line.md | 2 +- .../sdk/cpp-event-data-types/compiler-pass.md | 2 +- .../sdk/cpp-event-data-types/compiler.md | 2 +- .../environment-variable.md | 2 +- .../sdk/cpp-event-data-types/event-group.md | 2 +- .../sdk/cpp-event-data-types/event-stack.md | 2 +- .../sdk/cpp-event-data-types/event.md | 2 +- .../executable-image-output.md | 2 +- .../sdk/cpp-event-data-types/exp-output.md | 2 +- .../sdk/cpp-event-data-types/file-input.md | 2 +- .../sdk/cpp-event-data-types/file-output.md | 2 +- .../sdk/cpp-event-data-types/force-inlinee.md | 2 +- .../front-end-file-group.md | 2 +- .../cpp-event-data-types/front-end-file.md | 2 +- .../cpp-event-data-types/front-end-pass.md | 2 +- .../sdk/cpp-event-data-types/function.md | 2 +- .../sdk/cpp-event-data-types/header-unit.md | 2 +- .../cpp-event-data-types/imp-lib-output.md | 2 +- .../cpp-event-data-types/invocation-group.md | 2 +- .../sdk/cpp-event-data-types/invocation.md | 2 +- .../sdk/cpp-event-data-types/lib-output.md | 2 +- .../sdk/cpp-event-data-types/linker-group.md | 2 +- .../sdk/cpp-event-data-types/linker-pass.md | 2 +- .../sdk/cpp-event-data-types/linker.md | 2 +- .../sdk/cpp-event-data-types/ltcg.md | 2 +- .../sdk/cpp-event-data-types/module.md | 2 +- .../sdk/cpp-event-data-types/obj-output.md | 2 +- .../sdk/cpp-event-data-types/opt-icf.md | 2 +- .../sdk/cpp-event-data-types/opt-lbr.md | 2 +- .../sdk/cpp-event-data-types/opt-ref.md | 2 +- .../sdk/cpp-event-data-types/pass1.md | 2 +- .../sdk/cpp-event-data-types/pass2.md | 2 +- .../cpp-event-data-types/pre-ltcg-opt-ref.md | 2 +- .../precompiled-header.md | 2 +- .../sdk/cpp-event-data-types/raw-event.md | 2 +- .../sdk/cpp-event-data-types/simple-event.md | 2 +- .../sdk/cpp-event-data-types/symbol-name.md | 2 +- .../template-instantiation-group.md | 2 +- .../template-instantiation.md | 2 +- .../sdk/cpp-event-data-types/thread.md | 2 +- .../sdk/cpp-event-data-types/top-down.md | 2 +- .../sdk/cpp-event-data-types/trace-info.md | 2 +- .../translation-unit-type.md | 2 +- .../whole-program-analysis.md | 2 +- .../reference/sdk/event-table.md | 2 +- .../reference/sdk/functions/analyze-a.md | 2 +- .../reference/sdk/functions/analyze-w.md | 2 +- .../reference/sdk/functions/analyze.md | 2 +- .../reference/sdk/functions/inject-event.md | 2 +- .../functions/make-dynamic-analyzer-group.md | 2 +- .../functions/make-dynamic-relogger-group.md | 2 +- .../functions/make-static-analyzer-group.md | 2 +- .../functions/make-static-relogger-group.md | 2 +- .../match-event-in-member-function.md | 2 +- .../match-event-stack-in-member-function.md | 2 +- .../sdk/functions/match-event-stack.md | 2 +- .../reference/sdk/functions/match-event.md | 2 +- .../reference/sdk/functions/relog-a.md | 2 +- .../reference/sdk/functions/relog-w.md | 2 +- .../reference/sdk/functions/relog.md | 2 +- .../sdk/functions/start-tracing-session-a.md | 2 +- .../sdk/functions/start-tracing-session-w.md | 2 +- .../sdk/functions/start-tracing-session.md | 2 +- .../stop-and-analyze-tracing-session-a.md | 2 +- .../stop-and-analyze-tracing-session-w.md | 2 +- .../stop-and-analyze-tracing-session.md | 2 +- .../stop-and-relog-tracing-session-a.md | 2 +- .../stop-and-relog-tracing-session-w.md | 2 +- .../stop-and-relog-tracing-session.md | 2 +- .../sdk/functions/stop-tracing-session-a.md | 2 +- .../sdk/functions/stop-tracing-session-w.md | 2 +- .../sdk/functions/stop-tracing-session.md | 2 +- .../other-types/analysis-callbacks-struct.md | 2 +- .../analysis-control-enum-class.md | 2 +- .../other-types/analysis-descriptor-struct.md | 2 +- .../sdk/other-types/callback-code-enum.md | 2 +- .../sdk/other-types/ianalyzer-class.md | 2 +- .../sdk/other-types/irelogger-class.md | 2 +- .../on-analysis-event-func-typedef.md | 2 +- .../on-begin-end-pass-func-typedef.md | 2 +- .../on-relog-event-func-typedef.md | 2 +- .../other-types/on-trace-info-func-typedef.md | 2 +- .../sdk/other-types/relog-callbacks-struct.md | 2 +- .../other-types/relog-descriptor-struct.md | 2 +- ...-retention-system-event-flags-constants.md | 2 +- .../sdk/other-types/result-code-enum.md | 2 +- ...cing-session-msvc-event-flags-constants.md | 2 +- .../tracing-session-options-struct.md | 2 +- .../tracing-session-statistics-struct.md | 2 +- ...ng-session-system-event-flags-constants.md | 2 +- docs/build-insights/reference/sdk/overview.md | 2 +- .../reference/vcperf-commands.md | 9 ++-- docs/build-insights/reference/wpa-views.md | 4 +- .../tutorials/vcperf-and-wpa.md | 13 ++--- docs/build-insights/tutorials/wpa-basics.md | 4 +- docs/build/clang-support-cmake.md | 26 ++++++--- docs/build/clang-support-msbuild.md | 2 +- ...make-predefined-configuration-reference.md | 2 +- .../configure-cmake-debugging-sessions.md | 2 +- ...eating-and-managing-visual-cpp-projects.md | 2 +- docs/build/customize-cmake-settings.md | 2 +- .../build/reference/advanced-property-page.md | 4 +- ...clr-common-language-runtime-compilation.md | 2 +- ...path-of-source-code-file-in-diagnostics.md | 2 +- docs/build/vscpp-step-1-create.md | 2 +- ...creating-and-using-a-static-library-cpp.md | 14 ++--- docs/cppcx/static-libraries-c-cx.md | 8 +-- .../consumer-wizard-generated-classes.md | 2 +- .../consumer-wizard-generated-methods.md | 2 +- docs/data/oledb/creating-a-simple-consumer.md | 2 +- .../creating-a-simple-read-only-provider.md | 2 +- ...ating-an-ole-db-consumer-using-a-wizard.md | 2 +- .../data/oledb/creating-an-ole-db-consumer.md | 2 +- docs/data/oledb/creating-the-provider.md | 2 +- ...a-members-in-wizard-generated-accessors.md | 2 +- .../oledb/implementing-a-simple-consumer.md | 2 +- .../oledb/provider-wizard-generated-files.md | 2 +- docs/data/oledb/supporting-schema-rowsets.md | 2 +- ...net-programming-with-cpp-cli-visual-cpp.md | 11 +++- ...create-clr-console-applications-cpp-cli.md | 4 +- ...m-that-targets-the-clr-in-visual-studio.md | 10 ++-- docs/error-messages/toc.yml | 2 + .../tool-errors/command-line-error-d8049.md | 22 ++++++++ ...command-line-errors-d8000-through-d9999.md | 4 +- docs/ide/cpp-linter-overview.md | 11 +--- docs/ide/read-and-understand-code-cpp.md | 2 +- .../walkthrough-deploying-your-program-cpp.md | 4 +- ...working-with-projects-and-solutions-cpp.md | 6 +-- docs/ide/writing-and-refactoring-code-cpp.md | 4 +- ...ckedcompareexchange-intrinsic-functions.md | 15 ++++-- ...pareexchangepointer-intrinsic-functions.md | 2 +- .../interlockedor-intrinsic-functions.md | 2 +- docs/linux/cmake-linux-configure.md | 6 +-- docs/linux/configure-a-linux-project.md | 15 +++--- .../connect-to-your-remote-linux-computer.md | 12 ++--- docs/linux/connectionmanager-reference.md | 2 +- docs/linux/create-a-new-linux-project.md | 4 +- ...deploy-run-and-debug-your-linux-project.md | 14 ++--- ...nd-setup-the-linux-development-workload.md | 8 +-- ...mpliant-secure-remote-linux-development.md | 2 +- .../add-class-from-typelib-wizard.md | 2 +- .../mfc/reference/mfc-odbc-consumer-wizard.md | 2 +- ...hrough-using-the-new-mfc-shell-controls.md | 6 +-- docs/overview/install-c17-support.md | 44 ++++----------- docs/overview/overview-of-cpp-development.md | 14 ++--- ...-and-features-in-visual-studio-editions.md | 13 ++++- ...through-debugging-a-cpp-amp-application.md | 12 ++--- .../amp/walkthrough-matrix-multiplication.md | 8 +-- ...ugh-creating-an-agent-based-application.md | 54 ++++++++++--------- ...ugh-creating-a-standard-cpp-program-cpp.md | 6 +-- ...eating-windows-desktop-applications-cpp.md | 10 ++-- 192 files changed, 374 insertions(+), 345 deletions(-) create mode 100644 docs/error-messages/tool-errors/command-line-error-d8049.md diff --git a/docs/atl/example-implementing-a-property-page.md b/docs/atl/example-implementing-a-property-page.md index c7e80a50e3a..c6e44f85f6f 100644 --- a/docs/atl/example-implementing-a-property-page.md +++ b/docs/atl/example-implementing-a-property-page.md @@ -7,7 +7,7 @@ ms.assetid: c30b67fe-ce08-4249-ae29-f3060fa8d61e --- # Example: Implementing a Property Page -::: moniker range="msvc-160" +::: moniker range=">=msvc-160" The ATL Property Page wizard is not available in Visual Studio 2019 and later. diff --git a/docs/atl/implementing-property-pages.md b/docs/atl/implementing-property-pages.md index fe87f6889c8..3dcdced9d07 100644 --- a/docs/atl/implementing-property-pages.md +++ b/docs/atl/implementing-property-pages.md @@ -7,7 +7,7 @@ ms.assetid: 62f29440-33a7-40eb-a1ef-3634c95f640c --- # Implementing Property Pages -::: moniker range="msvc-160" +::: moniker range=">=msvc-160" The ATL Property Page wizard is not available in Visual Studio 2019 and later. diff --git a/docs/atl/reference/adding-an-atl-active-server-page-component.md b/docs/atl/reference/adding-an-atl-active-server-page-component.md index 253100c5772..508bf1fbfca 100644 --- a/docs/atl/reference/adding-an-atl-active-server-page-component.md +++ b/docs/atl/reference/adding-an-atl-active-server-page-component.md @@ -6,7 +6,7 @@ ms.assetid: 7be2204c-6e58-4099-8892-001b848c8987 --- # Adding an ATL Active Server Page Component -::: moniker range="msvc-160" +::: moniker range=">=msvc-160" The ATL Active Server Pages component wizard is not available in Visual Studio 2019 and later. diff --git a/docs/atl/reference/adding-an-atl-com-plus-1-0-component.md b/docs/atl/reference/adding-an-atl-com-plus-1-0-component.md index 603ba47fad1..6df0a367ba5 100644 --- a/docs/atl/reference/adding-an-atl-com-plus-1-0-component.md +++ b/docs/atl/reference/adding-an-atl-com-plus-1-0-component.md @@ -6,7 +6,7 @@ ms.assetid: c6c95e64-9ee4-4a6e-8804-5930202ce1b9 --- # Adding an ATL COM+ 1.0 Component -::: moniker range="msvc-160" +::: moniker range=">=msvc-160" The ATL COM+ 1.0 Component wizard is not available in Visual Studio 2019 and later. diff --git a/docs/atl/reference/adding-an-atl-ole-db-consumer.md b/docs/atl/reference/adding-an-atl-ole-db-consumer.md index d44cc88f164..52b1acc39ab 100644 --- a/docs/atl/reference/adding-an-atl-ole-db-consumer.md +++ b/docs/atl/reference/adding-an-atl-ole-db-consumer.md @@ -7,7 +7,7 @@ ms.assetid: f940a513-4e42-4148-b521-dd0d7dc89fa2 --- # Adding an ATL OLE DB Consumer -::: moniker range="msvc-160" +::: moniker range=">=msvc-160" The ATL OLE DB Consumer wizard is not available in Visual Studio 2019 and later. You can still add the functionality manually. For more information, see [Creating a Consumer Without Using a Wizard](../../data/oledb/creating-a-consumer-without-using-a-wizard.md). diff --git a/docs/atl/reference/adding-an-atl-ole-db-provider.md b/docs/atl/reference/adding-an-atl-ole-db-provider.md index 0b588ceece7..3aba76e606f 100644 --- a/docs/atl/reference/adding-an-atl-ole-db-provider.md +++ b/docs/atl/reference/adding-an-atl-ole-db-provider.md @@ -7,7 +7,7 @@ ms.assetid: 26fba1e3-880f-4bc6-90e5-2096a48a3a6c --- # Adding an ATL OLE DB Provider -::: moniker range="msvc-160" +::: moniker range=">=msvc-160" The ATL OLE DB Provider wizard is not available in Visual Studio 2019 and later. diff --git a/docs/atl/reference/atl-active-server-page-component-wizard.md b/docs/atl/reference/atl-active-server-page-component-wizard.md index fa5cc0a0e83..ceab8c73f93 100644 --- a/docs/atl/reference/atl-active-server-page-component-wizard.md +++ b/docs/atl/reference/atl-active-server-page-component-wizard.md @@ -7,7 +7,7 @@ ms.assetid: 5a5cb904-dbbf-44ea-ad3d-2ddd14c1d3c5 --- # ATL Active Server Page Component Wizard -::: moniker range="msvc-160" +::: moniker range=">=msvc-160" This wizard is not available in Visual Studio 2019 and later. diff --git a/docs/atl/reference/atl-com-plus-1-0-component-wizard.md b/docs/atl/reference/atl-com-plus-1-0-component-wizard.md index 2234a04e69a..4f342caa931 100644 --- a/docs/atl/reference/atl-com-plus-1-0-component-wizard.md +++ b/docs/atl/reference/atl-com-plus-1-0-component-wizard.md @@ -7,7 +7,7 @@ ms.assetid: 11670681-8671-4122-96a4-2e52f8dadce0 --- # ATL COM+ 1.0 Component Wizard -::: moniker range="msvc-160" +::: moniker range=">=msvc-160" This wizard is not available in Visual Studio 2019 and later. diff --git a/docs/atl/reference/atl-ole-db-consumer-wizard.md b/docs/atl/reference/atl-ole-db-consumer-wizard.md index 9689825beb6..da09ffeebbb 100644 --- a/docs/atl/reference/atl-ole-db-consumer-wizard.md +++ b/docs/atl/reference/atl-ole-db-consumer-wizard.md @@ -7,7 +7,7 @@ ms.assetid: dcb68ed1-2224-422f-9f7b-108a74864204 --- # ATL OLE DB Consumer Wizard -::: moniker range="msvc-160" +::: moniker range=">=msvc-160" This wizard is not available in Visual Studio 2019 and later. diff --git a/docs/atl/reference/atl-ole-db-provider-wizard.md b/docs/atl/reference/atl-ole-db-provider-wizard.md index 571ebc94957..29417f6f85d 100644 --- a/docs/atl/reference/atl-ole-db-provider-wizard.md +++ b/docs/atl/reference/atl-ole-db-provider-wizard.md @@ -7,7 +7,7 @@ ms.assetid: cf91ba78-01d1-4d12-b673-e95d96bfbebe --- # ATL OLE DB Provider Wizard -::: moniker range="msvc-160" +::: moniker range=">=msvc-160" This wizard is not available in Visual Studio 2019 and later. diff --git a/docs/atl/reference/atl-property-page-wizard.md b/docs/atl/reference/atl-property-page-wizard.md index 895ff9bbb70..16c00456903 100644 --- a/docs/atl/reference/atl-property-page-wizard.md +++ b/docs/atl/reference/atl-property-page-wizard.md @@ -8,7 +8,7 @@ ms.assetid: 6113e325-facd-4f68-b491-144d75209922 --- # ATL Property Page Wizard -::: moniker range="msvc-160" +::: moniker range=">=msvc-160" This wizard is not available in Visual Studio 2019 and later. diff --git a/docs/atl/reference/com-plus-1-0-atl-com-plus-1-0-component-wizard.md b/docs/atl/reference/com-plus-1-0-atl-com-plus-1-0-component-wizard.md index be124f9048a..0a125245518 100644 --- a/docs/atl/reference/com-plus-1-0-atl-com-plus-1-0-component-wizard.md +++ b/docs/atl/reference/com-plus-1-0-atl-com-plus-1-0-component-wizard.md @@ -7,7 +7,7 @@ ms.assetid: 2fbe259c-6be1-4d0e-9cfe-721c75c97cb1 --- # COM+ 1.0, ATL COM+ 1.0 Component Wizard -::: moniker range="msvc-160" +::: moniker range=">=msvc-160" This wizard is not available in Visual Studio 2019 and later. diff --git a/docs/atl/reference/options-atl-property-page-wizard.md b/docs/atl/reference/options-atl-property-page-wizard.md index bb5185ae7ba..a49caf9d072 100644 --- a/docs/atl/reference/options-atl-property-page-wizard.md +++ b/docs/atl/reference/options-atl-property-page-wizard.md @@ -8,7 +8,7 @@ ms.assetid: a7107779-b2ea-4f99-b84b-7f3e0c504bc8 --- # Options, ATL Property Page Wizard -::: moniker range="msvc-160" +::: moniker range=">=msvc-160" The ATL Property Page wizard is not available in Visual Studio 2019 and later. diff --git a/docs/atl/reference/strings-atl-property-page-wizard.md b/docs/atl/reference/strings-atl-property-page-wizard.md index 93fd1d9f381..af7682dd9f2 100644 --- a/docs/atl/reference/strings-atl-property-page-wizard.md +++ b/docs/atl/reference/strings-atl-property-page-wizard.md @@ -8,7 +8,7 @@ ms.assetid: 00547db6-911f-49eb-92e1-2ba67079d4df --- # Strings, ATL Property Page Wizard -::: moniker range="msvc-160" +::: moniker range=">=msvc-160" The ATL Property Page wizard is not available in Visual Studio 2019 and later. diff --git a/docs/build-insights/get-started-with-cpp-build-insights.md b/docs/build-insights/get-started-with-cpp-build-insights.md index 99659b39b12..038b948e192 100644 --- a/docs/build-insights/get-started-with-cpp-build-insights.md +++ b/docs/build-insights/get-started-with-cpp-build-insights.md @@ -9,10 +9,10 @@ ms.custom: intro-get-started ::: moniker range="<=msvc-150" -The C++ Build Insights tools are available in Visual Studio 2019. To see the documentation for that version, set the Visual Studio **Version** selector control for this article to Visual Studio 2019. It's found at the top of the table of contents on this page. +The C++ Build Insights tools are available in Visual Studio 2019 and later. To see the documentation for that version, set the Visual Studio **Version** selector control for this article to Visual Studio 2019 or later. It's found at the top of the table of contents on this page. ::: moniker-end -::: moniker range="msvc-160" +::: moniker range=">=msvc-160" C++ Build Insights is a collection of tools that provides increased visibility into the Microsoft Visual C++ (MSVC) tool chain. The tools collect data about your C++ builds, and present it in a format that can help you answer common questions, like: diff --git a/docs/build-insights/reference/sdk/c-event-data-types/cl-pass-data-struct.md b/docs/build-insights/reference/sdk/c-event-data-types/cl-pass-data-struct.md index a670a652c4c..60655fba341 100644 --- a/docs/build-insights/reference/sdk/c-event-data-types/cl-pass-data-struct.md +++ b/docs/build-insights/reference/sdk/c-event-data-types/cl-pass-data-struct.md @@ -8,7 +8,7 @@ helpviewer_keywords: ["C++ Build Insights", "C++ Build Insights SDK", "CL_PASS_D ::: moniker range="<=msvc-140" -The C++ Build Insights SDK is compatible with Visual Studio 2017 and above. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or Visual Studio 2019. It's found at the top of the table of contents on this page. +The C++ Build Insights SDK is compatible with Visual Studio 2017 and later. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or later. It's found at the top of the table of contents on this page. ::: moniker-end ::: moniker range=">=msvc-150" diff --git a/docs/build-insights/reference/sdk/c-event-data-types/event-collection-data-struct.md b/docs/build-insights/reference/sdk/c-event-data-types/event-collection-data-struct.md index 4fef60b896a..b3301f97a33 100644 --- a/docs/build-insights/reference/sdk/c-event-data-types/event-collection-data-struct.md +++ b/docs/build-insights/reference/sdk/c-event-data-types/event-collection-data-struct.md @@ -8,7 +8,7 @@ helpviewer_keywords: ["C++ Build Insights", "C++ Build Insights SDK", "EVENT_COL ::: moniker range="<=msvc-140" -The C++ Build Insights SDK is compatible with Visual Studio 2017 and above. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or Visual Studio 2019. It's found at the top of the table of contents on this page. +The C++ Build Insights SDK is compatible with Visual Studio 2017 and later. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or later. It's found at the top of the table of contents on this page. ::: moniker-end ::: moniker range=">=msvc-150" diff --git a/docs/build-insights/reference/sdk/c-event-data-types/event-data-struct.md b/docs/build-insights/reference/sdk/c-event-data-types/event-data-struct.md index f3b03f71d0f..3de2bb74579 100644 --- a/docs/build-insights/reference/sdk/c-event-data-types/event-data-struct.md +++ b/docs/build-insights/reference/sdk/c-event-data-types/event-data-struct.md @@ -8,7 +8,7 @@ helpviewer_keywords: ["C++ Build Insights", "C++ Build Insights SDK", "EVENT_DAT ::: moniker range="<=msvc-140" -The C++ Build Insights SDK is compatible with Visual Studio 2017 and above. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or Visual Studio 2019. It's found at the top of the table of contents on this page. +The C++ Build Insights SDK is compatible with Visual Studio 2017 and later. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or later. It's found at the top of the table of contents on this page. ::: moniker-end ::: moniker range=">=msvc-150" diff --git a/docs/build-insights/reference/sdk/c-event-data-types/event-id-enum.md b/docs/build-insights/reference/sdk/c-event-data-types/event-id-enum.md index 0127ff97b15..496af5fae9d 100644 --- a/docs/build-insights/reference/sdk/c-event-data-types/event-id-enum.md +++ b/docs/build-insights/reference/sdk/c-event-data-types/event-id-enum.md @@ -8,7 +8,7 @@ helpviewer_keywords: ["C++ Build Insights", "C++ Build Insights SDK", "EVENT_ID" ::: moniker range="<=msvc-140" -The C++ Build Insights SDK is compatible with Visual Studio 2017 and above. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or Visual Studio 2019. It's found at the top of the table of contents on this page. +The C++ Build Insights SDK is compatible with Visual Studio 2017 and later. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or later. It's found at the top of the table of contents on this page. ::: moniker-end ::: moniker range=">=msvc-150" diff --git a/docs/build-insights/reference/sdk/c-event-data-types/file-data-struct.md b/docs/build-insights/reference/sdk/c-event-data-types/file-data-struct.md index cc25afa7aad..6ee47af9c32 100644 --- a/docs/build-insights/reference/sdk/c-event-data-types/file-data-struct.md +++ b/docs/build-insights/reference/sdk/c-event-data-types/file-data-struct.md @@ -8,7 +8,7 @@ helpviewer_keywords: ["C++ Build Insights", "C++ Build Insights SDK", "FILE_DATA ::: moniker range="<=msvc-140" -The C++ Build Insights SDK is compatible with Visual Studio 2017 and above. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or Visual Studio 2019. It's found at the top of the table of contents on this page. +The C++ Build Insights SDK is compatible with Visual Studio 2017 and later. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or later. It's found at the top of the table of contents on this page. ::: moniker-end ::: moniker range=">=msvc-150" diff --git a/docs/build-insights/reference/sdk/c-event-data-types/file-type-code-enum.md b/docs/build-insights/reference/sdk/c-event-data-types/file-type-code-enum.md index 90f2c8aa741..1b1626e9f75 100644 --- a/docs/build-insights/reference/sdk/c-event-data-types/file-type-code-enum.md +++ b/docs/build-insights/reference/sdk/c-event-data-types/file-type-code-enum.md @@ -8,7 +8,7 @@ helpviewer_keywords: ["C++ Build Insights", "C++ Build Insights SDK", "FILE_TYPE ::: moniker range="<=msvc-140" -The C++ Build Insights SDK is compatible with Visual Studio 2017 and above. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or Visual Studio 2019. It's found at the top of the table of contents on this page. +The C++ Build Insights SDK is compatible with Visual Studio 2017 and later. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or later. It's found at the top of the table of contents on this page. ::: moniker-end ::: moniker range=">=msvc-150" diff --git a/docs/build-insights/reference/sdk/c-event-data-types/front-end-file-data-struct.md b/docs/build-insights/reference/sdk/c-event-data-types/front-end-file-data-struct.md index d486812a0b7..b4c5f345c33 100644 --- a/docs/build-insights/reference/sdk/c-event-data-types/front-end-file-data-struct.md +++ b/docs/build-insights/reference/sdk/c-event-data-types/front-end-file-data-struct.md @@ -8,7 +8,7 @@ helpviewer_keywords: ["C++ Build Insights", "C++ Build Insights SDK", "FRONT_END ::: moniker range="<=msvc-140" -The C++ Build Insights SDK is compatible with Visual Studio 2017 and above. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or Visual Studio 2019. It's found at the top of the table of contents on this page. +The C++ Build Insights SDK is compatible with Visual Studio 2017 and later. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or later. It's found at the top of the table of contents on this page. ::: moniker-end ::: moniker range=">=msvc-150" diff --git a/docs/build-insights/reference/sdk/c-event-data-types/function-data-struct.md b/docs/build-insights/reference/sdk/c-event-data-types/function-data-struct.md index c52267d3d71..f4bbfea7231 100644 --- a/docs/build-insights/reference/sdk/c-event-data-types/function-data-struct.md +++ b/docs/build-insights/reference/sdk/c-event-data-types/function-data-struct.md @@ -8,7 +8,7 @@ helpviewer_keywords: ["C++ Build Insights", "C++ Build Insights SDK", "FUNCTION_ ::: moniker range="<=msvc-140" -The C++ Build Insights SDK is compatible with Visual Studio 2017 and above. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or Visual Studio 2019. It's found at the top of the table of contents on this page. +The C++ Build Insights SDK is compatible with Visual Studio 2017 and later. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or later. It's found at the top of the table of contents on this page. ::: moniker-end ::: moniker range=">=msvc-150" diff --git a/docs/build-insights/reference/sdk/c-event-data-types/function-force-inlinee-data-struct.md b/docs/build-insights/reference/sdk/c-event-data-types/function-force-inlinee-data-struct.md index c9010546f40..122800678c4 100644 --- a/docs/build-insights/reference/sdk/c-event-data-types/function-force-inlinee-data-struct.md +++ b/docs/build-insights/reference/sdk/c-event-data-types/function-force-inlinee-data-struct.md @@ -8,7 +8,7 @@ helpviewer_keywords: ["C++ Build Insights", "C++ Build Insights SDK", "FUNCTION_ ::: moniker range="<=msvc-140" -The C++ Build Insights SDK is compatible with Visual Studio 2017 and above. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or Visual Studio 2019. It's found at the top of the table of contents on this page. +The C++ Build Insights SDK is compatible with Visual Studio 2017 and later. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or later. It's found at the top of the table of contents on this page. ::: moniker-end ::: moniker range=">=msvc-150" diff --git a/docs/build-insights/reference/sdk/c-event-data-types/invocation-data-struct.md b/docs/build-insights/reference/sdk/c-event-data-types/invocation-data-struct.md index d677a9ba2ab..2a188c9c002 100644 --- a/docs/build-insights/reference/sdk/c-event-data-types/invocation-data-struct.md +++ b/docs/build-insights/reference/sdk/c-event-data-types/invocation-data-struct.md @@ -8,7 +8,7 @@ helpviewer_keywords: ["C++ Build Insights", "C++ Build Insights SDK", "INVOCATIO ::: moniker range="<=msvc-140" -The C++ Build Insights SDK is compatible with Visual Studio 2017 and above. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or Visual Studio 2019. It's found at the top of the table of contents on this page. +The C++ Build Insights SDK is compatible with Visual Studio 2017 and later. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or later. It's found at the top of the table of contents on this page. ::: moniker-end ::: moniker range=">=msvc-150" diff --git a/docs/build-insights/reference/sdk/c-event-data-types/invocation-version-data-struct.md b/docs/build-insights/reference/sdk/c-event-data-types/invocation-version-data-struct.md index 1b509de5668..29407ee0256 100644 --- a/docs/build-insights/reference/sdk/c-event-data-types/invocation-version-data-struct.md +++ b/docs/build-insights/reference/sdk/c-event-data-types/invocation-version-data-struct.md @@ -8,7 +8,7 @@ helpviewer_keywords: ["C++ Build Insights", "C++ Build Insights SDK", "INVOCATIO ::: moniker range="<=msvc-140" -The C++ Build Insights SDK is compatible with Visual Studio 2017 and above. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or Visual Studio 2019. It's found at the top of the table of contents on this page. +The C++ Build Insights SDK is compatible with Visual Studio 2017 and later. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or later. It's found at the top of the table of contents on this page. ::: moniker-end ::: moniker range=">=msvc-150" diff --git a/docs/build-insights/reference/sdk/c-event-data-types/msvc-tool-code-enum.md b/docs/build-insights/reference/sdk/c-event-data-types/msvc-tool-code-enum.md index 085b863e042..c0c00c4d11c 100644 --- a/docs/build-insights/reference/sdk/c-event-data-types/msvc-tool-code-enum.md +++ b/docs/build-insights/reference/sdk/c-event-data-types/msvc-tool-code-enum.md @@ -8,7 +8,7 @@ helpviewer_keywords: ["C++ Build Insights", "C++ Build Insights SDK", "MSVC_TOOL ::: moniker range="<=msvc-140" -The C++ Build Insights SDK is compatible with Visual Studio 2017 and above. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or Visual Studio 2019. It's found at the top of the table of contents on this page. +The C++ Build Insights SDK is compatible with Visual Studio 2017 and later. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or later. It's found at the top of the table of contents on this page. ::: moniker-end ::: moniker range=">=msvc-150" diff --git a/docs/build-insights/reference/sdk/c-event-data-types/name-value-pair-data-struct.md b/docs/build-insights/reference/sdk/c-event-data-types/name-value-pair-data-struct.md index d23ec9633af..f748ff97c1b 100644 --- a/docs/build-insights/reference/sdk/c-event-data-types/name-value-pair-data-struct.md +++ b/docs/build-insights/reference/sdk/c-event-data-types/name-value-pair-data-struct.md @@ -8,7 +8,7 @@ helpviewer_keywords: ["C++ Build Insights", "C++ Build Insights SDK", "NAME_VALU ::: moniker range="<=msvc-140" -The C++ Build Insights SDK is compatible with Visual Studio 2017 and above. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or Visual Studio 2019. It's found at the top of the table of contents on this page. +The C++ Build Insights SDK is compatible with Visual Studio 2017 and later. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or later. It's found at the top of the table of contents on this page. ::: moniker-end ::: moniker range=">=msvc-150" diff --git a/docs/build-insights/reference/sdk/c-event-data-types/symbol-name-data-struct.md b/docs/build-insights/reference/sdk/c-event-data-types/symbol-name-data-struct.md index 2686e887ec2..933167d616a 100644 --- a/docs/build-insights/reference/sdk/c-event-data-types/symbol-name-data-struct.md +++ b/docs/build-insights/reference/sdk/c-event-data-types/symbol-name-data-struct.md @@ -8,7 +8,7 @@ helpviewer_keywords: ["C++ Build Insights", "C++ Build Insights SDK", "SYMBOL_NA ::: moniker range="<=msvc-140" -The C++ Build Insights SDK is compatible with Visual Studio 2017 and above. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or Visual Studio 2019. It's found at the top of the table of contents on this page. +The C++ Build Insights SDK is compatible with Visual Studio 2017 and later. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or later. It's found at the top of the table of contents on this page. ::: moniker-end ::: moniker range=">=msvc-150" diff --git a/docs/build-insights/reference/sdk/c-event-data-types/template-instantiation-data-struct.md b/docs/build-insights/reference/sdk/c-event-data-types/template-instantiation-data-struct.md index 32acf5af8c1..a2056df0d06 100644 --- a/docs/build-insights/reference/sdk/c-event-data-types/template-instantiation-data-struct.md +++ b/docs/build-insights/reference/sdk/c-event-data-types/template-instantiation-data-struct.md @@ -8,7 +8,7 @@ helpviewer_keywords: ["C++ Build Insights", "C++ Build Insights SDK", "TEMPLATE_ ::: moniker range="<=msvc-140" -The C++ Build Insights SDK is compatible with Visual Studio 2017 and above. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or Visual Studio 2019. It's found at the top of the table of contents on this page. +The C++ Build Insights SDK is compatible with Visual Studio 2017 and later. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or later. It's found at the top of the table of contents on this page. ::: moniker-end ::: moniker range=">=msvc-150" diff --git a/docs/build-insights/reference/sdk/c-event-data-types/template-instantiation-kind-code-enum.md b/docs/build-insights/reference/sdk/c-event-data-types/template-instantiation-kind-code-enum.md index 5d3d2f0e7e5..f258401a815 100644 --- a/docs/build-insights/reference/sdk/c-event-data-types/template-instantiation-kind-code-enum.md +++ b/docs/build-insights/reference/sdk/c-event-data-types/template-instantiation-kind-code-enum.md @@ -8,7 +8,7 @@ helpviewer_keywords: ["C++ Build Insights", "C++ Build Insights SDK", "TEMPLATE_ ::: moniker range="<=msvc-140" -The C++ Build Insights SDK is compatible with Visual Studio 2017 and above. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or Visual Studio 2019. It's found at the top of the table of contents on this page. +The C++ Build Insights SDK is compatible with Visual Studio 2017 and later. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or later. It's found at the top of the table of contents on this page. ::: moniker-end ::: moniker range=">=msvc-150" diff --git a/docs/build-insights/reference/sdk/c-event-data-types/trace-info-data-struct.md b/docs/build-insights/reference/sdk/c-event-data-types/trace-info-data-struct.md index 951e3ec00b9..e5ab1bc1309 100644 --- a/docs/build-insights/reference/sdk/c-event-data-types/trace-info-data-struct.md +++ b/docs/build-insights/reference/sdk/c-event-data-types/trace-info-data-struct.md @@ -8,7 +8,7 @@ helpviewer_keywords: ["C++ Build Insights", "C++ Build Insights SDK", "TRACE_INF ::: moniker range="<=msvc-140" -The C++ Build Insights SDK is compatible with Visual Studio 2017 and above. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or Visual Studio 2019. It's found at the top of the table of contents on this page. +The C++ Build Insights SDK is compatible with Visual Studio 2017 and later. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or later. It's found at the top of the table of contents on this page. ::: moniker-end ::: moniker range=">=msvc-150" diff --git a/docs/build-insights/reference/sdk/c-event-data-types/translation-unit-pass-code-enum.md b/docs/build-insights/reference/sdk/c-event-data-types/translation-unit-pass-code-enum.md index f4a0700f2d9..b3091655098 100644 --- a/docs/build-insights/reference/sdk/c-event-data-types/translation-unit-pass-code-enum.md +++ b/docs/build-insights/reference/sdk/c-event-data-types/translation-unit-pass-code-enum.md @@ -8,7 +8,7 @@ helpviewer_keywords: ["C++ Build Insights", "C++ Build Insights SDK", "TRANSLATI ::: moniker range="<=msvc-140" -The C++ Build Insights SDK is compatible with Visual Studio 2017 and above. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or Visual Studio 2019. It's found at the top of the table of contents on this page. +The C++ Build Insights SDK is compatible with Visual Studio 2017 and later. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or later. It's found at the top of the table of contents on this page. ::: moniker-end ::: moniker range=">=msvc-150" diff --git a/docs/build-insights/reference/sdk/c-event-data-types/translation-unit-type-data.md b/docs/build-insights/reference/sdk/c-event-data-types/translation-unit-type-data.md index 2a72eb350c7..6d7821bfa3b 100644 --- a/docs/build-insights/reference/sdk/c-event-data-types/translation-unit-type-data.md +++ b/docs/build-insights/reference/sdk/c-event-data-types/translation-unit-type-data.md @@ -8,7 +8,7 @@ helpviewer_keywords: ["C++ Build Insights", "C++ Build Insights SDK", "TRANSLATI ::: moniker range="<=msvc-140" -The C++ Build Insights SDK is compatible with Visual Studio 2017 and above. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or Visual Studio 2019. It's found at the top of the table of contents on this page. +The C++ Build Insights SDK is compatible with Visual Studio 2017 and later. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or later. It's found at the top of the table of contents on this page. ::: moniker-end ::: moniker range=">=msvc-150" diff --git a/docs/build-insights/reference/sdk/c-event-data-types/translation-unit-type.md b/docs/build-insights/reference/sdk/c-event-data-types/translation-unit-type.md index 472876b4db6..1ee8e38e00e 100644 --- a/docs/build-insights/reference/sdk/c-event-data-types/translation-unit-type.md +++ b/docs/build-insights/reference/sdk/c-event-data-types/translation-unit-type.md @@ -8,7 +8,7 @@ helpviewer_keywords: ["C++ Build Insights", "C++ Build Insights SDK", "TRANSLATI ::: moniker range="<=msvc-140" -The C++ Build Insights SDK is compatible with Visual Studio 2017 and above. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or Visual Studio 2019. It's found at the top of the table of contents on this page. +The C++ Build Insights SDK is compatible with Visual Studio 2017 and later. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or later. It's found at the top of the table of contents on this page. ::: moniker-end ::: moniker range=">=msvc-150" diff --git a/docs/build-insights/reference/sdk/cpp-event-data-types/activity.md b/docs/build-insights/reference/sdk/cpp-event-data-types/activity.md index b70dc7053b6..aa060dc27ba 100644 --- a/docs/build-insights/reference/sdk/cpp-event-data-types/activity.md +++ b/docs/build-insights/reference/sdk/cpp-event-data-types/activity.md @@ -8,7 +8,7 @@ helpviewer_keywords: ["C++ Build Insights", "C++ Build Insights SDK", "Activity" ::: moniker range="<=msvc-140" -The C++ Build Insights SDK is compatible with Visual Studio 2017 and above. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or Visual Studio 2019. It's found at the top of the table of contents on this page. +The C++ Build Insights SDK is compatible with Visual Studio 2017 and later. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or later. It's found at the top of the table of contents on this page. ::: moniker-end ::: moniker range=">=msvc-150" diff --git a/docs/build-insights/reference/sdk/cpp-event-data-types/back-end-pass.md b/docs/build-insights/reference/sdk/cpp-event-data-types/back-end-pass.md index 176f95d945c..d01ecfb1fbc 100644 --- a/docs/build-insights/reference/sdk/cpp-event-data-types/back-end-pass.md +++ b/docs/build-insights/reference/sdk/cpp-event-data-types/back-end-pass.md @@ -8,7 +8,7 @@ helpviewer_keywords: ["C++ Build Insights", "C++ Build Insights SDK", "BackEndPa ::: moniker range="<=msvc-140" -The C++ Build Insights SDK is compatible with Visual Studio 2017 and above. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or Visual Studio 2019. It's found at the top of the table of contents on this page. +The C++ Build Insights SDK is compatible with Visual Studio 2017 and later. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or later. It's found at the top of the table of contents on this page. ::: moniker-end ::: moniker range=">=msvc-150" diff --git a/docs/build-insights/reference/sdk/cpp-event-data-types/bottom-up.md b/docs/build-insights/reference/sdk/cpp-event-data-types/bottom-up.md index ab3716c283d..125c2478e57 100644 --- a/docs/build-insights/reference/sdk/cpp-event-data-types/bottom-up.md +++ b/docs/build-insights/reference/sdk/cpp-event-data-types/bottom-up.md @@ -8,7 +8,7 @@ helpviewer_keywords: ["C++ Build Insights", "C++ Build Insights SDK", "BottomUp" ::: moniker range="<=msvc-140" -The C++ Build Insights SDK is compatible with Visual Studio 2017 and above. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or Visual Studio 2019. It's found at the top of the table of contents on this page. +The C++ Build Insights SDK is compatible with Visual Studio 2017 and later. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or later. It's found at the top of the table of contents on this page. ::: moniker-end ::: moniker range=">=msvc-150" diff --git a/docs/build-insights/reference/sdk/cpp-event-data-types/c1-dll.md b/docs/build-insights/reference/sdk/cpp-event-data-types/c1-dll.md index 24e19d6ec25..8ad2fb40660 100644 --- a/docs/build-insights/reference/sdk/cpp-event-data-types/c1-dll.md +++ b/docs/build-insights/reference/sdk/cpp-event-data-types/c1-dll.md @@ -8,7 +8,7 @@ helpviewer_keywords: ["C++ Build Insights", "C++ Build Insights SDK", "C1DLL", " ::: moniker range="<=msvc-140" -The C++ Build Insights SDK is compatible with Visual Studio 2017 and above. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or Visual Studio 2019. It's found at the top of the table of contents on this page. +The C++ Build Insights SDK is compatible with Visual Studio 2017 and later. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or later. It's found at the top of the table of contents on this page. ::: moniker-end ::: moniker range=">=msvc-150" diff --git a/docs/build-insights/reference/sdk/cpp-event-data-types/c2-dll.md b/docs/build-insights/reference/sdk/cpp-event-data-types/c2-dll.md index 2c90aacf1a7..677326609cb 100644 --- a/docs/build-insights/reference/sdk/cpp-event-data-types/c2-dll.md +++ b/docs/build-insights/reference/sdk/cpp-event-data-types/c2-dll.md @@ -8,7 +8,7 @@ helpviewer_keywords: ["C++ Build Insights", "C++ Build Insights SDK", "C2DLL", " ::: moniker range="<=msvc-140" -The C++ Build Insights SDK is compatible with Visual Studio 2017 and above. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or Visual Studio 2019. It's found at the top of the table of contents on this page. +The C++ Build Insights SDK is compatible with Visual Studio 2017 and later. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or later. It's found at the top of the table of contents on this page. ::: moniker-end ::: moniker range=">=msvc-150" diff --git a/docs/build-insights/reference/sdk/cpp-event-data-types/code-generation.md b/docs/build-insights/reference/sdk/cpp-event-data-types/code-generation.md index 04ac8aecce4..0ae7671e26c 100644 --- a/docs/build-insights/reference/sdk/cpp-event-data-types/code-generation.md +++ b/docs/build-insights/reference/sdk/cpp-event-data-types/code-generation.md @@ -8,7 +8,7 @@ helpviewer_keywords: ["C++ Build Insights", "C++ Build Insights SDK", "CodeGener ::: moniker range="<=msvc-140" -The C++ Build Insights SDK is compatible with Visual Studio 2017 and above. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or Visual Studio 2019. It's found at the top of the table of contents on this page. +The C++ Build Insights SDK is compatible with Visual Studio 2017 and later. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or later. It's found at the top of the table of contents on this page. ::: moniker-end ::: moniker range=">=msvc-150" diff --git a/docs/build-insights/reference/sdk/cpp-event-data-types/command-line.md b/docs/build-insights/reference/sdk/cpp-event-data-types/command-line.md index 0efc1ac5557..9fcaa9a69f7 100644 --- a/docs/build-insights/reference/sdk/cpp-event-data-types/command-line.md +++ b/docs/build-insights/reference/sdk/cpp-event-data-types/command-line.md @@ -8,7 +8,7 @@ helpviewer_keywords: ["C++ Build Insights", "C++ Build Insights SDK", "CommandLi ::: moniker range="<=msvc-140" -The C++ Build Insights SDK is compatible with Visual Studio 2017 and above. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or Visual Studio 2019. It's found at the top of the table of contents on this page. +The C++ Build Insights SDK is compatible with Visual Studio 2017 and later. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or later. It's found at the top of the table of contents on this page. ::: moniker-end ::: moniker range=">=msvc-150" diff --git a/docs/build-insights/reference/sdk/cpp-event-data-types/compiler-pass.md b/docs/build-insights/reference/sdk/cpp-event-data-types/compiler-pass.md index 6342fd5e100..b98998fd390 100644 --- a/docs/build-insights/reference/sdk/cpp-event-data-types/compiler-pass.md +++ b/docs/build-insights/reference/sdk/cpp-event-data-types/compiler-pass.md @@ -8,7 +8,7 @@ helpviewer_keywords: ["C++ Build Insights", "C++ Build Insights SDK", "CompilerP ::: moniker range="<=msvc-140" -The C++ Build Insights SDK is compatible with Visual Studio 2017 and above. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or Visual Studio 2019. It's found at the top of the table of contents on this page. +The C++ Build Insights SDK is compatible with Visual Studio 2017 and later. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or later. It's found at the top of the table of contents on this page. ::: moniker-end ::: moniker range=">=msvc-150" diff --git a/docs/build-insights/reference/sdk/cpp-event-data-types/compiler.md b/docs/build-insights/reference/sdk/cpp-event-data-types/compiler.md index 6b8e9cfe64f..12cc382a395 100644 --- a/docs/build-insights/reference/sdk/cpp-event-data-types/compiler.md +++ b/docs/build-insights/reference/sdk/cpp-event-data-types/compiler.md @@ -8,7 +8,7 @@ helpviewer_keywords: ["C++ Build Insights", "C++ Build Insights SDK", "Compiler" ::: moniker range="<=msvc-140" -The C++ Build Insights SDK is compatible with Visual Studio 2017 and above. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or Visual Studio 2019. It's found at the top of the table of contents on this page. +The C++ Build Insights SDK is compatible with Visual Studio 2017 and later. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or later. It's found at the top of the table of contents on this page. ::: moniker-end ::: moniker range=">=msvc-150" diff --git a/docs/build-insights/reference/sdk/cpp-event-data-types/environment-variable.md b/docs/build-insights/reference/sdk/cpp-event-data-types/environment-variable.md index 2e8b32922ec..7265d140e1f 100644 --- a/docs/build-insights/reference/sdk/cpp-event-data-types/environment-variable.md +++ b/docs/build-insights/reference/sdk/cpp-event-data-types/environment-variable.md @@ -8,7 +8,7 @@ helpviewer_keywords: ["C++ Build Insights", "C++ Build Insights SDK", "Environme ::: moniker range="<=msvc-140" -The C++ Build Insights SDK is compatible with Visual Studio 2017 and above. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or Visual Studio 2019. It's found at the top of the table of contents on this page. +The C++ Build Insights SDK is compatible with Visual Studio 2017 and later. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or later. It's found at the top of the table of contents on this page. ::: moniker-end ::: moniker range=">=msvc-150" diff --git a/docs/build-insights/reference/sdk/cpp-event-data-types/event-group.md b/docs/build-insights/reference/sdk/cpp-event-data-types/event-group.md index e68ba3afcfd..0329689f4c0 100644 --- a/docs/build-insights/reference/sdk/cpp-event-data-types/event-group.md +++ b/docs/build-insights/reference/sdk/cpp-event-data-types/event-group.md @@ -8,7 +8,7 @@ helpviewer_keywords: ["C++ Build Insights", "C++ Build Insights SDK", "EventGrou ::: moniker range="<=msvc-140" -The C++ Build Insights SDK is compatible with Visual Studio 2017 and above. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or Visual Studio 2019. It's found at the top of the table of contents on this page. +The C++ Build Insights SDK is compatible with Visual Studio 2017 and later. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or later. It's found at the top of the table of contents on this page. ::: moniker-end ::: moniker range=">=msvc-150" diff --git a/docs/build-insights/reference/sdk/cpp-event-data-types/event-stack.md b/docs/build-insights/reference/sdk/cpp-event-data-types/event-stack.md index f87fd702503..7b642755497 100644 --- a/docs/build-insights/reference/sdk/cpp-event-data-types/event-stack.md +++ b/docs/build-insights/reference/sdk/cpp-event-data-types/event-stack.md @@ -8,7 +8,7 @@ helpviewer_keywords: ["C++ Build Insights", "C++ Build Insights SDK", "EventStac ::: moniker range="<=msvc-140" -The C++ Build Insights SDK is compatible with Visual Studio 2017 and above. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or Visual Studio 2019. It's found at the top of the table of contents on this page. +The C++ Build Insights SDK is compatible with Visual Studio 2017 and later. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or later. It's found at the top of the table of contents on this page. ::: moniker-end ::: moniker range=">=msvc-150" diff --git a/docs/build-insights/reference/sdk/cpp-event-data-types/event.md b/docs/build-insights/reference/sdk/cpp-event-data-types/event.md index df732635604..f8f89269172 100644 --- a/docs/build-insights/reference/sdk/cpp-event-data-types/event.md +++ b/docs/build-insights/reference/sdk/cpp-event-data-types/event.md @@ -8,7 +8,7 @@ helpviewer_keywords: ["C++ Build Insights", "C++ Build Insights SDK", "Event", " ::: moniker range="<=msvc-140" -The C++ Build Insights SDK is compatible with Visual Studio 2017 and above. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or Visual Studio 2019. It's found at the top of the table of contents on this page. +The C++ Build Insights SDK is compatible with Visual Studio 2017 and later. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or later. It's found at the top of the table of contents on this page. ::: moniker-end ::: moniker range=">=msvc-150" diff --git a/docs/build-insights/reference/sdk/cpp-event-data-types/executable-image-output.md b/docs/build-insights/reference/sdk/cpp-event-data-types/executable-image-output.md index 3cd217107fe..850aea985c1 100644 --- a/docs/build-insights/reference/sdk/cpp-event-data-types/executable-image-output.md +++ b/docs/build-insights/reference/sdk/cpp-event-data-types/executable-image-output.md @@ -8,7 +8,7 @@ helpviewer_keywords: ["C++ Build Insights", "C++ Build Insights SDK", "Executabl ::: moniker range="<=msvc-140" -The C++ Build Insights SDK is compatible with Visual Studio 2017 and above. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or Visual Studio 2019. It's found at the top of the table of contents on this page. +The C++ Build Insights SDK is compatible with Visual Studio 2017 and later. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or later. It's found at the top of the table of contents on this page. ::: moniker-end ::: moniker range=">=msvc-150" diff --git a/docs/build-insights/reference/sdk/cpp-event-data-types/exp-output.md b/docs/build-insights/reference/sdk/cpp-event-data-types/exp-output.md index 778f1557388..179919e9a55 100644 --- a/docs/build-insights/reference/sdk/cpp-event-data-types/exp-output.md +++ b/docs/build-insights/reference/sdk/cpp-event-data-types/exp-output.md @@ -8,7 +8,7 @@ helpviewer_keywords: ["C++ Build Insights", "C++ Build Insights SDK", "ExpOutput ::: moniker range="<=msvc-140" -The C++ Build Insights SDK is compatible with Visual Studio 2017 and above. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or Visual Studio 2019. It's found at the top of the table of contents on this page. +The C++ Build Insights SDK is compatible with Visual Studio 2017 and later. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or later. It's found at the top of the table of contents on this page. ::: moniker-end ::: moniker range=">=msvc-150" diff --git a/docs/build-insights/reference/sdk/cpp-event-data-types/file-input.md b/docs/build-insights/reference/sdk/cpp-event-data-types/file-input.md index 4d09203476a..74ba8fc4ce6 100644 --- a/docs/build-insights/reference/sdk/cpp-event-data-types/file-input.md +++ b/docs/build-insights/reference/sdk/cpp-event-data-types/file-input.md @@ -8,7 +8,7 @@ helpviewer_keywords: ["C++ Build Insights", "C++ Build Insights SDK", "FileInput ::: moniker range="<=msvc-140" -The C++ Build Insights SDK is compatible with Visual Studio 2017 and above. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or Visual Studio 2019. It's found at the top of the table of contents on this page. +The C++ Build Insights SDK is compatible with Visual Studio 2017 and later. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or later. It's found at the top of the table of contents on this page. ::: moniker-end ::: moniker range=">=msvc-150" diff --git a/docs/build-insights/reference/sdk/cpp-event-data-types/file-output.md b/docs/build-insights/reference/sdk/cpp-event-data-types/file-output.md index 2806b5c27ec..6772fe813e9 100644 --- a/docs/build-insights/reference/sdk/cpp-event-data-types/file-output.md +++ b/docs/build-insights/reference/sdk/cpp-event-data-types/file-output.md @@ -8,7 +8,7 @@ helpviewer_keywords: ["C++ Build Insights", "C++ Build Insights SDK", "FileOutpu ::: moniker range="<=msvc-140" -The C++ Build Insights SDK is compatible with Visual Studio 2017 and above. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or Visual Studio 2019. It's found at the top of the table of contents on this page. +The C++ Build Insights SDK is compatible with Visual Studio 2017 and later. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or later. It's found at the top of the table of contents on this page. ::: moniker-end ::: moniker range=">=msvc-150" diff --git a/docs/build-insights/reference/sdk/cpp-event-data-types/force-inlinee.md b/docs/build-insights/reference/sdk/cpp-event-data-types/force-inlinee.md index d22e076adda..edd2ae4ddf3 100644 --- a/docs/build-insights/reference/sdk/cpp-event-data-types/force-inlinee.md +++ b/docs/build-insights/reference/sdk/cpp-event-data-types/force-inlinee.md @@ -8,7 +8,7 @@ helpviewer_keywords: ["C++ Build Insights", "C++ Build Insights SDK", "ForceInli ::: moniker range="<=msvc-140" -The C++ Build Insights SDK is compatible with Visual Studio 2017 and above. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or Visual Studio 2019. It's found at the top of the table of contents on this page. +The C++ Build Insights SDK is compatible with Visual Studio 2017 and later. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or later. It's found at the top of the table of contents on this page. ::: moniker-end ::: moniker range=">=msvc-150" diff --git a/docs/build-insights/reference/sdk/cpp-event-data-types/front-end-file-group.md b/docs/build-insights/reference/sdk/cpp-event-data-types/front-end-file-group.md index 89cce934ec2..d6a370160f1 100644 --- a/docs/build-insights/reference/sdk/cpp-event-data-types/front-end-file-group.md +++ b/docs/build-insights/reference/sdk/cpp-event-data-types/front-end-file-group.md @@ -8,7 +8,7 @@ helpviewer_keywords: ["C++ Build Insights", "C++ Build Insights SDK", "FrontEndF ::: moniker range="<=msvc-140" -The C++ Build Insights SDK is compatible with Visual Studio 2017 and above. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or Visual Studio 2019. It's found at the top of the table of contents on this page. +The C++ Build Insights SDK is compatible with Visual Studio 2017 and later. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or later. It's found at the top of the table of contents on this page. ::: moniker-end ::: moniker range=">=msvc-150" diff --git a/docs/build-insights/reference/sdk/cpp-event-data-types/front-end-file.md b/docs/build-insights/reference/sdk/cpp-event-data-types/front-end-file.md index efcced34c3d..6cf0901f5e2 100644 --- a/docs/build-insights/reference/sdk/cpp-event-data-types/front-end-file.md +++ b/docs/build-insights/reference/sdk/cpp-event-data-types/front-end-file.md @@ -8,7 +8,7 @@ helpviewer_keywords: ["C++ Build Insights", "C++ Build Insights SDK", "FrontEndF ::: moniker range="<=msvc-140" -The C++ Build Insights SDK is compatible with Visual Studio 2017 and above. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or Visual Studio 2019. It's found at the top of the table of contents on this page. +The C++ Build Insights SDK is compatible with Visual Studio 2017 and later. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or later. It's found at the top of the table of contents on this page. ::: moniker-end ::: moniker range=">=msvc-150" diff --git a/docs/build-insights/reference/sdk/cpp-event-data-types/front-end-pass.md b/docs/build-insights/reference/sdk/cpp-event-data-types/front-end-pass.md index 23453b45c90..8d61fc735d5 100644 --- a/docs/build-insights/reference/sdk/cpp-event-data-types/front-end-pass.md +++ b/docs/build-insights/reference/sdk/cpp-event-data-types/front-end-pass.md @@ -8,7 +8,7 @@ helpviewer_keywords: ["C++ Build Insights", "C++ Build Insights SDK", "FrontEndP ::: moniker range="<=msvc-140" -The C++ Build Insights SDK is compatible with Visual Studio 2017 and above. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or Visual Studio 2019. It's found at the top of the table of contents on this page. +The C++ Build Insights SDK is compatible with Visual Studio 2017 and later. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or later. It's found at the top of the table of contents on this page. ::: moniker-end ::: moniker range=">=msvc-150" diff --git a/docs/build-insights/reference/sdk/cpp-event-data-types/function.md b/docs/build-insights/reference/sdk/cpp-event-data-types/function.md index 094719677a6..8d15a5ce989 100644 --- a/docs/build-insights/reference/sdk/cpp-event-data-types/function.md +++ b/docs/build-insights/reference/sdk/cpp-event-data-types/function.md @@ -8,7 +8,7 @@ helpviewer_keywords: ["C++ Build Insights", "C++ Build Insights SDK", "Function" ::: moniker range="<=msvc-140" -The C++ Build Insights SDK is compatible with Visual Studio 2017 and above. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or Visual Studio 2019. It's found at the top of the table of contents on this page. +The C++ Build Insights SDK is compatible with Visual Studio 2017 and later. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or later. It's found at the top of the table of contents on this page. ::: moniker-end ::: moniker range=">=msvc-150" diff --git a/docs/build-insights/reference/sdk/cpp-event-data-types/header-unit.md b/docs/build-insights/reference/sdk/cpp-event-data-types/header-unit.md index 3c28c9fc497..d94130ba308 100644 --- a/docs/build-insights/reference/sdk/cpp-event-data-types/header-unit.md +++ b/docs/build-insights/reference/sdk/cpp-event-data-types/header-unit.md @@ -8,7 +8,7 @@ helpviewer_keywords: ["C++ Build Insights", "C++ Build Insights SDK", "HeaderUni ::: moniker range="<=msvc-140" -The C++ Build Insights SDK is compatible with Visual Studio 2017 and above. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or Visual Studio 2019. It's found at the top of the table of contents on this page. +The C++ Build Insights SDK is compatible with Visual Studio 2017 and later. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or later. It's found at the top of the table of contents on this page. ::: moniker-end ::: moniker range=">=msvc-150" diff --git a/docs/build-insights/reference/sdk/cpp-event-data-types/imp-lib-output.md b/docs/build-insights/reference/sdk/cpp-event-data-types/imp-lib-output.md index 94c6ab83447..88b5bcdbedc 100644 --- a/docs/build-insights/reference/sdk/cpp-event-data-types/imp-lib-output.md +++ b/docs/build-insights/reference/sdk/cpp-event-data-types/imp-lib-output.md @@ -8,7 +8,7 @@ helpviewer_keywords: ["C++ Build Insights", "C++ Build Insights SDK", "ImpLibOut ::: moniker range="<=msvc-140" -The C++ Build Insights SDK is compatible with Visual Studio 2017 and above. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or Visual Studio 2019. It's found at the top of the table of contents on this page. +The C++ Build Insights SDK is compatible with Visual Studio 2017 and later. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or later. It's found at the top of the table of contents on this page. ::: moniker-end ::: moniker range=">=msvc-150" diff --git a/docs/build-insights/reference/sdk/cpp-event-data-types/invocation-group.md b/docs/build-insights/reference/sdk/cpp-event-data-types/invocation-group.md index 80282379624..6fdae35fd45 100644 --- a/docs/build-insights/reference/sdk/cpp-event-data-types/invocation-group.md +++ b/docs/build-insights/reference/sdk/cpp-event-data-types/invocation-group.md @@ -8,7 +8,7 @@ helpviewer_keywords: ["C++ Build Insights", "C++ Build Insights SDK", "Invocatio ::: moniker range="<=msvc-140" -The C++ Build Insights SDK is compatible with Visual Studio 2017 and above. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or Visual Studio 2019. It's found at the top of the table of contents on this page. +The C++ Build Insights SDK is compatible with Visual Studio 2017 and later. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or later. It's found at the top of the table of contents on this page. ::: moniker-end ::: moniker range=">=msvc-150" diff --git a/docs/build-insights/reference/sdk/cpp-event-data-types/invocation.md b/docs/build-insights/reference/sdk/cpp-event-data-types/invocation.md index 01d7d5144a6..0006c06a835 100644 --- a/docs/build-insights/reference/sdk/cpp-event-data-types/invocation.md +++ b/docs/build-insights/reference/sdk/cpp-event-data-types/invocation.md @@ -8,7 +8,7 @@ helpviewer_keywords: ["C++ Build Insights", "C++ Build Insights SDK", "Invocatio ::: moniker range="<=msvc-140" -The C++ Build Insights SDK is compatible with Visual Studio 2017 and above. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or Visual Studio 2019. It's found at the top of the table of contents on this page. +The C++ Build Insights SDK is compatible with Visual Studio 2017 and later. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or later. It's found at the top of the table of contents on this page. ::: moniker-end ::: moniker range=">=msvc-150" diff --git a/docs/build-insights/reference/sdk/cpp-event-data-types/lib-output.md b/docs/build-insights/reference/sdk/cpp-event-data-types/lib-output.md index eeb5162255b..aec337bdb0d 100644 --- a/docs/build-insights/reference/sdk/cpp-event-data-types/lib-output.md +++ b/docs/build-insights/reference/sdk/cpp-event-data-types/lib-output.md @@ -8,7 +8,7 @@ helpviewer_keywords: ["C++ Build Insights", "C++ Build Insights SDK", "LibOutput ::: moniker range="<=msvc-140" -The C++ Build Insights SDK is compatible with Visual Studio 2017 and above. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or Visual Studio 2019. It's found at the top of the table of contents on this page. +The C++ Build Insights SDK is compatible with Visual Studio 2017 and later. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or later. It's found at the top of the table of contents on this page. ::: moniker-end ::: moniker range=">=msvc-150" diff --git a/docs/build-insights/reference/sdk/cpp-event-data-types/linker-group.md b/docs/build-insights/reference/sdk/cpp-event-data-types/linker-group.md index a51e1850f56..ee1feada4de 100644 --- a/docs/build-insights/reference/sdk/cpp-event-data-types/linker-group.md +++ b/docs/build-insights/reference/sdk/cpp-event-data-types/linker-group.md @@ -8,7 +8,7 @@ helpviewer_keywords: ["C++ Build Insights", "C++ Build Insights SDK", "LinkerGro ::: moniker range="<=msvc-140" -The C++ Build Insights SDK is compatible with Visual Studio 2017 and above. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or Visual Studio 2019. It's found at the top of the table of contents on this page. +The C++ Build Insights SDK is compatible with Visual Studio 2017 and later. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or later. It's found at the top of the table of contents on this page. ::: moniker-end ::: moniker range=">=msvc-150" diff --git a/docs/build-insights/reference/sdk/cpp-event-data-types/linker-pass.md b/docs/build-insights/reference/sdk/cpp-event-data-types/linker-pass.md index 16fde07fe35..d0219af45ba 100644 --- a/docs/build-insights/reference/sdk/cpp-event-data-types/linker-pass.md +++ b/docs/build-insights/reference/sdk/cpp-event-data-types/linker-pass.md @@ -8,7 +8,7 @@ helpviewer_keywords: ["C++ Build Insights", "C++ Build Insights SDK", "LinkerPas ::: moniker range="<=msvc-140" -The C++ Build Insights SDK is compatible with Visual Studio 2017 and above. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or Visual Studio 2019. It's found at the top of the table of contents on this page. +The C++ Build Insights SDK is compatible with Visual Studio 2017 and later. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or later. It's found at the top of the table of contents on this page. ::: moniker-end ::: moniker range=">=msvc-150" diff --git a/docs/build-insights/reference/sdk/cpp-event-data-types/linker.md b/docs/build-insights/reference/sdk/cpp-event-data-types/linker.md index 683aaaec434..4275f822e44 100644 --- a/docs/build-insights/reference/sdk/cpp-event-data-types/linker.md +++ b/docs/build-insights/reference/sdk/cpp-event-data-types/linker.md @@ -8,7 +8,7 @@ helpviewer_keywords: ["C++ Build Insights", "C++ Build Insights SDK", "Linker", ::: moniker range="<=msvc-140" -The C++ Build Insights SDK is compatible with Visual Studio 2017 and above. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or Visual Studio 2019. It's found at the top of the table of contents on this page. +The C++ Build Insights SDK is compatible with Visual Studio 2017 and later. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or later. It's found at the top of the table of contents on this page. ::: moniker-end ::: moniker range=">=msvc-150" diff --git a/docs/build-insights/reference/sdk/cpp-event-data-types/ltcg.md b/docs/build-insights/reference/sdk/cpp-event-data-types/ltcg.md index f049e4be9d7..8895f29552a 100644 --- a/docs/build-insights/reference/sdk/cpp-event-data-types/ltcg.md +++ b/docs/build-insights/reference/sdk/cpp-event-data-types/ltcg.md @@ -8,7 +8,7 @@ helpviewer_keywords: ["C++ Build Insights", "C++ Build Insights SDK", "LTCG", "t ::: moniker range="<=msvc-140" -The C++ Build Insights SDK is compatible with Visual Studio 2017 and above. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or Visual Studio 2019. It's found at the top of the table of contents on this page. +The C++ Build Insights SDK is compatible with Visual Studio 2017 and later. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or later. It's found at the top of the table of contents on this page. ::: moniker-end ::: moniker range=">=msvc-150" diff --git a/docs/build-insights/reference/sdk/cpp-event-data-types/module.md b/docs/build-insights/reference/sdk/cpp-event-data-types/module.md index 53f1b4adb24..cbefd56200d 100644 --- a/docs/build-insights/reference/sdk/cpp-event-data-types/module.md +++ b/docs/build-insights/reference/sdk/cpp-event-data-types/module.md @@ -8,7 +8,7 @@ helpviewer_keywords: ["C++ Build Insights", "C++ Build Insights SDK", "Module", ::: moniker range="<=msvc-140" -The C++ Build Insights SDK is compatible with Visual Studio 2017 and above. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or Visual Studio 2019. It's found at the top of the table of contents on this page. +The C++ Build Insights SDK is compatible with Visual Studio 2017 and later. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or later. It's found at the top of the table of contents on this page. ::: moniker-end ::: moniker range=">=msvc-150" diff --git a/docs/build-insights/reference/sdk/cpp-event-data-types/obj-output.md b/docs/build-insights/reference/sdk/cpp-event-data-types/obj-output.md index e9f2ce5793c..45c53b88f91 100644 --- a/docs/build-insights/reference/sdk/cpp-event-data-types/obj-output.md +++ b/docs/build-insights/reference/sdk/cpp-event-data-types/obj-output.md @@ -8,7 +8,7 @@ helpviewer_keywords: ["C++ Build Insights", "C++ Build Insights SDK", "ObjOutput ::: moniker range="<=msvc-140" -The C++ Build Insights SDK is compatible with Visual Studio 2017 and above. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or Visual Studio 2019. It's found at the top of the table of contents on this page. +The C++ Build Insights SDK is compatible with Visual Studio 2017 and later. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or later. It's found at the top of the table of contents on this page. ::: moniker-end ::: moniker range=">=msvc-150" diff --git a/docs/build-insights/reference/sdk/cpp-event-data-types/opt-icf.md b/docs/build-insights/reference/sdk/cpp-event-data-types/opt-icf.md index f797d136139..dd1818a3aaa 100644 --- a/docs/build-insights/reference/sdk/cpp-event-data-types/opt-icf.md +++ b/docs/build-insights/reference/sdk/cpp-event-data-types/opt-icf.md @@ -8,7 +8,7 @@ helpviewer_keywords: ["C++ Build Insights", "C++ Build Insights SDK", "OptICF", ::: moniker range="<=msvc-140" -The C++ Build Insights SDK is compatible with Visual Studio 2017 and above. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or Visual Studio 2019. It's found at the top of the table of contents on this page. +The C++ Build Insights SDK is compatible with Visual Studio 2017 and later. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or later. It's found at the top of the table of contents on this page. ::: moniker-end ::: moniker range=">=msvc-150" diff --git a/docs/build-insights/reference/sdk/cpp-event-data-types/opt-lbr.md b/docs/build-insights/reference/sdk/cpp-event-data-types/opt-lbr.md index 38bde915c08..f4df6a6cdca 100644 --- a/docs/build-insights/reference/sdk/cpp-event-data-types/opt-lbr.md +++ b/docs/build-insights/reference/sdk/cpp-event-data-types/opt-lbr.md @@ -8,7 +8,7 @@ helpviewer_keywords: ["C++ Build Insights", "C++ Build Insights SDK", "OptLBR", ::: moniker range="<=msvc-140" -The C++ Build Insights SDK is compatible with Visual Studio 2017 and above. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or Visual Studio 2019. It's found at the top of the table of contents on this page. +The C++ Build Insights SDK is compatible with Visual Studio 2017 and later. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or later. It's found at the top of the table of contents on this page. ::: moniker-end ::: moniker range=">=msvc-150" diff --git a/docs/build-insights/reference/sdk/cpp-event-data-types/opt-ref.md b/docs/build-insights/reference/sdk/cpp-event-data-types/opt-ref.md index 3e3a6d14cf1..6b6b402ccd8 100644 --- a/docs/build-insights/reference/sdk/cpp-event-data-types/opt-ref.md +++ b/docs/build-insights/reference/sdk/cpp-event-data-types/opt-ref.md @@ -8,7 +8,7 @@ helpviewer_keywords: ["C++ Build Insights", "C++ Build Insights SDK", "OptRef", ::: moniker range="<=msvc-140" -The C++ Build Insights SDK is compatible with Visual Studio 2017 and above. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or Visual Studio 2019. It's found at the top of the table of contents on this page. +The C++ Build Insights SDK is compatible with Visual Studio 2017 and later. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or later. It's found at the top of the table of contents on this page. ::: moniker-end ::: moniker range=">=msvc-150" diff --git a/docs/build-insights/reference/sdk/cpp-event-data-types/pass1.md b/docs/build-insights/reference/sdk/cpp-event-data-types/pass1.md index 7d0036431af..fc8d17f3cd9 100644 --- a/docs/build-insights/reference/sdk/cpp-event-data-types/pass1.md +++ b/docs/build-insights/reference/sdk/cpp-event-data-types/pass1.md @@ -8,7 +8,7 @@ helpviewer_keywords: ["C++ Build Insights", "C++ Build Insights SDK", "Pass1", " ::: moniker range="<=msvc-140" -The C++ Build Insights SDK is compatible with Visual Studio 2017 and above. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or Visual Studio 2019. It's found at the top of the table of contents on this page. +The C++ Build Insights SDK is compatible with Visual Studio 2017 and later. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or later. It's found at the top of the table of contents on this page. ::: moniker-end ::: moniker range=">=msvc-150" diff --git a/docs/build-insights/reference/sdk/cpp-event-data-types/pass2.md b/docs/build-insights/reference/sdk/cpp-event-data-types/pass2.md index 793d91826f3..c99c01f5964 100644 --- a/docs/build-insights/reference/sdk/cpp-event-data-types/pass2.md +++ b/docs/build-insights/reference/sdk/cpp-event-data-types/pass2.md @@ -8,7 +8,7 @@ helpviewer_keywords: ["C++ Build Insights", "C++ Build Insights SDK", "Pass2", " ::: moniker range="<=msvc-140" -The C++ Build Insights SDK is compatible with Visual Studio 2017 and above. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or Visual Studio 2019. It's found at the top of the table of contents on this page. +The C++ Build Insights SDK is compatible with Visual Studio 2017 and later. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or later. It's found at the top of the table of contents on this page. ::: moniker-end ::: moniker range=">=msvc-150" diff --git a/docs/build-insights/reference/sdk/cpp-event-data-types/pre-ltcg-opt-ref.md b/docs/build-insights/reference/sdk/cpp-event-data-types/pre-ltcg-opt-ref.md index 39129c4446d..61bae8e8180 100644 --- a/docs/build-insights/reference/sdk/cpp-event-data-types/pre-ltcg-opt-ref.md +++ b/docs/build-insights/reference/sdk/cpp-event-data-types/pre-ltcg-opt-ref.md @@ -8,7 +8,7 @@ helpviewer_keywords: ["C++ Build Insights", "C++ Build Insights SDK", "PreLTCGOp ::: moniker range="<=msvc-140" -The C++ Build Insights SDK is compatible with Visual Studio 2017 and above. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or Visual Studio 2019. It's found at the top of the table of contents on this page. +The C++ Build Insights SDK is compatible with Visual Studio 2017 and later. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or later. It's found at the top of the table of contents on this page. ::: moniker-end ::: moniker range=">=msvc-150" diff --git a/docs/build-insights/reference/sdk/cpp-event-data-types/precompiled-header.md b/docs/build-insights/reference/sdk/cpp-event-data-types/precompiled-header.md index cbb03d8df81..d2dcf369bdb 100644 --- a/docs/build-insights/reference/sdk/cpp-event-data-types/precompiled-header.md +++ b/docs/build-insights/reference/sdk/cpp-event-data-types/precompiled-header.md @@ -8,7 +8,7 @@ helpviewer_keywords: ["C++ Build Insights", "C++ Build Insights SDK", "Precompil ::: moniker range="<=msvc-140" -The C++ Build Insights SDK is compatible with Visual Studio 2017 and above. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or Visual Studio 2019. It's found at the top of the table of contents on this page. +The C++ Build Insights SDK is compatible with Visual Studio 2017 and later. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or later. It's found at the top of the table of contents on this page. ::: moniker-end ::: moniker range=">=msvc-150" diff --git a/docs/build-insights/reference/sdk/cpp-event-data-types/raw-event.md b/docs/build-insights/reference/sdk/cpp-event-data-types/raw-event.md index 86083f6154a..2d767ed2805 100644 --- a/docs/build-insights/reference/sdk/cpp-event-data-types/raw-event.md +++ b/docs/build-insights/reference/sdk/cpp-event-data-types/raw-event.md @@ -8,7 +8,7 @@ helpviewer_keywords: ["C++ Build Insights", "C++ Build Insights SDK", "RawEvent" ::: moniker range="<=msvc-140" -The C++ Build Insights SDK is compatible with Visual Studio 2017 and above. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or Visual Studio 2019. It's found at the top of the table of contents on this page. +The C++ Build Insights SDK is compatible with Visual Studio 2017 and later. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or later. It's found at the top of the table of contents on this page. ::: moniker-end ::: moniker range=">=msvc-150" diff --git a/docs/build-insights/reference/sdk/cpp-event-data-types/simple-event.md b/docs/build-insights/reference/sdk/cpp-event-data-types/simple-event.md index c19a4005707..b811c0bab2f 100644 --- a/docs/build-insights/reference/sdk/cpp-event-data-types/simple-event.md +++ b/docs/build-insights/reference/sdk/cpp-event-data-types/simple-event.md @@ -8,7 +8,7 @@ helpviewer_keywords: ["C++ Build Insights", "C++ Build Insights SDK", "SimpleEve ::: moniker range="<=msvc-140" -The C++ Build Insights SDK is compatible with Visual Studio 2017 and above. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or Visual Studio 2019. It's found at the top of the table of contents on this page. +The C++ Build Insights SDK is compatible with Visual Studio 2017 and later. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or later. It's found at the top of the table of contents on this page. ::: moniker-end ::: moniker range=">=msvc-150" diff --git a/docs/build-insights/reference/sdk/cpp-event-data-types/symbol-name.md b/docs/build-insights/reference/sdk/cpp-event-data-types/symbol-name.md index 21e57ba1441..98b10ece5b7 100644 --- a/docs/build-insights/reference/sdk/cpp-event-data-types/symbol-name.md +++ b/docs/build-insights/reference/sdk/cpp-event-data-types/symbol-name.md @@ -8,7 +8,7 @@ helpviewer_keywords: ["C++ Build Insights", "C++ Build Insights SDK", "SymbolNam ::: moniker range="<=msvc-140" -The C++ Build Insights SDK is compatible with Visual Studio 2017 and above. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or Visual Studio 2019. It's found at the top of the table of contents on this page. +The C++ Build Insights SDK is compatible with Visual Studio 2017 and later. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or later. It's found at the top of the table of contents on this page. ::: moniker-end ::: moniker range=">=msvc-150" diff --git a/docs/build-insights/reference/sdk/cpp-event-data-types/template-instantiation-group.md b/docs/build-insights/reference/sdk/cpp-event-data-types/template-instantiation-group.md index 7cc7a8d71ed..1af54668f60 100644 --- a/docs/build-insights/reference/sdk/cpp-event-data-types/template-instantiation-group.md +++ b/docs/build-insights/reference/sdk/cpp-event-data-types/template-instantiation-group.md @@ -8,7 +8,7 @@ helpviewer_keywords: ["C++ Build Insights", "C++ Build Insights SDK", "TemplateI ::: moniker range="<=msvc-140" -The C++ Build Insights SDK is compatible with Visual Studio 2017 and above. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or Visual Studio 2019. It's found at the top of the table of contents on this page. +The C++ Build Insights SDK is compatible with Visual Studio 2017 and later. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or later. It's found at the top of the table of contents on this page. ::: moniker-end ::: moniker range=">=msvc-150" diff --git a/docs/build-insights/reference/sdk/cpp-event-data-types/template-instantiation.md b/docs/build-insights/reference/sdk/cpp-event-data-types/template-instantiation.md index e4b8a26e2d3..3729c2bebd0 100644 --- a/docs/build-insights/reference/sdk/cpp-event-data-types/template-instantiation.md +++ b/docs/build-insights/reference/sdk/cpp-event-data-types/template-instantiation.md @@ -8,7 +8,7 @@ helpviewer_keywords: ["C++ Build Insights", "C++ Build Insights SDK", "TemplateI ::: moniker range="<=msvc-140" -The C++ Build Insights SDK is compatible with Visual Studio 2017 and above. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or Visual Studio 2019. It's found at the top of the table of contents on this page. +The C++ Build Insights SDK is compatible with Visual Studio 2017 and later. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or later. It's found at the top of the table of contents on this page. ::: moniker-end ::: moniker range=">=msvc-150" diff --git a/docs/build-insights/reference/sdk/cpp-event-data-types/thread.md b/docs/build-insights/reference/sdk/cpp-event-data-types/thread.md index 4bfaf7d8d7e..290d7e82754 100644 --- a/docs/build-insights/reference/sdk/cpp-event-data-types/thread.md +++ b/docs/build-insights/reference/sdk/cpp-event-data-types/thread.md @@ -8,7 +8,7 @@ helpviewer_keywords: ["C++ Build Insights", "C++ Build Insights SDK", "Thread", ::: moniker range="<=msvc-140" -The C++ Build Insights SDK is compatible with Visual Studio 2017 and above. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or Visual Studio 2019. It's found at the top of the table of contents on this page. +The C++ Build Insights SDK is compatible with Visual Studio 2017 and later. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or later. It's found at the top of the table of contents on this page. ::: moniker-end ::: moniker range=">=msvc-150" diff --git a/docs/build-insights/reference/sdk/cpp-event-data-types/top-down.md b/docs/build-insights/reference/sdk/cpp-event-data-types/top-down.md index 1e1b264cf60..ecf52e8165b 100644 --- a/docs/build-insights/reference/sdk/cpp-event-data-types/top-down.md +++ b/docs/build-insights/reference/sdk/cpp-event-data-types/top-down.md @@ -8,7 +8,7 @@ helpviewer_keywords: ["C++ Build Insights", "C++ Build Insights SDK", "TopDown", ::: moniker range="<=msvc-140" -The C++ Build Insights SDK is compatible with Visual Studio 2017 and above. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or Visual Studio 2019. It's found at the top of the table of contents on this page. +The C++ Build Insights SDK is compatible with Visual Studio 2017 and later. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or later. It's found at the top of the table of contents on this page. ::: moniker-end ::: moniker range=">=msvc-150" diff --git a/docs/build-insights/reference/sdk/cpp-event-data-types/trace-info.md b/docs/build-insights/reference/sdk/cpp-event-data-types/trace-info.md index 4172cc60601..918f0ecba93 100644 --- a/docs/build-insights/reference/sdk/cpp-event-data-types/trace-info.md +++ b/docs/build-insights/reference/sdk/cpp-event-data-types/trace-info.md @@ -8,7 +8,7 @@ helpviewer_keywords: ["C++ Build Insights", "C++ Build Insights SDK", "TraceInfo ::: moniker range="<=msvc-140" -The C++ Build Insights SDK is compatible with Visual Studio 2017 and above. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or Visual Studio 2019. It's found at the top of the table of contents on this page. +The C++ Build Insights SDK is compatible with Visual Studio 2017 and later. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or later. It's found at the top of the table of contents on this page. ::: moniker-end ::: moniker range=">=msvc-150" diff --git a/docs/build-insights/reference/sdk/cpp-event-data-types/translation-unit-type.md b/docs/build-insights/reference/sdk/cpp-event-data-types/translation-unit-type.md index 6ccef5803ef..985dc0d3d41 100644 --- a/docs/build-insights/reference/sdk/cpp-event-data-types/translation-unit-type.md +++ b/docs/build-insights/reference/sdk/cpp-event-data-types/translation-unit-type.md @@ -8,7 +8,7 @@ helpviewer_keywords: ["C++ Build Insights", "C++ Build Insights SDK", "Translati ::: moniker range="<=msvc-140" -The C++ Build Insights SDK is compatible with Visual Studio 2017 and above. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or Visual Studio 2019. It's found at the top of the table of contents on this page. +The C++ Build Insights SDK is compatible with Visual Studio 2017 and later. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or later. It's found at the top of the table of contents on this page. ::: moniker-end ::: moniker range=">=msvc-150" diff --git a/docs/build-insights/reference/sdk/cpp-event-data-types/whole-program-analysis.md b/docs/build-insights/reference/sdk/cpp-event-data-types/whole-program-analysis.md index 4dbfbb94251..1afce1de2b7 100644 --- a/docs/build-insights/reference/sdk/cpp-event-data-types/whole-program-analysis.md +++ b/docs/build-insights/reference/sdk/cpp-event-data-types/whole-program-analysis.md @@ -8,7 +8,7 @@ helpviewer_keywords: ["C++ Build Insights", "C++ Build Insights SDK", "WholeProg ::: moniker range="<=msvc-140" -The C++ Build Insights SDK is compatible with Visual Studio 2017 and above. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or Visual Studio 2019. It's found at the top of the table of contents on this page. +The C++ Build Insights SDK is compatible with Visual Studio 2017 and later. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or later. It's found at the top of the table of contents on this page. ::: moniker-end ::: moniker range=">=msvc-150" diff --git a/docs/build-insights/reference/sdk/event-table.md b/docs/build-insights/reference/sdk/event-table.md index b40f6f78e76..2a2993364ff 100644 --- a/docs/build-insights/reference/sdk/event-table.md +++ b/docs/build-insights/reference/sdk/event-table.md @@ -8,7 +8,7 @@ helpviewer_keywords: ["C++ Build Insights", "C++ Build Insights SDK", "Events", ::: moniker range="<=msvc-140" -The C++ Build Insights SDK is compatible with Visual Studio 2017 and above. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or Visual Studio 2019. It's found at the top of the table of contents on this page. +The C++ Build Insights SDK is compatible with Visual Studio 2017 and later. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or later. It's found at the top of the table of contents on this page. ::: moniker-end ::: moniker range=">=msvc-150" diff --git a/docs/build-insights/reference/sdk/functions/analyze-a.md b/docs/build-insights/reference/sdk/functions/analyze-a.md index c0326a8f65a..2f690eaa29f 100644 --- a/docs/build-insights/reference/sdk/functions/analyze-a.md +++ b/docs/build-insights/reference/sdk/functions/analyze-a.md @@ -8,7 +8,7 @@ helpviewer_keywords: ["C++ Build Insights", "C++ Build Insights SDK", "AnalyzeA" ::: moniker range="<=msvc-140" -The C++ Build Insights SDK is compatible with Visual Studio 2017 and above. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or Visual Studio 2019. It's found at the top of the table of contents on this page. +The C++ Build Insights SDK is compatible with Visual Studio 2017 and later. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or later. It's found at the top of the table of contents on this page. ::: moniker-end ::: moniker range=">=msvc-150" diff --git a/docs/build-insights/reference/sdk/functions/analyze-w.md b/docs/build-insights/reference/sdk/functions/analyze-w.md index 822c1b931c9..b4442cb02ed 100644 --- a/docs/build-insights/reference/sdk/functions/analyze-w.md +++ b/docs/build-insights/reference/sdk/functions/analyze-w.md @@ -8,7 +8,7 @@ helpviewer_keywords: ["C++ Build Insights", "C++ Build Insights SDK", "AnalyzeW" ::: moniker range="<=msvc-140" -The C++ Build Insights SDK is compatible with Visual Studio 2017 and above. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or Visual Studio 2019. It's found at the top of the table of contents on this page. +The C++ Build Insights SDK is compatible with Visual Studio 2017 and later. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or later. It's found at the top of the table of contents on this page. ::: moniker-end ::: moniker range=">=msvc-150" diff --git a/docs/build-insights/reference/sdk/functions/analyze.md b/docs/build-insights/reference/sdk/functions/analyze.md index 33b367ebaf3..3d2f07c585e 100644 --- a/docs/build-insights/reference/sdk/functions/analyze.md +++ b/docs/build-insights/reference/sdk/functions/analyze.md @@ -8,7 +8,7 @@ helpviewer_keywords: ["C++ Build Insights", "C++ Build Insights SDK", "Analyze", ::: moniker range="<=msvc-140" -The C++ Build Insights SDK is compatible with Visual Studio 2017 and above. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or Visual Studio 2019. It's found at the top of the table of contents on this page. +The C++ Build Insights SDK is compatible with Visual Studio 2017 and later. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or later. It's found at the top of the table of contents on this page. ::: moniker-end ::: moniker range=">=msvc-150" diff --git a/docs/build-insights/reference/sdk/functions/inject-event.md b/docs/build-insights/reference/sdk/functions/inject-event.md index 90edbd03ab1..e6425788569 100644 --- a/docs/build-insights/reference/sdk/functions/inject-event.md +++ b/docs/build-insights/reference/sdk/functions/inject-event.md @@ -8,7 +8,7 @@ helpviewer_keywords: ["C++ Build Insights", "C++ Build Insights SDK", "InjectEve ::: moniker range="<=msvc-140" -The C++ Build Insights SDK is compatible with Visual Studio 2017 and above. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or Visual Studio 2019. It's found at the top of the table of contents on this page. +The C++ Build Insights SDK is compatible with Visual Studio 2017 and later. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or later. It's found at the top of the table of contents on this page. ::: moniker-end ::: moniker range=">=msvc-150" diff --git a/docs/build-insights/reference/sdk/functions/make-dynamic-analyzer-group.md b/docs/build-insights/reference/sdk/functions/make-dynamic-analyzer-group.md index 61250353628..0f67ad4504d 100644 --- a/docs/build-insights/reference/sdk/functions/make-dynamic-analyzer-group.md +++ b/docs/build-insights/reference/sdk/functions/make-dynamic-analyzer-group.md @@ -8,7 +8,7 @@ helpviewer_keywords: ["C++ Build Insights", "C++ Build Insights SDK", "MakeDynam ::: moniker range="<=msvc-140" -The C++ Build Insights SDK is compatible with Visual Studio 2017 and above. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or Visual Studio 2019. It's found at the top of the table of contents on this page. +The C++ Build Insights SDK is compatible with Visual Studio 2017 and later. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or later. It's found at the top of the table of contents on this page. ::: moniker-end ::: moniker range=">=msvc-150" diff --git a/docs/build-insights/reference/sdk/functions/make-dynamic-relogger-group.md b/docs/build-insights/reference/sdk/functions/make-dynamic-relogger-group.md index dc581e7b9a1..97ea2529d90 100644 --- a/docs/build-insights/reference/sdk/functions/make-dynamic-relogger-group.md +++ b/docs/build-insights/reference/sdk/functions/make-dynamic-relogger-group.md @@ -8,7 +8,7 @@ helpviewer_keywords: ["C++ Build Insights", "C++ Build Insights SDK", "MakeDynam ::: moniker range="<=msvc-140" -The C++ Build Insights SDK is compatible with Visual Studio 2017 and above. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or Visual Studio 2019. It's found at the top of the table of contents on this page. +The C++ Build Insights SDK is compatible with Visual Studio 2017 and later. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or later. It's found at the top of the table of contents on this page. ::: moniker-end ::: moniker range=">=msvc-150" diff --git a/docs/build-insights/reference/sdk/functions/make-static-analyzer-group.md b/docs/build-insights/reference/sdk/functions/make-static-analyzer-group.md index ea06633d31d..49afc727187 100644 --- a/docs/build-insights/reference/sdk/functions/make-static-analyzer-group.md +++ b/docs/build-insights/reference/sdk/functions/make-static-analyzer-group.md @@ -8,7 +8,7 @@ helpviewer_keywords: ["C++ Build Insights", "C++ Build Insights SDK", "MakeStati ::: moniker range="<=msvc-140" -The C++ Build Insights SDK is compatible with Visual Studio 2017 and above. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or Visual Studio 2019. It's found at the top of the table of contents on this page. +The C++ Build Insights SDK is compatible with Visual Studio 2017 and later. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or later. It's found at the top of the table of contents on this page. ::: moniker-end ::: moniker range=">=msvc-150" diff --git a/docs/build-insights/reference/sdk/functions/make-static-relogger-group.md b/docs/build-insights/reference/sdk/functions/make-static-relogger-group.md index a800e6f7c99..1ea522b7e8d 100644 --- a/docs/build-insights/reference/sdk/functions/make-static-relogger-group.md +++ b/docs/build-insights/reference/sdk/functions/make-static-relogger-group.md @@ -8,7 +8,7 @@ helpviewer_keywords: ["C++ Build Insights", "C++ Build Insights SDK", "MakeStati ::: moniker range="<=msvc-140" -The C++ Build Insights SDK is compatible with Visual Studio 2017 and above. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or Visual Studio 2019. It's found at the top of the table of contents on this page. +The C++ Build Insights SDK is compatible with Visual Studio 2017 and later. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or later. It's found at the top of the table of contents on this page. ::: moniker-end ::: moniker range=">=msvc-150" diff --git a/docs/build-insights/reference/sdk/functions/match-event-in-member-function.md b/docs/build-insights/reference/sdk/functions/match-event-in-member-function.md index ab5b1166aa1..d0817f3dc9a 100644 --- a/docs/build-insights/reference/sdk/functions/match-event-in-member-function.md +++ b/docs/build-insights/reference/sdk/functions/match-event-in-member-function.md @@ -8,7 +8,7 @@ helpviewer_keywords: ["C++ Build Insights", "C++ Build Insights SDK", "MatchEven ::: moniker range="<=msvc-140" -The C++ Build Insights SDK is compatible with Visual Studio 2017 and above. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or Visual Studio 2019. It's found at the top of the table of contents on this page. +The C++ Build Insights SDK is compatible with Visual Studio 2017 and later. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or later. It's found at the top of the table of contents on this page. ::: moniker-end ::: moniker range=">=msvc-150" diff --git a/docs/build-insights/reference/sdk/functions/match-event-stack-in-member-function.md b/docs/build-insights/reference/sdk/functions/match-event-stack-in-member-function.md index a9ad2bb234f..2237139e8f5 100644 --- a/docs/build-insights/reference/sdk/functions/match-event-stack-in-member-function.md +++ b/docs/build-insights/reference/sdk/functions/match-event-stack-in-member-function.md @@ -8,7 +8,7 @@ helpviewer_keywords: ["C++ Build Insights", "C++ Build Insights SDK", "MatchEven ::: moniker range="<=msvc-140" -The C++ Build Insights SDK is compatible with Visual Studio 2017 and above. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or Visual Studio 2019. It's found at the top of the table of contents on this page. +The C++ Build Insights SDK is compatible with Visual Studio 2017 and later. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or later. It's found at the top of the table of contents on this page. ::: moniker-end ::: moniker range=">=msvc-150" diff --git a/docs/build-insights/reference/sdk/functions/match-event-stack.md b/docs/build-insights/reference/sdk/functions/match-event-stack.md index b3f1b757593..55a15df0fa4 100644 --- a/docs/build-insights/reference/sdk/functions/match-event-stack.md +++ b/docs/build-insights/reference/sdk/functions/match-event-stack.md @@ -8,7 +8,7 @@ helpviewer_keywords: ["C++ Build Insights", "C++ Build Insights SDK", "MatchEven ::: moniker range="<=msvc-140" -The C++ Build Insights SDK is compatible with Visual Studio 2017 and above. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or Visual Studio 2019. It's found at the top of the table of contents on this page. +The C++ Build Insights SDK is compatible with Visual Studio 2017 and later. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or later. It's found at the top of the table of contents on this page. ::: moniker-end ::: moniker range=">=msvc-150" diff --git a/docs/build-insights/reference/sdk/functions/match-event.md b/docs/build-insights/reference/sdk/functions/match-event.md index 65a738ebae1..e392c3184d9 100644 --- a/docs/build-insights/reference/sdk/functions/match-event.md +++ b/docs/build-insights/reference/sdk/functions/match-event.md @@ -8,7 +8,7 @@ helpviewer_keywords: ["C++ Build Insights", "C++ Build Insights SDK", "MatchEven ::: moniker range="<=msvc-140" -The C++ Build Insights SDK is compatible with Visual Studio 2017 and above. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or Visual Studio 2019. It's found at the top of the table of contents on this page. +The C++ Build Insights SDK is compatible with Visual Studio 2017 and later. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or later. It's found at the top of the table of contents on this page. ::: moniker-end ::: moniker range=">=msvc-150" diff --git a/docs/build-insights/reference/sdk/functions/relog-a.md b/docs/build-insights/reference/sdk/functions/relog-a.md index 166793f23b5..ca57d0fdb68 100644 --- a/docs/build-insights/reference/sdk/functions/relog-a.md +++ b/docs/build-insights/reference/sdk/functions/relog-a.md @@ -8,7 +8,7 @@ helpviewer_keywords: ["C++ Build Insights", "C++ Build Insights SDK", "RelogA", ::: moniker range="<=msvc-140" -The C++ Build Insights SDK is compatible with Visual Studio 2017 and above. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or Visual Studio 2019. It's found at the top of the table of contents on this page. +The C++ Build Insights SDK is compatible with Visual Studio 2017 and later. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or later. It's found at the top of the table of contents on this page. ::: moniker-end ::: moniker range=">=msvc-150" diff --git a/docs/build-insights/reference/sdk/functions/relog-w.md b/docs/build-insights/reference/sdk/functions/relog-w.md index 091372d548a..c4ed0ad3d9b 100644 --- a/docs/build-insights/reference/sdk/functions/relog-w.md +++ b/docs/build-insights/reference/sdk/functions/relog-w.md @@ -8,7 +8,7 @@ helpviewer_keywords: ["C++ Build Insights", "C++ Build Insights SDK", "RelogW", ::: moniker range="<=msvc-140" -The C++ Build Insights SDK is compatible with Visual Studio 2017 and above. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or Visual Studio 2019. It's found at the top of the table of contents on this page. +The C++ Build Insights SDK is compatible with Visual Studio 2017 and later. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or later. It's found at the top of the table of contents on this page. ::: moniker-end ::: moniker range=">=msvc-150" diff --git a/docs/build-insights/reference/sdk/functions/relog.md b/docs/build-insights/reference/sdk/functions/relog.md index 8567b6cf178..53fe924c8cd 100644 --- a/docs/build-insights/reference/sdk/functions/relog.md +++ b/docs/build-insights/reference/sdk/functions/relog.md @@ -8,7 +8,7 @@ helpviewer_keywords: ["C++ Build Insights", "C++ Build Insights SDK", "Relog", " ::: moniker range="<=msvc-140" -The C++ Build Insights SDK is compatible with Visual Studio 2017 and above. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or Visual Studio 2019. It's found at the top of the table of contents on this page. +The C++ Build Insights SDK is compatible with Visual Studio 2017 and later. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or later. It's found at the top of the table of contents on this page. ::: moniker-end ::: moniker range=">=msvc-150" diff --git a/docs/build-insights/reference/sdk/functions/start-tracing-session-a.md b/docs/build-insights/reference/sdk/functions/start-tracing-session-a.md index 2c9dffc90e7..117dcf7e3b3 100644 --- a/docs/build-insights/reference/sdk/functions/start-tracing-session-a.md +++ b/docs/build-insights/reference/sdk/functions/start-tracing-session-a.md @@ -8,7 +8,7 @@ helpviewer_keywords: ["C++ Build Insights", "C++ Build Insights SDK", "StartTrac ::: moniker range="<=msvc-140" -The C++ Build Insights SDK is compatible with Visual Studio 2017 and above. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or Visual Studio 2019. It's found at the top of the table of contents on this page. +The C++ Build Insights SDK is compatible with Visual Studio 2017 and later. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or later. It's found at the top of the table of contents on this page. ::: moniker-end ::: moniker range=">=msvc-150" diff --git a/docs/build-insights/reference/sdk/functions/start-tracing-session-w.md b/docs/build-insights/reference/sdk/functions/start-tracing-session-w.md index 479e3bcc510..cac3ec12023 100644 --- a/docs/build-insights/reference/sdk/functions/start-tracing-session-w.md +++ b/docs/build-insights/reference/sdk/functions/start-tracing-session-w.md @@ -8,7 +8,7 @@ helpviewer_keywords: ["C++ Build Insights", "C++ Build Insights SDK", "StartTrac ::: moniker range="<=msvc-140" -The C++ Build Insights SDK is compatible with Visual Studio 2017 and above. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or Visual Studio 2019. It's found at the top of the table of contents on this page. +The C++ Build Insights SDK is compatible with Visual Studio 2017 and later. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or later. It's found at the top of the table of contents on this page. ::: moniker-end ::: moniker range=">=msvc-150" diff --git a/docs/build-insights/reference/sdk/functions/start-tracing-session.md b/docs/build-insights/reference/sdk/functions/start-tracing-session.md index 3cfc133416b..78270e8aa09 100644 --- a/docs/build-insights/reference/sdk/functions/start-tracing-session.md +++ b/docs/build-insights/reference/sdk/functions/start-tracing-session.md @@ -8,7 +8,7 @@ helpviewer_keywords: ["C++ Build Insights", "C++ Build Insights SDK", "StartTrac ::: moniker range="<=msvc-140" -The C++ Build Insights SDK is compatible with Visual Studio 2017 and above. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or Visual Studio 2019. It's found at the top of the table of contents on this page. +The C++ Build Insights SDK is compatible with Visual Studio 2017 and later. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or later. It's found at the top of the table of contents on this page. ::: moniker-end ::: moniker range=">=msvc-150" diff --git a/docs/build-insights/reference/sdk/functions/stop-and-analyze-tracing-session-a.md b/docs/build-insights/reference/sdk/functions/stop-and-analyze-tracing-session-a.md index 24e3816509f..34d8cff6626 100644 --- a/docs/build-insights/reference/sdk/functions/stop-and-analyze-tracing-session-a.md +++ b/docs/build-insights/reference/sdk/functions/stop-and-analyze-tracing-session-a.md @@ -8,7 +8,7 @@ helpviewer_keywords: ["C++ Build Insights", "C++ Build Insights SDK", "StopAndAn ::: moniker range="<=msvc-140" -The C++ Build Insights SDK is compatible with Visual Studio 2017 and above. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or Visual Studio 2019. It's found at the top of the table of contents on this page. +The C++ Build Insights SDK is compatible with Visual Studio 2017 and later. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or later. It's found at the top of the table of contents on this page. ::: moniker-end ::: moniker range=">=msvc-150" diff --git a/docs/build-insights/reference/sdk/functions/stop-and-analyze-tracing-session-w.md b/docs/build-insights/reference/sdk/functions/stop-and-analyze-tracing-session-w.md index 7f281f5f41b..3018e6ca942 100644 --- a/docs/build-insights/reference/sdk/functions/stop-and-analyze-tracing-session-w.md +++ b/docs/build-insights/reference/sdk/functions/stop-and-analyze-tracing-session-w.md @@ -8,7 +8,7 @@ helpviewer_keywords: ["C++ Build Insights", "C++ Build Insights SDK", "StopAndAn ::: moniker range="<=msvc-140" -The C++ Build Insights SDK is compatible with Visual Studio 2017 and above. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or Visual Studio 2019. It's found at the top of the table of contents on this page. +The C++ Build Insights SDK is compatible with Visual Studio 2017 and later. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or later. It's found at the top of the table of contents on this page. ::: moniker-end ::: moniker range=">=msvc-150" diff --git a/docs/build-insights/reference/sdk/functions/stop-and-analyze-tracing-session.md b/docs/build-insights/reference/sdk/functions/stop-and-analyze-tracing-session.md index 258262d4082..fafece4a2da 100644 --- a/docs/build-insights/reference/sdk/functions/stop-and-analyze-tracing-session.md +++ b/docs/build-insights/reference/sdk/functions/stop-and-analyze-tracing-session.md @@ -8,7 +8,7 @@ helpviewer_keywords: ["C++ Build Insights", "C++ Build Insights SDK", "StopAndAn ::: moniker range="<=msvc-140" -The C++ Build Insights SDK is compatible with Visual Studio 2017 and above. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or Visual Studio 2019. It's found at the top of the table of contents on this page. +The C++ Build Insights SDK is compatible with Visual Studio 2017 and later. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or later. It's found at the top of the table of contents on this page. ::: moniker-end ::: moniker range=">=msvc-150" diff --git a/docs/build-insights/reference/sdk/functions/stop-and-relog-tracing-session-a.md b/docs/build-insights/reference/sdk/functions/stop-and-relog-tracing-session-a.md index b09f5465762..408010651ca 100644 --- a/docs/build-insights/reference/sdk/functions/stop-and-relog-tracing-session-a.md +++ b/docs/build-insights/reference/sdk/functions/stop-and-relog-tracing-session-a.md @@ -8,7 +8,7 @@ helpviewer_keywords: ["C++ Build Insights", "C++ Build Insights SDK", "StopAndRe ::: moniker range="<=msvc-140" -The C++ Build Insights SDK is compatible with Visual Studio 2017 and above. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or Visual Studio 2019. It's found at the top of the table of contents on this page. +The C++ Build Insights SDK is compatible with Visual Studio 2017 and later. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or later. It's found at the top of the table of contents on this page. ::: moniker-end ::: moniker range=">=msvc-150" diff --git a/docs/build-insights/reference/sdk/functions/stop-and-relog-tracing-session-w.md b/docs/build-insights/reference/sdk/functions/stop-and-relog-tracing-session-w.md index 665dfd4ed71..307e96dc1b7 100644 --- a/docs/build-insights/reference/sdk/functions/stop-and-relog-tracing-session-w.md +++ b/docs/build-insights/reference/sdk/functions/stop-and-relog-tracing-session-w.md @@ -8,7 +8,7 @@ helpviewer_keywords: ["C++ Build Insights", "C++ Build Insights SDK", "StopAndRe ::: moniker range="<=msvc-140" -The C++ Build Insights SDK is compatible with Visual Studio 2017 and above. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or Visual Studio 2019. It's found at the top of the table of contents on this page. +The C++ Build Insights SDK is compatible with Visual Studio 2017 and later. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or later. It's found at the top of the table of contents on this page. ::: moniker-end ::: moniker range=">=msvc-150" diff --git a/docs/build-insights/reference/sdk/functions/stop-and-relog-tracing-session.md b/docs/build-insights/reference/sdk/functions/stop-and-relog-tracing-session.md index 857a335489c..b89dc7f62f5 100644 --- a/docs/build-insights/reference/sdk/functions/stop-and-relog-tracing-session.md +++ b/docs/build-insights/reference/sdk/functions/stop-and-relog-tracing-session.md @@ -8,7 +8,7 @@ helpviewer_keywords: ["C++ Build Insights", "C++ Build Insights SDK", "StopAndRe ::: moniker range="<=msvc-140" -The C++ Build Insights SDK is compatible with Visual Studio 2017 and above. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or Visual Studio 2019. It's found at the top of the table of contents on this page. +The C++ Build Insights SDK is compatible with Visual Studio 2017 and later. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or later. It's found at the top of the table of contents on this page. ::: moniker-end ::: moniker range=">=msvc-150" diff --git a/docs/build-insights/reference/sdk/functions/stop-tracing-session-a.md b/docs/build-insights/reference/sdk/functions/stop-tracing-session-a.md index 8636f816955..46dedc00da0 100644 --- a/docs/build-insights/reference/sdk/functions/stop-tracing-session-a.md +++ b/docs/build-insights/reference/sdk/functions/stop-tracing-session-a.md @@ -8,7 +8,7 @@ helpviewer_keywords: ["C++ Build Insights", "C++ Build Insights SDK", "StopTraci ::: moniker range="<=msvc-140" -The C++ Build Insights SDK is compatible with Visual Studio 2017 and above. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or Visual Studio 2019. It's found at the top of the table of contents on this page. +The C++ Build Insights SDK is compatible with Visual Studio 2017 and later. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or later. It's found at the top of the table of contents on this page. ::: moniker-end ::: moniker range=">=msvc-150" diff --git a/docs/build-insights/reference/sdk/functions/stop-tracing-session-w.md b/docs/build-insights/reference/sdk/functions/stop-tracing-session-w.md index cc0f1adbbcb..a050b60ed3b 100644 --- a/docs/build-insights/reference/sdk/functions/stop-tracing-session-w.md +++ b/docs/build-insights/reference/sdk/functions/stop-tracing-session-w.md @@ -8,7 +8,7 @@ helpviewer_keywords: ["C++ Build Insights", "C++ Build Insights SDK", "StopTraci ::: moniker range="<=msvc-140" -The C++ Build Insights SDK is compatible with Visual Studio 2017 and above. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or Visual Studio 2019. It's found at the top of the table of contents on this page. +The C++ Build Insights SDK is compatible with Visual Studio 2017 and later. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or later. It's found at the top of the table of contents on this page. ::: moniker-end ::: moniker range=">=msvc-150" diff --git a/docs/build-insights/reference/sdk/functions/stop-tracing-session.md b/docs/build-insights/reference/sdk/functions/stop-tracing-session.md index 69f30697dee..1aa039019e9 100644 --- a/docs/build-insights/reference/sdk/functions/stop-tracing-session.md +++ b/docs/build-insights/reference/sdk/functions/stop-tracing-session.md @@ -8,7 +8,7 @@ helpviewer_keywords: ["C++ Build Insights", "C++ Build Insights SDK", "StopTraci ::: moniker range="<=msvc-140" -The C++ Build Insights SDK is compatible with Visual Studio 2017 and above. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or Visual Studio 2019. It's found at the top of the table of contents on this page. +The C++ Build Insights SDK is compatible with Visual Studio 2017 and later. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or later. It's found at the top of the table of contents on this page. ::: moniker-end ::: moniker range=">=msvc-150" diff --git a/docs/build-insights/reference/sdk/other-types/analysis-callbacks-struct.md b/docs/build-insights/reference/sdk/other-types/analysis-callbacks-struct.md index d95f2c22219..2957df07f10 100644 --- a/docs/build-insights/reference/sdk/other-types/analysis-callbacks-struct.md +++ b/docs/build-insights/reference/sdk/other-types/analysis-callbacks-struct.md @@ -8,7 +8,7 @@ helpviewer_keywords: ["C++ Build Insights", "C++ Build Insights SDK", "ANALYSIS_ ::: moniker range="<=msvc-140" -The C++ Build Insights SDK is compatible with Visual Studio 2017 and above. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or Visual Studio 2019. It's found at the top of the table of contents on this page. +The C++ Build Insights SDK is compatible with Visual Studio 2017 and later. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or later. It's found at the top of the table of contents on this page. ::: moniker-end ::: moniker range=">=msvc-150" diff --git a/docs/build-insights/reference/sdk/other-types/analysis-control-enum-class.md b/docs/build-insights/reference/sdk/other-types/analysis-control-enum-class.md index 79cd00995be..b3426f035e2 100644 --- a/docs/build-insights/reference/sdk/other-types/analysis-control-enum-class.md +++ b/docs/build-insights/reference/sdk/other-types/analysis-control-enum-class.md @@ -8,7 +8,7 @@ helpviewer_keywords: ["C++ Build Insights", "C++ Build Insights SDK", "AnalysisC ::: moniker range="<=msvc-140" -The C++ Build Insights SDK is compatible with Visual Studio 2017 and above. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or Visual Studio 2019. It's found at the top of the table of contents on this page. +The C++ Build Insights SDK is compatible with Visual Studio 2017 and later. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or later. It's found at the top of the table of contents on this page. ::: moniker-end ::: moniker range=">=msvc-150" diff --git a/docs/build-insights/reference/sdk/other-types/analysis-descriptor-struct.md b/docs/build-insights/reference/sdk/other-types/analysis-descriptor-struct.md index 16835e82d1f..73012b0d9ac 100644 --- a/docs/build-insights/reference/sdk/other-types/analysis-descriptor-struct.md +++ b/docs/build-insights/reference/sdk/other-types/analysis-descriptor-struct.md @@ -8,7 +8,7 @@ helpviewer_keywords: ["C++ Build Insights", "C++ Build Insights SDK", "ANALYSIS_ ::: moniker range="<=msvc-140" -The C++ Build Insights SDK is compatible with Visual Studio 2017 and above. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or Visual Studio 2019. It's found at the top of the table of contents on this page. +The C++ Build Insights SDK is compatible with Visual Studio 2017 and later. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or later. It's found at the top of the table of contents on this page. ::: moniker-end ::: moniker range=">=msvc-150" diff --git a/docs/build-insights/reference/sdk/other-types/callback-code-enum.md b/docs/build-insights/reference/sdk/other-types/callback-code-enum.md index 671f852f518..157b5e45345 100644 --- a/docs/build-insights/reference/sdk/other-types/callback-code-enum.md +++ b/docs/build-insights/reference/sdk/other-types/callback-code-enum.md @@ -8,7 +8,7 @@ helpviewer_keywords: ["C++ Build Insights", "C++ Build Insights SDK", "CALLBACK_ ::: moniker range="<=msvc-140" -The C++ Build Insights SDK is compatible with Visual Studio 2017 and above. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or Visual Studio 2019. It's found at the top of the table of contents on this page. +The C++ Build Insights SDK is compatible with Visual Studio 2017 and later. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or later. It's found at the top of the table of contents on this page. ::: moniker-end ::: moniker range=">=msvc-150" diff --git a/docs/build-insights/reference/sdk/other-types/ianalyzer-class.md b/docs/build-insights/reference/sdk/other-types/ianalyzer-class.md index 99c29eade9b..b08d6a4ab3b 100644 --- a/docs/build-insights/reference/sdk/other-types/ianalyzer-class.md +++ b/docs/build-insights/reference/sdk/other-types/ianalyzer-class.md @@ -8,7 +8,7 @@ helpviewer_keywords: ["C++ Build Insights", "C++ Build Insights SDK", "IAnalyzer ::: moniker range="<=msvc-140" -The C++ Build Insights SDK is compatible with Visual Studio 2017 and above. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or Visual Studio 2019. It's found at the top of the table of contents on this page. +The C++ Build Insights SDK is compatible with Visual Studio 2017 and later. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or later. It's found at the top of the table of contents on this page. ::: moniker-end ::: moniker range=">=msvc-150" diff --git a/docs/build-insights/reference/sdk/other-types/irelogger-class.md b/docs/build-insights/reference/sdk/other-types/irelogger-class.md index 5d5a44a2bd2..8fedb9fc5b3 100644 --- a/docs/build-insights/reference/sdk/other-types/irelogger-class.md +++ b/docs/build-insights/reference/sdk/other-types/irelogger-class.md @@ -8,7 +8,7 @@ helpviewer_keywords: ["C++ Build Insights", "C++ Build Insights SDK", "IRelogger ::: moniker range="<=msvc-140" -The C++ Build Insights SDK is compatible with Visual Studio 2017 and above. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or Visual Studio 2019. It's found at the top of the table of contents on this page. +The C++ Build Insights SDK is compatible with Visual Studio 2017 and later. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or later. It's found at the top of the table of contents on this page. ::: moniker-end ::: moniker range=">=msvc-150" diff --git a/docs/build-insights/reference/sdk/other-types/on-analysis-event-func-typedef.md b/docs/build-insights/reference/sdk/other-types/on-analysis-event-func-typedef.md index 63f993e60ff..d063b48e89a 100644 --- a/docs/build-insights/reference/sdk/other-types/on-analysis-event-func-typedef.md +++ b/docs/build-insights/reference/sdk/other-types/on-analysis-event-func-typedef.md @@ -8,7 +8,7 @@ helpviewer_keywords: ["C++ Build Insights", "C++ Build Insights SDK", "OnAnalysi ::: moniker range="<=msvc-140" -The C++ Build Insights SDK is compatible with Visual Studio 2017 and above. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or Visual Studio 2019. It's found at the top of the table of contents on this page. +The C++ Build Insights SDK is compatible with Visual Studio 2017 and later. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or later. It's found at the top of the table of contents on this page. ::: moniker-end ::: moniker range=">=msvc-150" diff --git a/docs/build-insights/reference/sdk/other-types/on-begin-end-pass-func-typedef.md b/docs/build-insights/reference/sdk/other-types/on-begin-end-pass-func-typedef.md index c07cb82d6c7..505cc21c6e6 100644 --- a/docs/build-insights/reference/sdk/other-types/on-begin-end-pass-func-typedef.md +++ b/docs/build-insights/reference/sdk/other-types/on-begin-end-pass-func-typedef.md @@ -8,7 +8,7 @@ helpviewer_keywords: ["C++ Build Insights", "C++ Build Insights SDK", "OnBeginEn ::: moniker range="<=msvc-140" -The C++ Build Insights SDK is compatible with Visual Studio 2017 and above. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or Visual Studio 2019. It's found at the top of the table of contents on this page. +The C++ Build Insights SDK is compatible with Visual Studio 2017 and later. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or later. It's found at the top of the table of contents on this page. ::: moniker-end ::: moniker range=">=msvc-150" diff --git a/docs/build-insights/reference/sdk/other-types/on-relog-event-func-typedef.md b/docs/build-insights/reference/sdk/other-types/on-relog-event-func-typedef.md index ac61f5ae456..af1d88f1ff0 100644 --- a/docs/build-insights/reference/sdk/other-types/on-relog-event-func-typedef.md +++ b/docs/build-insights/reference/sdk/other-types/on-relog-event-func-typedef.md @@ -8,7 +8,7 @@ helpviewer_keywords: ["C++ Build Insights", "C++ Build Insights SDK", "OnRelogEv ::: moniker range="<=msvc-140" -The C++ Build Insights SDK is compatible with Visual Studio 2017 and above. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or Visual Studio 2019. It's found at the top of the table of contents on this page. +The C++ Build Insights SDK is compatible with Visual Studio 2017 and later. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or later. It's found at the top of the table of contents on this page. ::: moniker-end ::: moniker range=">=msvc-150" diff --git a/docs/build-insights/reference/sdk/other-types/on-trace-info-func-typedef.md b/docs/build-insights/reference/sdk/other-types/on-trace-info-func-typedef.md index 15f6bba0122..9d90ce108a2 100644 --- a/docs/build-insights/reference/sdk/other-types/on-trace-info-func-typedef.md +++ b/docs/build-insights/reference/sdk/other-types/on-trace-info-func-typedef.md @@ -8,7 +8,7 @@ helpviewer_keywords: ["C++ Build Insights", "C++ Build Insights SDK", "OnTraceIn ::: moniker range="<=msvc-140" -The C++ Build Insights SDK is compatible with Visual Studio 2017 and above. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or Visual Studio 2019. It's found at the top of the table of contents on this page. +The C++ Build Insights SDK is compatible with Visual Studio 2017 and later. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or later. It's found at the top of the table of contents on this page. ::: moniker-end ::: moniker range=">=msvc-150" diff --git a/docs/build-insights/reference/sdk/other-types/relog-callbacks-struct.md b/docs/build-insights/reference/sdk/other-types/relog-callbacks-struct.md index db6fa74b8c3..4232ac43f4a 100644 --- a/docs/build-insights/reference/sdk/other-types/relog-callbacks-struct.md +++ b/docs/build-insights/reference/sdk/other-types/relog-callbacks-struct.md @@ -8,7 +8,7 @@ helpviewer_keywords: ["C++ Build Insights", "C++ Build Insights SDK", "RELOG_CAL ::: moniker range="<=msvc-140" -The C++ Build Insights SDK is compatible with Visual Studio 2017 and above. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or Visual Studio 2019. It's found at the top of the table of contents on this page. +The C++ Build Insights SDK is compatible with Visual Studio 2017 and later. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or later. It's found at the top of the table of contents on this page. ::: moniker-end ::: moniker range=">=msvc-150" diff --git a/docs/build-insights/reference/sdk/other-types/relog-descriptor-struct.md b/docs/build-insights/reference/sdk/other-types/relog-descriptor-struct.md index 934f9e431cb..756616dbbc5 100644 --- a/docs/build-insights/reference/sdk/other-types/relog-descriptor-struct.md +++ b/docs/build-insights/reference/sdk/other-types/relog-descriptor-struct.md @@ -8,7 +8,7 @@ helpviewer_keywords: ["C++ Build Insights", "C++ Build Insights SDK", "RELOG_DES ::: moniker range="<=msvc-140" -The C++ Build Insights SDK is compatible with Visual Studio 2017 and above. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or Visual Studio 2019. It's found at the top of the table of contents on this page. +The C++ Build Insights SDK is compatible with Visual Studio 2017 and later. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or later. It's found at the top of the table of contents on this page. ::: moniker-end ::: moniker range=">=msvc-150" diff --git a/docs/build-insights/reference/sdk/other-types/relog-retention-system-event-flags-constants.md b/docs/build-insights/reference/sdk/other-types/relog-retention-system-event-flags-constants.md index daa02b1fd37..103d7f456bc 100644 --- a/docs/build-insights/reference/sdk/other-types/relog-retention-system-event-flags-constants.md +++ b/docs/build-insights/reference/sdk/other-types/relog-retention-system-event-flags-constants.md @@ -8,7 +8,7 @@ helpviewer_keywords: ["C++ Build Insights", "C++ Build Insights SDK", "RELOG_RET ::: moniker range="<=msvc-140" -The C++ Build Insights SDK is compatible with Visual Studio 2017 and above. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or Visual Studio 2019. It's found at the top of the table of contents on this page. +The C++ Build Insights SDK is compatible with Visual Studio 2017 and later. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or later. It's found at the top of the table of contents on this page. ::: moniker-end ::: moniker range=">=msvc-150" diff --git a/docs/build-insights/reference/sdk/other-types/result-code-enum.md b/docs/build-insights/reference/sdk/other-types/result-code-enum.md index 27318139aac..6cc9ba32d44 100644 --- a/docs/build-insights/reference/sdk/other-types/result-code-enum.md +++ b/docs/build-insights/reference/sdk/other-types/result-code-enum.md @@ -8,7 +8,7 @@ helpviewer_keywords: ["C++ Build Insights", "C++ Build Insights SDK", "RESULT_CO ::: moniker range="<=msvc-140" -The C++ Build Insights SDK is compatible with Visual Studio 2017 and above. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or Visual Studio 2019. It's found at the top of the table of contents on this page. +The C++ Build Insights SDK is compatible with Visual Studio 2017 and later. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or later. It's found at the top of the table of contents on this page. ::: moniker-end ::: moniker range=">=msvc-150" diff --git a/docs/build-insights/reference/sdk/other-types/tracing-session-msvc-event-flags-constants.md b/docs/build-insights/reference/sdk/other-types/tracing-session-msvc-event-flags-constants.md index 95f5ed3c191..f54881ad7f1 100644 --- a/docs/build-insights/reference/sdk/other-types/tracing-session-msvc-event-flags-constants.md +++ b/docs/build-insights/reference/sdk/other-types/tracing-session-msvc-event-flags-constants.md @@ -8,7 +8,7 @@ helpviewer_keywords: ["C++ Build Insights", "C++ Build Insights SDK", "TRACING_S ::: moniker range="<=msvc-140" -The C++ Build Insights SDK is compatible with Visual Studio 2017 and above. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or Visual Studio 2019. It's found at the top of the table of contents on this page. +The C++ Build Insights SDK is compatible with Visual Studio 2017 and later. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or later. It's found at the top of the table of contents on this page. ::: moniker-end ::: moniker range=">=msvc-150" diff --git a/docs/build-insights/reference/sdk/other-types/tracing-session-options-struct.md b/docs/build-insights/reference/sdk/other-types/tracing-session-options-struct.md index db91e7a1307..88116edfe19 100644 --- a/docs/build-insights/reference/sdk/other-types/tracing-session-options-struct.md +++ b/docs/build-insights/reference/sdk/other-types/tracing-session-options-struct.md @@ -8,7 +8,7 @@ helpviewer_keywords: ["C++ Build Insights", "C++ Build Insights SDK", "TRACING_S ::: moniker range="<=msvc-140" -The C++ Build Insights SDK is compatible with Visual Studio 2017 and above. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or Visual Studio 2019. It's found at the top of the table of contents on this page. +The C++ Build Insights SDK is compatible with Visual Studio 2017 and later. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or later. It's found at the top of the table of contents on this page. ::: moniker-end ::: moniker range=">=msvc-150" diff --git a/docs/build-insights/reference/sdk/other-types/tracing-session-statistics-struct.md b/docs/build-insights/reference/sdk/other-types/tracing-session-statistics-struct.md index 4f427f8e7c7..67374d0acfe 100644 --- a/docs/build-insights/reference/sdk/other-types/tracing-session-statistics-struct.md +++ b/docs/build-insights/reference/sdk/other-types/tracing-session-statistics-struct.md @@ -8,7 +8,7 @@ helpviewer_keywords: ["C++ Build Insights", "C++ Build Insights SDK", "TRACING_S ::: moniker range="<=msvc-140" -The C++ Build Insights SDK is compatible with Visual Studio 2017 and above. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or Visual Studio 2019. It's found at the top of the table of contents on this page. +The C++ Build Insights SDK is compatible with Visual Studio 2017 and later. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or later. It's found at the top of the table of contents on this page. ::: moniker-end ::: moniker range=">=msvc-150" diff --git a/docs/build-insights/reference/sdk/other-types/tracing-session-system-event-flags-constants.md b/docs/build-insights/reference/sdk/other-types/tracing-session-system-event-flags-constants.md index 694868c710a..4e24aea5d9b 100644 --- a/docs/build-insights/reference/sdk/other-types/tracing-session-system-event-flags-constants.md +++ b/docs/build-insights/reference/sdk/other-types/tracing-session-system-event-flags-constants.md @@ -8,7 +8,7 @@ helpviewer_keywords: ["C++ Build Insights", "C++ Build Insights SDK", "TRACING_S ::: moniker range="<=msvc-140" -The C++ Build Insights SDK is compatible with Visual Studio 2017 and above. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or Visual Studio 2019. It's found at the top of the table of contents on this page. +The C++ Build Insights SDK is compatible with Visual Studio 2017 and later. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or later. It's found at the top of the table of contents on this page. ::: moniker-end ::: moniker range=">=msvc-150" diff --git a/docs/build-insights/reference/sdk/overview.md b/docs/build-insights/reference/sdk/overview.md index 03191ec1d68..483b547d4fb 100644 --- a/docs/build-insights/reference/sdk/overview.md +++ b/docs/build-insights/reference/sdk/overview.md @@ -8,7 +8,7 @@ helpviewer_keywords: ["C++ Build Insights", "C++ Build Insights SDK", "Analyzing ::: moniker range="<=msvc-140" -The C++ Build Insights SDK is compatible with Visual Studio 2017 and above. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or Visual Studio 2019. It's found at the top of the table of contents on this page. +The C++ Build Insights SDK is compatible with Visual Studio 2017 and later. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or later. It's found at the top of the table of contents on this page. ::: moniker-end ::: moniker range=">=msvc-150" diff --git a/docs/build-insights/reference/vcperf-commands.md b/docs/build-insights/reference/vcperf-commands.md index 67108130036..1a7924241b4 100644 --- a/docs/build-insights/reference/vcperf-commands.md +++ b/docs/build-insights/reference/vcperf-commands.md @@ -8,16 +8,17 @@ helpviewer_keywords: ["C++ Build Insights", "throughput analysis", "build time a ::: moniker range="<=msvc-150" -The C++ Build Insights tools are available in Visual Studio 2019. To see the documentation for that version, set the Visual Studio **Version** selector control for this article to Visual Studio 2019. It's found at the top of the table of contents on this page. +The C++ Build Insights tools are available starting in Visual Studio 2019 and later. To see the documentation for that version, set the Visual Studio **Version** selector control for this article to Visual Studio 2019 or later. It's found at the top of the table of contents on this page. ::: moniker-end -::: moniker range="msvc-160" +::: moniker range=">=msvc-160" -This article lists and describes the commands available in *vcperf.exe*, and how to use them. +This article lists and describes the commands available in *`vcperf.exe`*, and how to use them. ## Commands to start and stop traces -*IMPORTANT: the following commands all require administrative privileges.* +> [!IMPORTANT] +> The following commands all require administrative privileges. | Option | Arguments and description | |------------------|---------------------------| diff --git a/docs/build-insights/reference/wpa-views.md b/docs/build-insights/reference/wpa-views.md index b12a0c99fac..a7c5391f5c6 100644 --- a/docs/build-insights/reference/wpa-views.md +++ b/docs/build-insights/reference/wpa-views.md @@ -8,10 +8,10 @@ helpviewer_keywords: ["C++ Build Insights", "throughput analysis", "build time a ::: moniker range="<=msvc-150" -The C++ Build Insights tools are available in Visual Studio 2019. To see the documentation for this version, set the Visual Studio **Version** selector control for this article to Visual Studio 2019. It's found at the top of the table of contents on this page. +The C++ Build Insights tools are available in Visual Studio 2019 and later. To see the documentation for this version, set the Visual Studio **Version** selector control for this article to Visual Studio 2019 or later. It's found at the top of the table of contents on this page. ::: moniker-end -::: moniker range="msvc-160" +::: moniker range=">=msvc-160" This article provides details on each of the C++ Build Insights views available in Windows Performance Analyzer (WPA). Use this page to find: diff --git a/docs/build-insights/tutorials/vcperf-and-wpa.md b/docs/build-insights/tutorials/vcperf-and-wpa.md index e76549b94ae..ac87f886b6c 100644 --- a/docs/build-insights/tutorials/vcperf-and-wpa.md +++ b/docs/build-insights/tutorials/vcperf-and-wpa.md @@ -8,18 +8,18 @@ helpviewer_keywords: ["C++ Build Insights", "throughput analysis", "build time a ::: moniker range="<=msvc-150" -The C++ Build Insights tools are available in Visual Studio 2019. To see the documentation for this version, set the Visual Studio **Version** selector control for this article to Visual Studio 2019. It's found at the top of the table of contents on this page. +The C++ Build Insights tools are available in Visual Studio 2019 and later. To see the documentation for this version, set the Visual Studio **Version** selector control for this article to Visual Studio 2019 or later. It's found at the top of the table of contents on this page. ::: moniker-end -::: moniker range="msvc-160" +::: moniker range=">=msvc-160" -In this tutorial, you'll learn how to use *vcperf.exe* to collect a trace of your C++ build. You'll also learn how to view this trace in Windows Performance Analyzer. +In this tutorial, you'll learn how to use *`vcperf.exe`* to collect a trace of your C++ build. You'll also learn how to view this trace in Windows Performance Analyzer. ## Step 1: Install and configure Windows Performance Analyzer WPA is a trace viewer available in the Windows Assessment and Deployment Kit (ADK). It's a separate utility that's not part of the components you can install with the Visual Studio installer. -A version of WPA that supports C++ Build Insights is currently only available in the most recent versions of the Windows ADK, 10.1.19041.0 or later. +A version of WPA that supports C++ Build Insights is only available in versions of the Windows ADK numbered 10.1.19041.0 or later. ### To download and install WPA @@ -42,10 +42,11 @@ Viewing C++ Build Insights traces in WPA requires a special add-in. Follow these 1. [C++ Build Insights NuGet package](https://www.nuget.org/packages/Microsoft.Cpp.BuildInsights/). 1. Copy the `perf_msvcbuildinsights.dll` file into your WPA installation directory. - 1. In Visual Studio 2019 version 16.6 and above, this file is located here: `C:\Program Files (x86)\Microsoft Visual Studio\2019\{Edition}\VC\Tools\MSVC\{Version}\bin\Host{Architecture}\{Architecture}`. + 1. In Visual Studio 2019 version 16.6 and above, this file is located here: `C:\Program Files (x86)\Microsoft Visual Studio\{Year}\{Edition}\VC\Tools\MSVC\{Version}\bin\Host{Architecture}\{Architecture}`. 1. In the C++ Build Insights NuGet package, this file is located here: `wpa\{Architecture}`. 1. In the paths above, replace the variables surrounded by curly brackets as follows: - 1. `{Edition}` is your Visual Studio 2019 edition such as Community, Professional, or Enterprise. + 1. `{Year}` is your Visual Studio product year, such as 2019 or 2022. + 1. `{Edition}` is your Visual Studio edition such as Community, Professional, or Enterprise. 1. `{Version}` is your MSVC version. Choose the highest one available. 1. `{Architecture}`: choose `x64` if you have a 64-bit version of Windows. Otherwise, choose `x86`. 1. The WPA installation directory is typically: `C:\Program Files (x86)\Windows Kits\10\Windows Performance Toolkit`. diff --git a/docs/build-insights/tutorials/wpa-basics.md b/docs/build-insights/tutorials/wpa-basics.md index 7c4c748f284..9ac76d830c9 100644 --- a/docs/build-insights/tutorials/wpa-basics.md +++ b/docs/build-insights/tutorials/wpa-basics.md @@ -8,10 +8,10 @@ helpviewer_keywords: ["C++ Build Insights", "throughput analysis", "build time a ::: moniker range="<=msvc-150" -The C++ Build Insights tools are available in Visual Studio 2019. To see the documentation for this version, set the Visual Studio **Version** selector control for this article to Visual Studio 2019. It's found at the top of the table of contents on this page. +The C++ Build Insights tools are available in Visual Studio 2019 and later. To see the documentation for this version, set the Visual Studio **Version** selector control for this article to Visual Studio 2019 or later. It's found at the top of the table of contents on this page. ::: moniker-end -::: moniker range="msvc-160" +::: moniker range=">=msvc-160" Using C++ Build Insights effectively requires some knowledge of Windows Performance Analyzer (WPA). This article helps you become familiar with common WPA operations. For more information on how to use WPA, see the [Windows Performance Analyzer](/windows-hardware/test/wpt/windows-performance-analyzer) documentation. diff --git a/docs/build/clang-support-cmake.md b/docs/build/clang-support-cmake.md index 90d0faf9f1f..6ae9039afb1 100644 --- a/docs/build/clang-support-cmake.md +++ b/docs/build/clang-support-cmake.md @@ -9,23 +9,33 @@ helpviewer_keywords: ["Clang support for C++ CMake projects"] ::: moniker range="<=msvc-150" -Clang support is available in Visual Studio 2019. +Clang support is available starting in Visual Studio 2019. ::: moniker-end - -::: moniker range="msvc-160" +::: moniker range=">=msvc-160" You can use Visual Studio with Clang to edit and debug C++ CMake projects that target Windows or Linux. -**Windows**: Visual Studio 2019 version 16.1 includes support for editing, building, and debugging with Clang/LLVM in CMake projects targeting Windows. +**Windows**: Starting in Visual Studio 2019 version 16.1, Visual Studio includes support for editing, building, and debugging with Clang/LLVM in CMake projects targeting Windows. **Linux**: For Linux CMake projects, no special Visual Studio support is required. You can install Clang using your distro's package manager, and add the appropriate commands in the CMakeLists.txt file. ## Install -For best IDE support in Visual Studio, we recommend using the latest Clang compiler tools for Windows. If you don't already have those, you can install them by opening the Visual Studio Installer and choosing **C++ Clang compiler for Windows** under **Desktop development with C++** optional components. When using a custom Clang installation, check the **C++ Clang-cl for v142 build tools** component. +::: moniker-end +::: moniker range="msvc-160" + +For the best IDE support in Visual Studio, we recommend using the latest Clang compiler tools for Windows. If you don't already have those, you can install them by opening the Visual Studio Installer and choosing **C++ Clang compiler for Windows** under **Desktop development with C++** optional components. When using a custom Clang installation, check the **C++ Clang-cl for v142 build tools** component. + +::: moniker-end +::: moniker range="msvc-170" + +For the best IDE support in Visual Studio, we recommend using the latest Clang compiler tools for Windows. If you don't already have those, you can install them by opening the Visual Studio Installer and choosing **C++ Clang compiler for Windows** under **Desktop development with C++** optional components. When using a custom Clang installation, check the **C++ Clang-cl for v143 build tools** component. + +::: moniker-end +::: moniker range=">=msvc-160" -![Clang component installation.](media/clang-install-vs2019.png) +![Screenshot of the Visual Studio Installer Individual Components page that shows Clang components available for installation.](media/clang-install-vs2019.png) ## Create a new configuration @@ -35,11 +45,11 @@ To add a new Clang configuration to a CMake project: 1. Under **Configurations**, press the **Add Configuration** button: - ![Add configuration.](media/cmake-add-config-icon.png) + ![Screenshot of the controls at the top of the C Make Settings dialog, with the Add Configuration control highlighted.](media/cmake-add-config-icon.png) 1. Choose the desired Clang configuration (note that separate Clang configurations are provided for Windows and Linux), then press **Select**: - ![CMake Clang configuration.](media/cmake-clang-configuration.png) + ![Screenshot of the Add Configuration to C Make Settings dialog for Clang configuration.](media/cmake-clang-configuration.png) 1. To make modifications to this configuration, use the **CMake Settings Editor**. For more information, see [Customize CMake build settings in Visual Studio](customize-cmake-settings.md). diff --git a/docs/build/clang-support-msbuild.md b/docs/build/clang-support-msbuild.md index 164309c77ef..68e0ae8a9a0 100644 --- a/docs/build/clang-support-msbuild.md +++ b/docs/build/clang-support-msbuild.md @@ -13,7 +13,7 @@ Clang support for both CMake and MSBuild projects is available in Visual Studio ::: moniker-end -::: moniker range="msvc-160" +::: moniker range=">=msvc-160" You can use Visual Studio 2019 version 16.2 and later with Clang to edit, build, and debug C++ Visual Studio projects (MSBuild) that target Windows or Linux. diff --git a/docs/build/cmake-predefined-configuration-reference.md b/docs/build/cmake-predefined-configuration-reference.md index 59a2ddf7b01..d9597573d8d 100644 --- a/docs/build/cmake-predefined-configuration-reference.md +++ b/docs/build/cmake-predefined-configuration-reference.md @@ -347,7 +347,7 @@ These options allow you to run commands on the remote system before and after bu ::: moniker-end -::: moniker range="msvc-160" +::: moniker range=">=msvc-160" In a CMake project, build configurations are stored in a *`CMakeSettings.json`* file. When you choose **Manage Configurations** from the build configuration dropdown in the main toolbar, a dialog appears that shows the default CMake configurations available in Visual Studio: diff --git a/docs/build/configure-cmake-debugging-sessions.md b/docs/build/configure-cmake-debugging-sessions.md index 2e1439d69b5..724048132ef 100644 --- a/docs/build/configure-cmake-debugging-sessions.md +++ b/docs/build/configure-cmake-debugging-sessions.md @@ -8,7 +8,7 @@ helpviewer_keywords: ["CMake debugging"] ::: moniker range="msvc-140" -Native CMake support is available in Visual Studio 2017 and later. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or Visual Studio 2019. It's found at the top of the table of contents on this page. +Native CMake support is available in Visual Studio 2017 and later. To see the documentation for these versions, set the Visual Studio **Version** selector control for this article to Visual Studio 2017 or later. It's found at the top of the table of contents on this page. ::: moniker-end diff --git a/docs/build/creating-and-managing-visual-cpp-projects.md b/docs/build/creating-and-managing-visual-cpp-projects.md index 274e37146a0..f6fa4c479e8 100644 --- a/docs/build/creating-and-managing-visual-cpp-projects.md +++ b/docs/build/creating-and-managing-visual-cpp-projects.md @@ -11,7 +11,7 @@ A *Visual Studio project* is a project based on the MSBuild build system. MSBuil ## Create a project -::: moniker range="msvc-160" +::: moniker range=">=msvc-160" You can create C++ projects by choosing **File** > **New** > **Project**, then setting the **Language** to C++. In the results list you see a list of project templates which you can filter by setting the **Platform** or **Project Type** and by typing keywords into the search box. diff --git a/docs/build/customize-cmake-settings.md b/docs/build/customize-cmake-settings.md index e6c9b859a31..a219e385927 100644 --- a/docs/build/customize-cmake-settings.md +++ b/docs/build/customize-cmake-settings.md @@ -6,7 +6,7 @@ helpviewer_keywords: ["CMake build settings"] --- # Customize CMake build settings -::: moniker range="msvc-160" +::: moniker range=">=msvc-160" In Visual Studio 2019 and later, you can add configurations and customize their settings by using the **CMake settings editor**. The editor is intended to be a simpler alternative to manually editing the *CMakeSettings.json* file, but if you prefer to edit the file directly, you can click the **Edit JSON** link in the upper right of the editor. diff --git a/docs/build/reference/advanced-property-page.md b/docs/build/reference/advanced-property-page.md index 25a1eb82127..03e9ef214bb 100644 --- a/docs/build/reference/advanced-property-page.md +++ b/docs/build/reference/advanced-property-page.md @@ -8,7 +8,7 @@ f1_keywords: ["VC.Project.VCConfiguration.TargetExt", "VC.Project.VCConfiguratio ::: moniker range="<=msvc-150" -The Advanced property page is available in Visual Studio 2019 and later. To see the documentation for that version, set the Visual Studio **Version** selector control for this article to Visual Studio 2019. It's found at the top of the table of contents on this page. In earlier versions of Visual Studio, these properties appear on the [General property page](./general-property-page-project.md): +The Advanced property page is available in Visual Studio 2019 and later. To see the documentation for that version, set the Visual Studio **Version** selector control for this article to Visual Studio 2019 or later. It's found at the top of the table of contents on this page. In earlier versions of Visual Studio, these properties appear on the [General property page](./general-property-page-project.md): - [Target Extension](./general-property-page-project.md#target-extension) - [Extensions to Delete on Clean](./general-property-page-project.md#extensions-to-delete-on-clean) @@ -22,7 +22,7 @@ The Advanced property page is available in Visual Studio 2019 and later. To see ::: moniker-end -::: moniker range="msvc-160" +::: moniker range=">=msvc-160" The Advanced property page is available in Visual Studio 2019 and later. The specific properties shown depend on the project type. Windows Runtime (Universal Windows Platform, or UWP) projects don't show this page. diff --git a/docs/build/reference/clr-common-language-runtime-compilation.md b/docs/build/reference/clr-common-language-runtime-compilation.md index 063fff6b89d..d8189c75f6e 100644 --- a/docs/build/reference/clr-common-language-runtime-compilation.md +++ b/docs/build/reference/clr-common-language-runtime-compilation.md @@ -23,7 +23,7 @@ One or more of the following comma-separated arguments. With no options, **`/clr`** creates metadata for the component. The metadata can be consumed by other CLR applications, and enables the component to consume types and data in the metadata of other CLR components. For more information, see [Mixed (Native and Managed) Assemblies](../../dotnet/mixed-native-and-managed-assemblies.md). -::: moniker range="msvc-160" +::: moniker range=">=msvc-160" - **`netcore`** diff --git a/docs/build/reference/fc-full-path-of-source-code-file-in-diagnostics.md b/docs/build/reference/fc-full-path-of-source-code-file-in-diagnostics.md index 5cc1c4a4eba..82e2b082db6 100644 --- a/docs/build/reference/fc-full-path-of-source-code-file-in-diagnostics.md +++ b/docs/build/reference/fc-full-path-of-source-code-file-in-diagnostics.md @@ -37,7 +37,7 @@ With **`/FC`**, the compiler output looks similar to this diagnostic text: - c:\test\compiler_option_fc.cpp(5): error C2143: syntax error: missing ';' before '}' ::: moniker-end -::: moniker range="msvc-160" +::: moniker range=">=msvc-160" - C:\test\compiler_option_FC.cpp(5): error C2143: syntax error: missing ';' before '}' diff --git a/docs/build/vscpp-step-1-create.md b/docs/build/vscpp-step-1-create.md index d0744e447be..af10d950ea4 100644 --- a/docs/build/vscpp-step-1-create.md +++ b/docs/build/vscpp-step-1-create.md @@ -113,7 +113,7 @@ Come here for solutions to common issues when you create your first C++ project. ### Create your app project: issues -::: moniker range="msvc-160" +::: moniker range=">=msvc-160" The **New Project** dialog should show a **Console App** template that has **C++**, **Windows**, and **Console** tags. If you don't see it, there are two possible causes. It might be filtered out of the list, or it might not be installed. First, check the filter dropdowns at the top of the list of templates. Set them to **C++**, **Windows**, and **Console**. The C++ **Console App** template should appear; otherwise, the **Desktop development with C++** workload isn't installed. diff --git a/docs/build/walkthrough-creating-and-using-a-static-library-cpp.md b/docs/build/walkthrough-creating-and-using-a-static-library-cpp.md index e219b4f0a47..d8f66d6f61a 100644 --- a/docs/build/walkthrough-creating-and-using-a-static-library-cpp.md +++ b/docs/build/walkthrough-creating-and-using-a-static-library-cpp.md @@ -2,7 +2,7 @@ title: "Walkthrough: Create and use a static library (C++)" description: "Use C++ to create a static library (.lib) in Visual Studio." ms.custom: "get-started-article" -ms.date: "04/13/2020" +ms.date: 10/28/2021 helpviewer_keywords: ["libraries [C++], static", "static libraries [C++]"] ms.assetid: 3cc36411-7d66-4240-851e-dacb9a8fd6ac --- @@ -30,11 +30,11 @@ An understanding of the fundamentals of the C++ language. The instructions for how to create the project vary depending on your version of Visual Studio. To see the documentation for your preferred version of Visual Studio, use the **Version** selector control. It's found at the top of the table of contents on this page. -::: moniker range="msvc-160" +::: moniker range=">=msvc-160" -### To create a static library project in Visual Studio 2019 +### To create a static library project in Visual Studio -1. On the menu bar, choose **File** > **New** > **Project** to open the **Create a New Project** dialog box. +1. On the menu bar, choose **File** > **New** > **Project** to open the **Create a New Project** dialog. 1. At the top of the dialog, set **Language** to **C++**, set **Platform** to **Windows**, and set **Project type** to **Library**. @@ -162,11 +162,11 @@ The instructions for how to create the project vary depending on your version of ## Create a C++ console app that references the static library -::: moniker range="msvc-160" +::: moniker range=">=msvc-160" -### To create a C++ console app that references the static library in Visual Studio 2019 +### To create a C++ console app that references the static library in Visual Studio -1. In **Solution Explorer**, right-click on the top node, **Solution 'StaticMath'**, to open the shortcut menu. Choose **Add** > **New Project** to open the **Add a New Project** dialog box. +1. In **Solution Explorer**, right-click on the top node, **Solution 'StaticMath'**, to open the shortcut menu. Choose **Add** > **New Project** to open the **Add a New Project** dialog. 1. At the top of the dialog, set the **Project type** filter to **Console**. diff --git a/docs/cppcx/static-libraries-c-cx.md b/docs/cppcx/static-libraries-c-cx.md index 076b8f8b8dc..a67e7db8feb 100644 --- a/docs/cppcx/static-libraries-c-cx.md +++ b/docs/cppcx/static-libraries-c-cx.md @@ -1,7 +1,7 @@ --- description: "Learn more about: Static libraries (C++/CX)" title: "Static libraries (C++/CX)" -ms.date: "02/03/2017" +ms.date: 10/28/2021 ms.assetid: 7faf53c8-fa21-42cc-8246-d32533ef9dfa --- # Static libraries (C++/CX) @@ -12,11 +12,11 @@ A static library that's used in a Universal Windows Platform (UWP) app can conta Instructions for creating a new project vary depending on which version of Visual Studio you have installed. To see the documentation for your preferred version of Visual Studio, use the **Version** selector control. It's found at the top of the table of contents on this page. -::: moniker range="msvc-160" +::: moniker range=">=msvc-160" -### To create a UWP static library in Visual Studio 2019 +### To create a UWP static library in Visual Studio -1. On the menu bar, choose **File** > **New** > **Project** to open the **Create a New Project** dialog box. +1. On the menu bar, choose **File** > **New** > **Project** to open the **Create a New Project** dialog. 1. At the top of the dialog, set **Language** to **C++**, set **Platform** to **Windows**, and set **Project type** to **UWP**. diff --git a/docs/data/oledb/consumer-wizard-generated-classes.md b/docs/data/oledb/consumer-wizard-generated-classes.md index f0a7a74ec06..c56375b66cc 100644 --- a/docs/data/oledb/consumer-wizard-generated-classes.md +++ b/docs/data/oledb/consumer-wizard-generated-classes.md @@ -7,7 +7,7 @@ ms.assetid: dba0538f-2afe-4354-8cbb-f202ea8ade5a --- # Consumer Wizard-Generated Classes -::: moniker range="msvc-160" +::: moniker range=">=msvc-160" The ATL OLE DB Consumer wizard is not available in Visual Studio 2019 and later. You can still add the functionality manually. diff --git a/docs/data/oledb/consumer-wizard-generated-methods.md b/docs/data/oledb/consumer-wizard-generated-methods.md index 437195fc244..28a3305590d 100644 --- a/docs/data/oledb/consumer-wizard-generated-methods.md +++ b/docs/data/oledb/consumer-wizard-generated-methods.md @@ -7,7 +7,7 @@ ms.assetid: d80ee51c-8bb3-4dca-8760-5808e0fb47b4 --- # Consumer Wizard-Generated Methods -::: moniker range="msvc-160" +::: moniker range=">=msvc-160" The ATL OLE DB Consumer wizard is not available in Visual Studio 2019 and later. You can still add the functionality manually. diff --git a/docs/data/oledb/creating-a-simple-consumer.md b/docs/data/oledb/creating-a-simple-consumer.md index 7ee6611edfb..f66ec43fe81 100644 --- a/docs/data/oledb/creating-a-simple-consumer.md +++ b/docs/data/oledb/creating-a-simple-consumer.md @@ -7,7 +7,7 @@ ms.assetid: ae32d657-72ea-4db8-9839-75cb5cff68ae --- # Creating a Simple Consumer -::: moniker range="msvc-160" +::: moniker range=">=msvc-160" The ATL OLE DB Consumer wizard is not available in Visual Studio 2019 and later. You can still add the functionality manually. For more information, see [Creating a Consumer Without Using a Wizard](creating-a-consumer-without-using-a-wizard.md). diff --git a/docs/data/oledb/creating-a-simple-read-only-provider.md b/docs/data/oledb/creating-a-simple-read-only-provider.md index 30d1d173e5b..32a81fc1e77 100644 --- a/docs/data/oledb/creating-a-simple-read-only-provider.md +++ b/docs/data/oledb/creating-a-simple-read-only-provider.md @@ -7,7 +7,7 @@ ms.assetid: ade8ccdd-9ea4-4e46-a964-18460c2a2401 --- # Creating a Simple Read-Only Provider -::: moniker range="msvc-160" +::: moniker range=">=msvc-160" The ATL OLE DB Provider wizard is not available in Visual Studio 2019 and later. diff --git a/docs/data/oledb/creating-an-ole-db-consumer-using-a-wizard.md b/docs/data/oledb/creating-an-ole-db-consumer-using-a-wizard.md index 8a0574d3594..711eab3b31c 100644 --- a/docs/data/oledb/creating-an-ole-db-consumer-using-a-wizard.md +++ b/docs/data/oledb/creating-an-ole-db-consumer-using-a-wizard.md @@ -7,7 +7,7 @@ ms.assetid: efefd4c0-4491-4072-aa9b-59545641efb3 --- # Creating an OLE DB Consumer Using a Wizard -::: moniker range="msvc-160" +::: moniker range=">=msvc-160" The ATL OLE DB Consumer wizard is not available in Visual Studio 2019 and later. You can still add the functionality manually. For more information, see [Creating a Consumer Without Using a Wizard](creating-a-consumer-without-using-a-wizard.md). diff --git a/docs/data/oledb/creating-an-ole-db-consumer.md b/docs/data/oledb/creating-an-ole-db-consumer.md index 4fd38c88552..330869ffc8c 100644 --- a/docs/data/oledb/creating-an-ole-db-consumer.md +++ b/docs/data/oledb/creating-an-ole-db-consumer.md @@ -7,7 +7,7 @@ ms.assetid: 652309d3-7736-4354-89ec-28ec80a83f9a --- # Creating an OLE DB Consumer -::: moniker range="msvc-160" +::: moniker range=">=msvc-160" The ATL OLE DB Consumer wizard is not available in Visual Studio 2019 and later. You can still add the functionality manually. For more information, see [Creating a Consumer Without Using a Wizard](creating-a-consumer-without-using-a-wizard.md). diff --git a/docs/data/oledb/creating-the-provider.md b/docs/data/oledb/creating-the-provider.md index 9034fb27ca0..2953bf1c08f 100644 --- a/docs/data/oledb/creating-the-provider.md +++ b/docs/data/oledb/creating-the-provider.md @@ -7,7 +7,7 @@ ms.assetid: 2506ba8f-010d-4231-aac1-387432f7b6b9 --- # Creating the Provider -::: moniker range="msvc-160" +::: moniker range=">=msvc-160" The ATL OLE DB Provider wizard is not available in Visual Studio 2019 and later. diff --git a/docs/data/oledb/field-status-data-members-in-wizard-generated-accessors.md b/docs/data/oledb/field-status-data-members-in-wizard-generated-accessors.md index 573ba7ab859..9fdc887f098 100644 --- a/docs/data/oledb/field-status-data-members-in-wizard-generated-accessors.md +++ b/docs/data/oledb/field-status-data-members-in-wizard-generated-accessors.md @@ -7,7 +7,7 @@ ms.assetid: 66e4e223-c60c-471e-860d-d23abcdfe371 --- # Field Status Data Members in Wizard-Generated Accessors -::: moniker range="msvc-160" +::: moniker range=">=msvc-160" The ATL OLE DB Consumer wizard is not available in Visual Studio 2019 and later. You can still add the functionality manually. For more information, see [Creating a Consumer Without Using a Wizard](creating-a-consumer-without-using-a-wizard.md). diff --git a/docs/data/oledb/implementing-a-simple-consumer.md b/docs/data/oledb/implementing-a-simple-consumer.md index 8b9ca8527be..21b0ec040fe 100644 --- a/docs/data/oledb/implementing-a-simple-consumer.md +++ b/docs/data/oledb/implementing-a-simple-consumer.md @@ -7,7 +7,7 @@ ms.assetid: 13828167-23a4-4e94-8b6c-878262fda464 --- # Implementing a Simple Consumer -::: moniker range="msvc-160" +::: moniker range=">=msvc-160" The ATL OLE DB Consumer wizard is not available in Visual Studio 2019 and later. You can still add the functionality manually. For more information, see [Creating a Consumer Without Using a Wizard](creating-a-consumer-without-using-a-wizard.md). diff --git a/docs/data/oledb/provider-wizard-generated-files.md b/docs/data/oledb/provider-wizard-generated-files.md index 59f81e9e1cd..f4590c8ed8c 100644 --- a/docs/data/oledb/provider-wizard-generated-files.md +++ b/docs/data/oledb/provider-wizard-generated-files.md @@ -7,7 +7,7 @@ ms.assetid: 6e1ac94b-eb90-4abf-82b3-06944b947ebc --- # Provider Wizard-Generated Files -::: moniker range="msvc-160" +::: moniker range=">=msvc-160" The ATL OLE DB Provider wizard is not available in Visual Studio 2019 and later. diff --git a/docs/data/oledb/supporting-schema-rowsets.md b/docs/data/oledb/supporting-schema-rowsets.md index 6e653d63f44..cb6844a7383 100644 --- a/docs/data/oledb/supporting-schema-rowsets.md +++ b/docs/data/oledb/supporting-schema-rowsets.md @@ -23,7 +23,7 @@ Schema rowsets allow consumers to get information about a data store without kno ## ATL OLE DB Provider Wizard Support -::: moniker range="msvc-160" +::: moniker range=">=msvc-160" The ATL OLE DB Provider wizard is not available in Visual Studio 2019 and later. diff --git a/docs/dotnet/dotnet-programming-with-cpp-cli-visual-cpp.md b/docs/dotnet/dotnet-programming-with-cpp-cli-visual-cpp.md index 0c271fad2d8..2109d30acee 100644 --- a/docs/dotnet/dotnet-programming-with-cpp-cli-visual-cpp.md +++ b/docs/dotnet/dotnet-programming-with-cpp-cli-visual-cpp.md @@ -1,7 +1,7 @@ --- title: ".NET programming with C++/CLI" description: "Learn how to use C++/CLI to create .NET apps and components in Visual Studio." -ms.date: 9/21/2021 +ms.date: 10/28/2021 helpviewer_keywords: ["programming [C++], .NET programming", ".NET Framework [C++]", ".NET applications [C++]", "Visual C++, .NET programming"] --- # .NET programming with C++/CLI @@ -28,6 +28,15 @@ In Visual Studio 2019, the default target framework for .NET Core projects is 5. C++/CLI itself isn't installed by default when you install a Visual Studio C++ workload. To install the component after Visual Studio is installed, open the Visual Studio Installer by selecting the Windows **Start** menu and searching for **visual studio installer**. Choose the **Modify** button next to your installed version of Visual Studio. Select the **Individual components** tab. Scroll down to the **Compilers, build tools, and runtimes** section, and select **C++/CLI support for v142 build tools (Latest)**. Select **Modify** to download the necessary files and update Visual Studio. +::: moniker-end +::: moniker range="msvc-170" + +In Visual Studio 2022, the default target framework for .NET Core projects is 6.0. For .NET Frameworks projects, the default is 4.7.2. The .NET Framework version selector is on the **Configure your new project** page of the **Create a new project** dialog. + +## Install C++/CLI support in Visual Studio 2022 + +C++/CLI itself isn't installed by default when you install a Visual Studio C++ workload. To install the component after Visual Studio is installed, open the Visual Studio Installer by selecting the Windows **Start** menu and searching for **visual studio installer**. Choose the **Modify** button next to your installed version of Visual Studio. Select the **Individual components** tab. Scroll down to the **Compilers, build tools, and runtimes** section, and select **C++/CLI support for v143 build tools (Latest)**. Select **Modify** to download the necessary files and update Visual Studio. + ::: moniker-end ## In this section diff --git a/docs/dotnet/how-to-create-clr-console-applications-cpp-cli.md b/docs/dotnet/how-to-create-clr-console-applications-cpp-cli.md index de50c880fbd..a84ac096d45 100644 --- a/docs/dotnet/how-to-create-clr-console-applications-cpp-cli.md +++ b/docs/dotnet/how-to-create-clr-console-applications-cpp-cli.md @@ -18,7 +18,7 @@ You can use the **CLR Console App** template in the **New Project** dialog to cr C++/CLI support isn't installed by default when you install a Visual Studio C++ workload. If you don't see a CLR heading under Visual C++ in the **New Project** dialog, you may need to install C++/CLI support. For more information, see [.NET programming with C++/CLI](../dotnet/dotnet-programming-with-cpp-cli-visual-cpp.md). ::: moniker-end -::: moniker range="msvc-160" +::: moniker range=">=msvc-160" You can use the **CLR Console App (.NET Framework)** template in the **Create a new project** dialog to create a console app project that already has essential project references and files. @@ -121,7 +121,7 @@ When you use the CLR Console App template to create a project, it automatically 1. Choose the **OK** button to generate the project and source files. ::: moniker-end -::: moniker range="msvc-160" +::: moniker range=">=msvc-160" 1. On the menu bar, choose **File** > **New** > **Project**. diff --git a/docs/dotnet/walkthrough-compiling-a-cpp-program-that-targets-the-clr-in-visual-studio.md b/docs/dotnet/walkthrough-compiling-a-cpp-program-that-targets-the-clr-in-visual-studio.md index b24f5a42c8e..a07c0032fc1 100644 --- a/docs/dotnet/walkthrough-compiling-a-cpp-program-that-targets-the-clr-in-visual-studio.md +++ b/docs/dotnet/walkthrough-compiling-a-cpp-program-that-targets-the-clr-in-visual-studio.md @@ -1,11 +1,11 @@ --- -title: "Compile a C++/CLI Program that Targets the CLR" +title: "Compile a C++/CLI program that targets the CLR" description: "Use Microsoft C++ to create programs and libraries that can connect native C++ code and .NET programs." -ms.date: "04/23/2019" +ms.date: 10/28/2021 helpviewer_keywords: ["command-line applications [C++], managed code", "compiling programs [C++]", "Visual C++, managed code", "managed code [C++]"] ms.assetid: 339f89df-a5d2-4040-831a-ddbe25b5dce4 --- -# Walkthrough: Compile a C++/CLI Program that Targets the CLR in Visual Studio +# Walkthrough: Compile a C++/CLI program that targets the CLR in Visual Studio By using C++/CLI you can create C++ programs that use .NET classes as well as native C++ types. C++/CLI is intended for use in console applications and in DLLs that wrap native C++ code and make it accessible from .NET programs. To create a Windows user interface based on .NET, use C# or Visual Basic. @@ -20,9 +20,9 @@ For this procedure, you can type your own C++ program or use one of the sample p The following steps vary depending on which version of Visual Studio you are using. To see the documentation for your preferred version of Visual Studio, use the **Version** selector control. It's found at the top of the table of contents on this page. -::: moniker range="msvc-160" +::: moniker range=">=msvc-160" -### To create a C++/CLI project in Visual Studio 2019 +### To create a C++/CLI project in Visual Studio 1. In **Solution Explorer**, right-click on the top to open the **Create a New Project** dialog box. diff --git a/docs/error-messages/toc.yml b/docs/error-messages/toc.yml index c125a6fdfdd..71ccf0402f5 100644 --- a/docs/error-messages/toc.yml +++ b/docs/error-messages/toc.yml @@ -61,6 +61,8 @@ items: href: tool-errors/command-line-error-d8045.md - name: Command-line error D8048 href: tool-errors/command-line-error-d8048.md + - name: Command-line error D8049 + href: tool-errors/command-line-error-d8049.md - name: Command-line warning D9024 href: tool-errors/command-line-warning-d9024.md - name: Command-line warning D9025 diff --git a/docs/error-messages/tool-errors/command-line-error-d8049.md b/docs/error-messages/tool-errors/command-line-error-d8049.md new file mode 100644 index 00000000000..ec848363813 --- /dev/null +++ b/docs/error-messages/tool-errors/command-line-error-d8049.md @@ -0,0 +1,22 @@ +--- +description: "Learn about the cause and solutions for command-line error D8049" +title: "Command-Line Error D8049" +ms.date: 10/28/2021 +f1_keywords: ["D8049"] +helpviewer_keywords: ["D8049"] +--- +# Command-line error D8049 + +> cannot execute '*compiler-component*': command line is too long to fit in debug record + +An internal length limit on debug record include paths was exceeded. + +## Remarks + +When the compiler creates debug records in an object file, it uses the full path for each included file. Absolute paths are recorded as specified. For relative include paths, the debug record prepends the build's current working directory to the relative path. If your build runs in a relatively deep path, the corresponding path records get longer. The total length of too many long paths can exceed the internal limits of the compiler. + +## To resolve this issue + +- Use shorter paths for your include and build directories. Install your library include headers in directories that have shorter paths, and use short paths to your projects' intermediate and destination build directories. IF you alias paths, use short aliases. Set `%TMP%` and `%TEMP%` to directories that have shorter paths. + +- Optimize your include files to the minimum set required for any given source file. This method also has the advantage of speeding compilation times. If you use precompiled headers, it's important to optimize the set of headers you include in your precompiled header file. In complex solutions, it may be worthwhile to create different precompiled headers optimized for different parts of your project. If your code uses C++20, we recommend you use modules or header modules in preference to precompiled headers. diff --git a/docs/error-messages/tool-errors/command-line-errors-d8000-through-d9999.md b/docs/error-messages/tool-errors/command-line-errors-d8000-through-d9999.md index 50b63f763f0..5eb48e048e6 100644 --- a/docs/error-messages/tool-errors/command-line-errors-d8000-through-d9999.md +++ b/docs/error-messages/tool-errors/command-line-errors-d8000-through-d9999.md @@ -18,7 +18,9 @@ The articles in this section provide a reference to the command-line errors and [Command-Line Error D8027](../../error-messages/tool-errors/command-line-error-d8027.md) \ [Command-Line Error D8036](../../error-messages/tool-errors/command-line-error-d8036.md) \ [Command-Line Error D8037](../../error-messages/tool-errors/command-line-error-d8037.md) \ -[Command-Line Error D8045](../../error-messages/tool-errors/command-line-error-d8045.md) +[Command-Line Error D8045](../../error-messages/tool-errors/command-line-error-d8045.md) \ +[Command-Line Error D8048](../../error-messages/tool-errors/command-line-error-d8048.md) \ +[Command-Line Error D8049](../../error-messages/tool-errors/command-line-error-d8049.md) ## Command-line warning messages diff --git a/docs/ide/cpp-linter-overview.md b/docs/ide/cpp-linter-overview.md index 6d6dd9ff556..31990255209 100644 --- a/docs/ide/cpp-linter-overview.md +++ b/docs/ide/cpp-linter-overview.md @@ -20,16 +20,7 @@ The IntelliSense code linter for C++ helps developers find and fix common C++ pr ## Find problems -::: moniker range=">=msvc-170" - -In Visual Studio 2019, the C++ linter is available as an option. Starting in Visual Studio 2022, the C++ Linter is enabled by default. To use it, just open a source file in the editor. The linter shows any problems it finds by annotations in the editor window and in the Error List window. - -::: moniker-end -::: moniker range="msvc-160" - -In Visual Studio 2019, the C++ linter is available as an option. To enable it, follow the instructions in [Configure the linter](#configure-the-linter). Then just open a source file in the editor. The linter shows any problems it finds by annotations in the editor window and in the Error List window. - -::: moniker-end +Starting in Visual Studio 2022, the C++ Linter is enabled by default. To use it, just open a source file in the editor. The linter shows any problems it finds by annotations in the editor window and in the Error List window. In Visual Studio 2019, the C++ linter is available as an option. To enable it, follow the instructions in [Configure the linter](#configure-the-linter). ## Fix problems diff --git a/docs/ide/read-and-understand-code-cpp.md b/docs/ide/read-and-understand-code-cpp.md index e8d8ace8b72..e8309344360 100644 --- a/docs/ide/read-and-understand-code-cpp.md +++ b/docs/ide/read-and-understand-code-cpp.md @@ -51,7 +51,7 @@ When **Map Mode** is off, the scroll bar still highlights the changes you have m Hover over any variable, function, or other symbol to get information about it, including the declaration, and any comments that are located just preceding it. -::: moniker range="msvc-160" +::: moniker range=">=msvc-160" ![Screenshot showing the Quick Info tooltip in Visual Studio 2019.](../ide/media/quick-info-vs2019.png "Quick Info") diff --git a/docs/ide/walkthrough-deploying-your-program-cpp.md b/docs/ide/walkthrough-deploying-your-program-cpp.md index 6b80c4ac4e8..44cdf605b43 100644 --- a/docs/ide/walkthrough-deploying-your-program-cpp.md +++ b/docs/ide/walkthrough-deploying-your-program-cpp.md @@ -25,9 +25,9 @@ The steps in this section vary depending on which version of Visual Studio you h -::: moniker range="msvc-160" +::: moniker range=">=msvc-160" -### To install the setup and deployment project template for Visual Studio 2019 +### To install the setup and deployment project template for Visual Studio 1. If you haven't already done so, download the Microsoft Visual Studio Installer Projects extension. The extension is free for Visual Studio developers and adds the functionality of the setup and deployment project templates to Visual Studio. When you're connected to the Internet, in Visual Studio, choose **Extensions** > **Manage Extensions**. Under the **Extensions and Updates** dialog, select the **Online** tab and type *Microsoft Visual Studio Installer Projects* in the search box. Hit **Enter**, select **Microsoft Visual Studio \ Installer Projects**, and click **Download**. Choose to run and install the extension, then restart Visual Studio. diff --git a/docs/ide/walkthrough-working-with-projects-and-solutions-cpp.md b/docs/ide/walkthrough-working-with-projects-and-solutions-cpp.md index cdb91ee4e87..0bb96cb8a3b 100644 --- a/docs/ide/walkthrough-working-with-projects-and-solutions-cpp.md +++ b/docs/ide/walkthrough-working-with-projects-and-solutions-cpp.md @@ -1,7 +1,7 @@ --- description: "Learn more about: Walkthrough: Working with Projects and Solutions (C++)" title: "Walkthrough: Working with Projects and Solutions (C++)" -ms.date: "05/14/2019" +ms.date: 10/27/2021 helpviewer_keywords: ["solutions [C++]", "projects [C++], about projects", "projects [C++]", "solutions [C++], about solutions"] ms.assetid: 93a3f290-e294-46e3-876e-e3084d9ae833 --- @@ -21,9 +21,9 @@ It helps if you understand the fundamentals of the C++ language, and know what a To create a project, first choose a project-type template. For each project type, Visual Studio sets compiler settings and—depending on the type—generates starter code that you can modify later. The following steps vary depending on which version of Visual Studio you are using. To see the documentation for your preferred version of Visual Studio, use the **Version** selector control. It's found at the top of the table of contents on this page. -::: moniker range="msvc-160" +::: moniker range=">=msvc-160" -### To create a project in Visual Studio 2019 +### To create a project in Visual Studio 1. From the main menu, choose **File** > **New** > **Project** to open the **Create a New Project** dialog box. diff --git a/docs/ide/writing-and-refactoring-code-cpp.md b/docs/ide/writing-and-refactoring-code-cpp.md index 587561360c8..e66b2b391fb 100644 --- a/docs/ide/writing-and-refactoring-code-cpp.md +++ b/docs/ide/writing-and-refactoring-code-cpp.md @@ -33,9 +33,9 @@ When writing C++, IntelliCode will assist when using popular libraries such as t ![Screenshot of C++ IntelliCode.](../ide/media/intellicode-cpp.png "C++ IntelliCode") -::: moniker range="msvc-160" +::: moniker range=">=msvc-160" -In Visual Studio 2019, IntelliCode is available as an optional component in the **C++ Desktop Development** workload. To make sure that IntelliCode is active for C++, go to **Tools** > **Options** > **IntelliCode** > **General** and set **C++ base model** to **Enabled**. +In Visual Studio 2022 and Visual Studio 2019, IntelliCode is available as an optional component in the **C++ Desktop Development** workload. To make sure that IntelliCode is active for C++, go to **Tools** > **Options** > **IntelliCode** > **General** and set **C++ base model** to **Enabled**. ::: moniker-end diff --git a/docs/intrinsics/interlockedcompareexchange-intrinsic-functions.md b/docs/intrinsics/interlockedcompareexchange-intrinsic-functions.md index 9924b8a155a..db8af5eed10 100644 --- a/docs/intrinsics/interlockedcompareexchange-intrinsic-functions.md +++ b/docs/intrinsics/interlockedcompareexchange-intrinsic-functions.md @@ -1,9 +1,9 @@ --- description: "Learn more about: _InterlockedCompareExchange intrinsic functions" title: "_InterlockedCompareExchange intrinsic functions" -ms.date: "09/02/2019" -f1_keywords: ["_InterlockedCompareExchange_HLERelease", "_InterlockedCompareExchange8_nf", "_InterlockedCompareExchange16_acq_cpp", "_InterlockedCompareExchange_acq_cpp", "_InterlockedCompareExchange16_rel_cpp", "_InterlockedCompareExchange64_rel_cpp", "_InterlockedCompareExchange_cpp", "_InterlockedCompareExchange16_cpp", "_InterlockedCompareExchange64_acq_cpp", "_InterlockedCompareExchange_acq", "_InterlockedCompareExchange64_rel", "_InterlockedCompareExchange64_nf", "_InterlockedCompareExchange_rel_cpp", "_InterlockedCompareExchange16_nf", "_InterlockedCompareExchange8", "_InterlockedCompareExchange64_np", "_InterlockedCompareExchange16_rel", "_InterlockedCompareExchange64_acq", "_InterlockedCompareExchange8_rel", "_InterlockedCompareExchange_HLEAcquire", "_InterlockedCompareExchange64_HLERelease", "_InterlockedCompareExchange64_cpp", "_InterlockedCompareExchange_np", "_InterlockedCompareExchange8_acq", "_InterlockedCompareExchange16_acq", "_InterlockedCompareExchange_rel", "_InterlockedCompareExchange64_HLEAcquire", "_InterlockedCompareExchange64", "_InterlockedCompareExchange16", "_InterlockedCompareExchange"] -helpviewer_keywords: ["_InterlockedCompareExchange16 intrinsic", "_InterlockedCompareExchange_acq intrinsic", "InterlockedCompareExchange_acq intrinsic", "_InterlockedCompareExchange intrinsic", "InterlockedCompareExchange64 intrinsic", "_InterlockedCompareExchange64_acq intrinsic", "InterlockedCompareExchange16 intrinsic", "_InterlockedCompareExchange_rel intrinsic", "InterlockedCompareExchange intrinsic", "InterlockedCompareExchange64_acq intrinsic", "InterlockedCompareExchange_rel intrinsic", "_InterlockedCompareExchange64 intrinsic", "InterlockedCompareExchange64_rel intrinsic", "_InterlockedCompareExchange64_rel intrinsic"] +ms.date: 10/27/2021 +f1_keywords: ["_InterlockedCompareExchange", "_InterlockedCompareExchange_acq", "_InterlockedCompareExchange_acq_cpp", "_InterlockedCompareExchange_cpp", "_InterlockedCompareExchange_HLEAcquire", "_InterlockedCompareExchange_HLERelease", "_InterlockedCompareExchange_nf", "_InterlockedCompareExchange_np", "_InterlockedCompareExchange_rel", "_InterlockedCompareExchange_rel_cpp", "_InterlockedCompareExchange8", "_InterlockedCompareExchange8_acq", "_InterlockedCompareExchange8_nf", "_InterlockedCompareExchange8_rel", "_InterlockedCompareExchange16", "_InterlockedCompareExchange16_acq", "_InterlockedCompareExchange16_acq_cpp", "_InterlockedCompareExchange16_cpp", "_InterlockedCompareExchange16_nf", "_InterlockedCompareExchange16_rel", "_InterlockedCompareExchange16_rel_cpp", "_InterlockedCompareExchange64", "_InterlockedCompareExchange64_acq", "_InterlockedCompareExchange64_acq_cpp", "_InterlockedCompareExchange64_cpp", "_InterlockedCompareExchange64_HLEAcquire", "_InterlockedCompareExchange64_HLERelease", "_InterlockedCompareExchange64_nf", "_InterlockedCompareExchange64_np", "_InterlockedCompareExchange64_rel", "_InterlockedCompareExchange64_rel_cpp"] +helpviewer_keywords: ["_InterlockedCompareExchange intrinsic", "_InterlockedCompareExchange_acq intrinsic", "_InterlockedCompareExchange_acq_cpp intrinsic", "_InterlockedCompareExchange_cpp intrinsic", "_InterlockedCompareExchange_HLEAcquire intrinsic", "_InterlockedCompareExchange_HLERelease intrinsic", "_InterlockedCompareExchange_nf intrinsic", "_InterlockedCompareExchange_np intrinsic", "_InterlockedCompareExchange_rel intrinsic", "_InterlockedCompareExchange_rel_cpp intrinsic", "_InterlockedCompareExchange8 intrinsic", "_InterlockedCompareExchange8_acq intrinsic", "_InterlockedCompareExchange8_nf intrinsic", "_InterlockedCompareExchange8_rel intrinsic", "_InterlockedCompareExchange16 intrinsic", "_InterlockedCompareExchange16_acq intrinsic", "_InterlockedCompareExchange16_acq_cpp intrinsic", "_InterlockedCompareExchange16_cpp intrinsic", "_InterlockedCompareExchange16_nf intrinsic", "_InterlockedCompareExchange16_rel intrinsic", "_InterlockedCompareExchange16_rel_cpp intrinsic", "_InterlockedCompareExchange64 intrinsic", "_InterlockedCompareExchange64_acq intrinsic", "_InterlockedCompareExchange64_acq_cpp intrinsic", "_InterlockedCompareExchange64_cpp intrinsic", "_InterlockedCompareExchange64_HLEAcquire intrinsic", "_InterlockedCompareExchange64_HLERelease intrinsic", "_InterlockedCompareExchange64_nf intrinsic", "_InterlockedCompareExchange64_np intrinsic", "_InterlockedCompareExchange64_rel intrinsic", "_InterlockedCompareExchange64_rel_cpp intrinsic"] ms.assetid: c3ad79c0-a523-4930-a3a4-69a65d7d5c81 --- # _InterlockedCompareExchange intrinsic functions @@ -35,6 +35,11 @@ long _InterlockedCompareExchange_HLERelease( long Exchange, long Comparand ); +long _InterlockedCompareExchange_nf( + long volatile * Destination, + long Exchange, + long Comparand +); long _InterlockedCompareExchange_np( long volatile * Destination, long Exchange, @@ -147,7 +152,7 @@ The return value is the initial value of the `Destination` pointer. |Intrinsic|Architecture|Header| |---------------|------------------|------------| |`_InterlockedCompareExchange`, `_InterlockedCompareExchange8`, `_InterlockedCompareExchange16`, `_InterlockedCompareExchange64`|x86, ARM, x64, ARM64|\| -|`_InterlockedCompareExchange_acq`, `_InterlockedCompareExchange_rel`, `_InterlockedCompareExchange8_acq`, `_InterlockedCompareExchange8_nf`, `_InterlockedCompareExchange8_rel`,`_InterlockedCompareExchange16_acq`, `_InterlockedCompareExchange16_nf`, `_InterlockedCompareExchange16_rel`, `_InterlockedCompareExchange64_acq`, `_InterlockedCompareExchange64_nf`, `_InterlockedCompareExchange64_rel`,|ARM, ARM64|\| +|`_InterlockedCompareExchange_acq`, `_InterlockedCompareExchange_nf`, `_InterlockedCompareExchange_rel`, `_InterlockedCompareExchange8_acq`, `_InterlockedCompareExchange8_nf`, `_InterlockedCompareExchange8_rel`,`_InterlockedCompareExchange16_acq`, `_InterlockedCompareExchange16_nf`, `_InterlockedCompareExchange16_rel`, `_InterlockedCompareExchange64_acq`, `_InterlockedCompareExchange64_nf`, `_InterlockedCompareExchange64_rel`,|ARM, ARM64|\| |`_InterlockedCompareExchange_np`, `_InterlockedCompareExchange16_np`, `_InterlockedCompareExchange64_np`|x64|\| |`_InterlockedCompareExchange_HLEAcquire`, `_InterlockedCompareExchange_HLERelease`, `_InterlockedCompareExchange64_HLEAcquire`, `_InterlockedCompareExchange64_HLERelease`|x86, x64|\| @@ -161,7 +166,7 @@ There are several variations on `_InterlockedCompareExchange` that vary based on While the `_InterlockedCompareExchange` function operates on long integer values, `_InterlockedCompareExchange8` operates on 8-bit integer values, `_InterlockedCompareExchange16` operates on short integer values, and `_InterlockedCompareExchange64` operates on 64-bit integer values. -On ARM platforms, use the intrinsics with `_acq` and `_rel` suffixes for acquire and release semantics, such as at the beginning and end of a critical section. The ARM intrinsics with an `_nf` ("no fence") suffix don't act as a memory barrier. +On all ARM platforms, use the intrinsics with `_acq` and `_rel` suffixes for acquire and release semantics, such as at the beginning and end of a critical section. The ARM intrinsics with an `_nf` ("no fence") suffix don't act as a memory barrier. The intrinsics with an `_np` ("no prefetch") suffix prevent a possible prefetch operation from being inserted by the compiler. diff --git a/docs/intrinsics/interlockedcompareexchangepointer-intrinsic-functions.md b/docs/intrinsics/interlockedcompareexchangepointer-intrinsic-functions.md index 27cb168956d..56a4d6a0ea1 100644 --- a/docs/intrinsics/interlockedcompareexchangepointer-intrinsic-functions.md +++ b/docs/intrinsics/interlockedcompareexchangepointer-intrinsic-functions.md @@ -45,7 +45,7 @@ void * _InterlockedCompareExchangePointer_np ( void * Exchange, void * Comparand ); -long _InterlockedCompareExchangePointer_rel ( +void * _InterlockedCompareExchangePointer_rel ( void * volatile * Destination, void * Exchange, void * Comparand diff --git a/docs/intrinsics/interlockedor-intrinsic-functions.md b/docs/intrinsics/interlockedor-intrinsic-functions.md index 3af2b8d172d..652661f0226 100644 --- a/docs/intrinsics/interlockedor-intrinsic-functions.md +++ b/docs/intrinsics/interlockedor-intrinsic-functions.md @@ -45,7 +45,7 @@ long _InterlockedOr_rel( ); char _InterlockedOr8( char volatile * Value, - long Mask + char Mask ); char _InterlockedOr8_acq( char volatile * Value, diff --git a/docs/linux/cmake-linux-configure.md b/docs/linux/cmake-linux-configure.md index fa0b3d00d8a..6279e330017 100644 --- a/docs/linux/cmake-linux-configure.md +++ b/docs/linux/cmake-linux-configure.md @@ -50,8 +50,8 @@ The default configuration for Linux-Debug in Visual Studio 2017 (and Visual Stud ::: moniker-end -::: moniker range="msvc-160" -To change the default CMake settings in Visual Studio 2019, from the main toolbar, open the **Configuration** dropdown and choose **Manage Configurations**. +::: moniker range=">=msvc-160" +To change the default CMake settings in Visual Studio 2019 or later, from the main toolbar, open the **Configuration** dropdown and choose **Manage Configurations**. ![Screenshot showing CMake Manage Configurations highlighted in the Configuration dropdown.](../build/media/vs2019-cmake-manage-configurations.png "CMake configurations drop-down") @@ -107,7 +107,7 @@ After you select a target, CMake runs automatically on the Linux system to gener ![Screenshot of Visual Studio showing the output of Generate CMake cache on Linux.](media/cmake-linux-1.png "Generate the CMake cache on Linux") ::: moniker-end -::: moniker range="msvc-160" +::: moniker range=">=msvc-160" ### Target Windows Subsystem for Linux diff --git a/docs/linux/configure-a-linux-project.md b/docs/linux/configure-a-linux-project.md index 3049e8b68d0..88ef152274b 100644 --- a/docs/linux/configure-a-linux-project.md +++ b/docs/linux/configure-a-linux-project.md @@ -16,9 +16,9 @@ This topic describes how to configure a MSBuild-based Linux project as described You can configure a Linux project to target a physical Linux machine, a virtual machine, or the [Windows Subsystem for Linux](/windows/wsl/about) (WSL). -::: moniker range="msvc-160" +::: moniker range=">=msvc-160" -**Visual Studio 2019 version 16.1**: +**Visual Studio 2019 version 16.1** and later: - When you target WSL, you can avoid the copy operations needed to build and get IntelliSense that are required when you target a remote Linux system. @@ -48,9 +48,9 @@ To change settings related to the remote Linux computer, configure the remote se ![Screenshot showing the Remote Build Machine.](media/remote-build-machine-vs2019.png) - ::: moniker range="msvc-160" + ::: moniker range=">=msvc-160" - **Visual Studio 2019 version 16.7**: To target Windows Subsystem for Linux (WSL), set the **Platform Toolset** drop-down to **GCC for Windows Subsystem for Linux**. The other remote options will disappear and the path to the default WSL shell will appear in their place: + **Visual Studio 2019 version 16.7** and later: To target Windows Subsystem for Linux (WSL), set the **Platform Toolset** drop-down to **GCC for Windows Subsystem for Linux**. The other remote options will disappear and the path to the default WSL shell will appear in their place: ![Screenshot showing the WSL build machine.](media/wsl-remote-vs2019.png) @@ -69,9 +69,10 @@ To change settings related to the remote Linux computer, configure the remote se ## Copy sources (remote systems only) -::: moniker range="msvc-160" +::: moniker range=">=msvc-160" -This section doesn't apply when targeting WSL. +> [!NOTE] +> This section doesn't apply when targeting WSL. ::: moniker-end @@ -112,7 +113,7 @@ To manage your header cache, navigate to **Tools > Options, Cross Platform > Con ::: moniker-end -::: moniker range="msvc-160" +::: moniker range=">=msvc-160" ![Screenshot showing the Options dialog box with Cross Platform > Connection Manager selected.](media/connection-manager-vs2019.png) diff --git a/docs/linux/connect-to-your-remote-linux-computer.md b/docs/linux/connect-to-your-remote-linux-computer.md index 83fa41248e3..050ef04d0a3 100644 --- a/docs/linux/connect-to-your-remote-linux-computer.md +++ b/docs/linux/connect-to-your-remote-linux-computer.md @@ -17,7 +17,7 @@ You can configure a Linux project to target a remote machine or the Windows Subs ::: moniker-end -::: moniker range="msvc-160" +::: moniker range=">=msvc-160" You can configure a Linux project to target a remote machine or the Windows Subsystem for Linux (WSL). For a remote machine, you need to set up a remote connection in Visual Studio. To connect to WSL, skip ahead to the [Connect to WSL](#connect-to-wsl) section. @@ -30,10 +30,10 @@ To build the project, Visual Studio copies the source code to your remote Linux ::: moniker-end -::: moniker range="msvc-160" +::: moniker range=">=msvc-160" > [!NOTE] -> Visual Studio 2019 version 16.5 and later also supports secure, Federal Information Processing Standard (FIPS) 140-2 compliant cryptographic connections to Linux systems for remote development. To use a FIPS-compliant connection, follow the steps in [Set up FIPS-compliant secure remote Linux development](set-up-fips-compliant-secure-remote-linux-development.md) instead. +> Starting in Visual Studio 2019 version 16.5, Visual Studio supports secure, Federal Information Processing Standard (FIPS) 140-2 compliant cryptographic connections to Linux systems for remote development. To use a FIPS-compliant connection, follow the steps in [Set up FIPS-compliant secure remote Linux development](set-up-fips-compliant-secure-remote-linux-development.md) instead. ::: moniker-end @@ -205,10 +205,8 @@ The `rsync` command is used by both MSBuild-based Linux projects and CMake proje ![Screenshot showing an Rsync Error.](media/port-forwarding-copy-error.png) - `gdbserver` can be used for debugging on embedded devices. If you can't enable TCP port forwarding, then you must use `gdb` for all remote debugging scenarios. `gdb` is used by default when debugging projects on a remote system. - Visual Studio's Linux support has a dependency on TCP port forwarding. Both `rsync` and `gdbserver` are affected if TCP port forwarding is disabled on your remote system. If this dependency impacts you, vote for this [suggestion ticket](https://developercommunity2.visualstudio.com/t/shDonshshtsh-shrelysh-s/840265?space=62) on Developer Community. ## Connect to WSL @@ -221,9 +219,9 @@ In Visual Studio 2017, you use the same steps to connect to WSL as you use for a ::: moniker-end -::: moniker range="msvc-160" +::: moniker range=">=msvc-160" -Visual Studio 2019 version 16.1 added native support for using C++ with the [Windows Subsystem for Linux (WSL)](/windows/wsl/about). That means you can build and debug on your local WSL installation directly. You no longer need to add a remote connection or configure SSH. You can find details on [how to install WSL](/windows/wsl/install-win10) here. +Starting in Visual Studio 2019 version 16.1, Visual Studio has native support for using C++ with the [Windows Subsystem for Linux (WSL)](/windows/wsl/about). That means you can build and debug on your local WSL installation directly. You no longer need to add a remote connection or configure SSH. You can find details on [how to install WSL](/windows/wsl/install-win10) here. To configure your WSL installation to work with Visual Studio, you need the following tools installed: `gcc` or `clang`, `gdb`, `make`, `ninja-build` (only required for CMake projects using Visual Studio 2019 version 16.6 or later), `rsync`, and `zip`. You can install them on distros that use `apt` by using this command, which also installs the g++ compiler: diff --git a/docs/linux/connectionmanager-reference.md b/docs/linux/connectionmanager-reference.md index 60a3fb677e6..ac182b89902 100644 --- a/docs/linux/connectionmanager-reference.md +++ b/docs/linux/connectionmanager-reference.md @@ -13,7 +13,7 @@ ConnectionManager.exe is available in Visual Studio 2019 version 16.5 and later. ::: moniker-end -::: moniker range="msvc-160" +::: moniker range=">=msvc-160" ConnectionManager.exe is a command-line utility to manage remote development connections outside of Visual Studio. It's useful for tasks such as provisioning a new development machine. Or, use it to set up Visual Studio for continuous integration. You can use it in a Developer Command Prompt window. For more information about the Developer Command Prompt, see [Use the Microsoft C++ toolset from the command line](../build/building-on-the-command-line.md). diff --git a/docs/linux/create-a-new-linux-project.md b/docs/linux/create-a-new-linux-project.md index b4280585863..d2d98e79f44 100644 --- a/docs/linux/create-a-new-linux-project.md +++ b/docs/linux/create-a-new-linux-project.md @@ -36,7 +36,7 @@ To create a new Linux project in Visual Studio 2017, follow these steps: ::: moniker-end -::: moniker range="msvc-160" +::: moniker range=">=msvc-160" First, make sure you have the **Linux Development Workload** for Visual Studio installed. For more information, see [Download, install, and set up the Linux workload](download-install-and-setup-the-linux-development-workload.md). @@ -46,7 +46,7 @@ If you have an existing Windows Visual Studio solution that you would like to ex ## Create a new Linux project -To create a new Linux project in Visual Studio 2019, follow these steps: +To create a new Linux project in Visual Studio, follow these steps: 1. Select **File > New Project** in Visual Studio, or press **Ctrl + Shift + N**. The Create a new project dialog appears. 1. In the **Search for templates** textbox, enter **Linux** to list the available templates for Linux projects. diff --git a/docs/linux/deploy-run-and-debug-your-linux-project.md b/docs/linux/deploy-run-and-debug-your-linux-project.md index 46a91bf27b5..e7911b3e5bc 100644 --- a/docs/linux/deploy-run-and-debug-your-linux-project.md +++ b/docs/linux/deploy-run-and-debug-your-linux-project.md @@ -13,9 +13,9 @@ Linux support is available in Visual Studio 2017 and later. To see the documenta Once you've created a MSBuild-based Linux C++ project in Visual Studio and you've connected to the project using the [Linux Connection Manager](connect-to-your-remote-linux-computer.md), you can run and debug the project. You compile, execute, and debug the code on the remote target. -::: moniker range="msvc-160" +::: moniker range=">=msvc-160" -**Visual Studio 2019 version 16.1** You can target different Linux systems for debugging and building. For example, you can cross-compile on x64 and deploy to an ARM device when targeting IoT scenarios. For more information, see [Specify different machines for building and debugging](#separate_build_debug) later in this article. +**Visual Studio 2019 version 16.1** and later: You can target different Linux systems for debugging and building. For example, you can cross-compile on x64 and deploy to an ARM device when targeting IoT scenarios. For more information, see [Specify different machines for building and debugging](#separate_build_debug) later in this article. ::: moniker-end @@ -29,11 +29,11 @@ There are several ways to interact with and debug your Linux project. 1. Select debugging mode in the **Debugging** property page. - ::: moniker range="msvc-160" + ::: moniker range=">=msvc-160" GDB is used to debug applications running on Linux. When debugging on a remote system (not WSL) GDB can run in two different modes, which can be selected from the **Debugging Mode** option in the project's **Debugging** property page: - ![Screenshot of the Visual Studio 2019 Linux Console App Property Pages dialog box with Configuration Properties > Debugging selected and Debugging Mode highlighted with G B D selected and highlighted from the dropdown list.](media/vs2019-debugger-settings.png) + ![Screenshot of the Visual Studio Linux Console App Property Pages dialog box with Configuration Properties > Debugging selected and Debugging Mode highlighted with G D B selected and highlighted from the dropdown list.](media/vs2019-debugger-settings.png) ::: moniker-end @@ -41,7 +41,7 @@ There are several ways to interact with and debug your Linux project. GDB is used to debug applications running on Linux. GDB can run in two different modes, which can be selected from the **Debugging Mode** option in the project's **Debugging** property page: - ![Screenshot of the Visual Studio 2017 Linux Console App Property Pages dialog box with Configuration Properties > Debugging selected and Debugging Mode highlighted with G B D selected and highlighted from the dropdown list.](media/vs2017-debugger-settings.png) + ![Screenshot of the Visual Studio 2017 Linux Console App Property Pages dialog box with Configuration Properties > Debugging selected and Debugging Mode highlighted with G D B selected and highlighted from the dropdown list.](media/vs2017-debugger-settings.png) ::: moniker-end @@ -118,11 +118,11 @@ ExePath="C:\temp\ConsoleApplication17\ConsoleApplication17\bin\x64\Debug\Console The **AttachOptionsForConnection** has most of the attributes you might need. The example above shows how to specify a location to search for additional .so libraries. The child element **ServerOptions** enables attaching to the remote process with gdbserver instead. To do that, you need to specify a local gdb client (the one shipped in Visual Studio 2017 is shown above) and a local copy of the binary with symbols. The **SetupCommands** element enables you to pass commands directly to gdb. You can find all the options available in the [LaunchOptions.xsd schema](https://github.com/Microsoft/MIEngine/blob/master/src/MICore/LaunchOptions.xsd) on GitHub. -::: moniker range="msvc-160" +::: moniker range=">=msvc-160" ## Specify different machines for building and debugging in MSBuild-based Linux projects -In Visual Studio 2019 version 16.1, you can separate your remote build machine from your remote debug machine for both MSBuild-based Linux projects and CMake projects that target a remote Linux machine. For example, you can now cross-compile on x64 and deploy to an ARM device when targeting IoT scenarios. +You can separate your remote build machine from your remote debug machine for both MSBuild-based Linux projects and CMake projects that target a remote Linux machine. For example, you can now cross-compile on x64 and deploy to an ARM device when targeting IoT scenarios. By default, the remote debug machine is the same as the remote build machine (**Configuration Properties** > **General** > **Remote Build Machine**). To specify a new remote debug machine, right-click on the project in **Solution Explorer** and go to **Configuration Properties** > **Debugging** > **Remote Debug Machine**. diff --git a/docs/linux/download-install-and-setup-the-linux-development-workload.md b/docs/linux/download-install-and-setup-the-linux-development-workload.md index 416cf3e66a2..102bfca8ada 100644 --- a/docs/linux/download-install-and-setup-the-linux-development-workload.md +++ b/docs/linux/download-install-and-setup-the-linux-development-workload.md @@ -47,11 +47,11 @@ On Windows 10 and later, you can install and target your favorite Linux distro o ::: moniker-end -::: moniker range="msvc-160" +::: moniker range=">=msvc-160" Linux projects in Visual Studio require the following dependencies to be installed on your remote Linux system or WSL: -- **A compiler** - Visual Studio 2019 has full support for GCC and [Clang](../build/clang-support-cmake.md). +- **A compiler** - Visual Studio 2019 and later have full support for GCC and [Clang](../build/clang-support-cmake.md). - **gdb** - Visual Studio automatically launches gdb on the Linux system, and uses the front end of the Visual Studio debugger to provide a full-fidelity debugging experience on Linux. - **rsync** and **zip** - the inclusion of rsync and zip allows Visual Studio to extract header files from your Linux system to the Windows filesystem for use by IntelliSense. - **make** @@ -76,7 +76,7 @@ Linux projects in Visual Studio require the following dependencies to be install ::: moniker-end -::: moniker range="msvc-160" +::: moniker range=">=msvc-160" ## Linux setup: Ubuntu on WSL @@ -112,7 +112,7 @@ The target Linux system must have **openssh-server**, **g++**, **gdb**, and **ma ::: moniker-end -::: moniker range="msvc-160" +::: moniker range=">=msvc-160" ## Fedora on WSL diff --git a/docs/linux/set-up-fips-compliant-secure-remote-linux-development.md b/docs/linux/set-up-fips-compliant-secure-remote-linux-development.md index 02e67a5e5f7..791a759d80e 100644 --- a/docs/linux/set-up-fips-compliant-secure-remote-linux-development.md +++ b/docs/linux/set-up-fips-compliant-secure-remote-linux-development.md @@ -11,7 +11,7 @@ Linux support is available in Visual Studio 2017 and later. FIPS-compliant secur ::: moniker-end -::: moniker range="msvc-160" +::: moniker range=">=msvc-160" Federal Information Processing Standard (FIPS) Publication 140-2 is a U.S. government standard for cryptographic modules. Implementations of the standard are validated by NIST. Windows has [validated support for FIPS-compliant cryptographic modules](/windows/security/threat-protection/fips-140-validation). In Visual Studio 2019 version 16.5 and later, you can use a secure, FIPS-compliant cryptographic connection to your Linux system for remote development. diff --git a/docs/mfc/reference/add-class-from-typelib-wizard.md b/docs/mfc/reference/add-class-from-typelib-wizard.md index d678d414d1a..763e2a47172 100644 --- a/docs/mfc/reference/add-class-from-typelib-wizard.md +++ b/docs/mfc/reference/add-class-from-typelib-wizard.md @@ -7,7 +7,7 @@ ms.assetid: 96152afd-9374-4649-a6ab-b0fa2a5592a3 --- # Add Class from Typelib Wizard -::: moniker range="msvc-160" +::: moniker range=">=msvc-160" This wizard is not available in Visual Studio 2019 and later. diff --git a/docs/mfc/reference/mfc-odbc-consumer-wizard.md b/docs/mfc/reference/mfc-odbc-consumer-wizard.md index bc98f7967b1..4b3754189d2 100644 --- a/docs/mfc/reference/mfc-odbc-consumer-wizard.md +++ b/docs/mfc/reference/mfc-odbc-consumer-wizard.md @@ -7,7 +7,7 @@ ms.assetid: f64a890b-a252-4887-88a1-782a7cd4ff3d --- # MFC ODBC Consumer Wizard -::: moniker range="msvc-160" +::: moniker range=">=msvc-160" This wizard is not available in Visual Studio 2019 and later. diff --git a/docs/mfc/walkthrough-using-the-new-mfc-shell-controls.md b/docs/mfc/walkthrough-using-the-new-mfc-shell-controls.md index e4bf0040c39..35d503d1884 100644 --- a/docs/mfc/walkthrough-using-the-new-mfc-shell-controls.md +++ b/docs/mfc/walkthrough-using-the-new-mfc-shell-controls.md @@ -1,7 +1,7 @@ --- description: "Learn more about: Walkthrough: Using the New MFC Shell Controls" title: "Walkthrough: Using the New MFC Shell Controls" -ms.date: "04/25/2019" +ms.date: 10/27/2021 helpviewer_keywords: ["shell controls (MFC)"] ms.assetid: f0015caa-199d-4aaf-9501-5a239fce9095 --- @@ -19,9 +19,9 @@ In this walkthrough, you'll create an application that resembles File Explorer. These steps vary depending on which version of Visual Studio you are using. To see the documentation for your preferred version of Visual Studio, use the **Version** selector control. It's found at the top of the table of contents on this page. -::: moniker range="msvc-160" +::: moniker range=">=msvc-160" -### To create an MFC project in Visual Studio 2019 +### To create an MFC project in Visual Studio 1. From the main menu, choose **File** > **New** > **Project** to open the **Create a New Project** dialog box. diff --git a/docs/overview/install-c17-support.md b/docs/overview/install-c17-support.md index 654c5c76a2b..22e6be5a47b 100644 --- a/docs/overview/install-c17-support.md +++ b/docs/overview/install-c17-support.md @@ -1,7 +1,7 @@ --- title: Install C11 and C17 support in Visual Studio description: "Install Windows SDK and CRT support for C11 and C17 in Visual Studio" -ms.date: 06/29/2021 +ms.date: 10/27/2021 helpviewer_keywords: ["Install Windows SDK support for C"] ms.custom: intro-installation --- @@ -13,49 +13,23 @@ Support for C11 and C17 standards requires Visual Studio 2019 version 16.8 or la ::: moniker-end -::: moniker range="msvc-160" +::: moniker range=">=msvc-160" -Support for C11 and C17 standards is available starting in Visual Studio 2019 version 16.8. Support requires an updated Universal C Runtime (UCRT) and the latest Windows SDK updates, to work properly with the conforming preprocessor ([`/Zc:preprocessor`](../build/reference/zc-preprocessor.md)). +Support for C11 and C17 standards is available in Visual Studio 2019 version 16.8 and later. Support requires an updated Universal C Runtime (UCRT) and Windows SDK version to work properly with the conforming preprocessor ([`/Zc:preprocessor`](../build/reference/zc-preprocessor.md)). -Windows SDK releases correspond with Windows OS releases. C11 and C17 support requires Windows SDK 10.0.20348.0 (version 2104) or later. Normally, the Windows SDK is an installable option in the Individual Components tab in the Visual Studio Installer. That's the recommended way to update the SDK for use with Visual Studio. However, at the time of writing, the latest Windows SDK isn't available in the Visual Studio Installer. You can follow these steps to set up the latest SDK and build C11 or C17 code in Visual Studio or at the command line. +Windows SDK releases correspond with Windows OS releases. C11 and C17 support requires Windows SDK 10.0.20348.0 (version 2104) or later. The Windows SDK is an installable option in the **Individual Components** tab in the Visual Studio Installer. You can follow these steps to set up the latest SDK and build C11 or C17 code in Visual Studio or at the command line. ## Prerequisites -- Visual Studio 2019 version 16.8 or later installed and running on your computer. We recommend you use the latest version available for the best support. If Visual Studio isn't installed yet, see [Install C++ support in Visual Studio](../build/vscpp-step-0-installation.md) for installation instructions. In the install, include the **Desktop development with C++** workload. +Visual Studio 2019 version 16.8 or later and Windows SDK 10.0.20348.0 (version 2104) or later installed and running on your computer. We recommend you use the latest version available for the best support. -## Step 1: Download the Windows SDK +- If Visual Studio isn't installed yet, see [Install C++ support in Visual Studio](../build/vscpp-step-0-installation.md) for installation instructions. In the install, include the **Desktop development with C++** workload. Then, open the Individual Components tab. Select Windows 10 SDK (10.0.20348.0) or later, or the latest Windows 11 SDK. -You can download the latest Windows SDK from the [Windows SDK](https://developer.microsoft.com/windows/downloads/windows-sdk/) page. If you see a message that says "We are sorry, the page you requested cannot be found," try changing the locale in the URL to *en-us*. +- If Visual Studio is already installed, but you don't have the required Windows SDK, open the Visual Studio Installer. Choose **Modify** next to your version of Visual Studio to install the selected components. Open the Individual Components tab. Select Windows 10 SDK (10.0.20348.0) or later, or the latest Windows 11 SDK. Choose **Modify** to install the selected components. -Choose **Download the installer** to begin the download. If you've already installed Windows 10 SDK version 2104 (10.0.20348.0), that version will also work. +When installation completes, open Visual Studio. -When the download completes, open the folder for the downloaded file. It's usually your Downloads folder, and the file is typically named *`winsdksetup.exe`*. Right-click on the file to open the file's **Properties** dialog box. On the **General** tab, in the **Security** section, check the **Unblock** checkbox. Choose **OK** to save your changes. - -## Step 2: Install the Windows SDK - -Run *`winsdksetup.exe`* to start the installation. - -On the **Specify Location** page, select **Install the Windows Software Development Kit - \ to this computer**, and then choose **Next**. On the **Windows Kits Privacy** page, select whether to allow Microsoft to collect insights for the Windows Kits, then choose **Next**. Choose **Accept** to accept the license agreement. On the **Select the features you want to install** page, select at least these features: - -- Windows SDK Signing Tools for Desktop Apps - -- Windows SDK for UWP Managed Apps - -- Windows SDK for UWP C++ Apps - -- Windows SDK for Desktop C++ x86 Apps (if you plan to build for x86) - -- Windows SDK for Desktop C++ amd64 Apps (if you plan to build for x64) - -- Windows SDK for Desktop C++ arm Apps (if you plan to build for ARM) - -- Windows SDK for Desktop C++ arm64 Apps (if you plan to build for ARM64) - -![A screenshot of the Windows SDK installer, showing the components selected for installation.](media/c11-7-windows-sdk-installer-select-features.png) - -Choose **Install** to install the selected SDK components. The SDK takes a couple of minutes to complete installation. When it completes, open Visual Studio. - -## Step 3: Configuring C11 or C17 mode in Visual Studio +## Configure C11 or C17 mode in Visual Studio In Visual Studio, open a new or existing C project, then open your project's **Property Pages** dialog. diff --git a/docs/overview/overview-of-cpp-development.md b/docs/overview/overview-of-cpp-development.md index 4bd1565e38f..c982da95934 100644 --- a/docs/overview/overview-of-cpp-development.md +++ b/docs/overview/overview-of-cpp-development.md @@ -20,15 +20,15 @@ Visual Studio provides support for any project system or custom build tools that - **MSBuild** is the native project system for Visual Studio. When you select **File** > **New** > **Project** from the main menu, you see many kinds of MSBuild *project templates* that get you started quickly developing different kinds of C++ applications. - ::: moniker range="msvc-160" + ::: moniker range=">=msvc-160" - ![Screenshot of the Create a new Project dialog showing new project templates.](../build/media/mathclient-project-name-2019.png "Visual Studio 2019 New Project Dialog") + ![Screenshot of the Create a new Project dialog showing new project templates.](../build/media/mathclient-project-name-2019.png) ::: moniker-end ::: moniker range="<=msvc-150" - ![Screenshot of the New Project dialog showing project templates.](media/vs2017-new-project.png "Visual Studio 2017 New Project Dialog") + ![Screenshot of the New Project dialog showing project templates.](media/vs2017-new-project.png) ::: moniker-end @@ -42,15 +42,15 @@ Visual Studio provides support for any project system or custom build tools that Source control enables you to coordinate work among multiple developers, isolate in-progress work from production code, and backup your source code. Visual Studio supports Git and [Team Foundation Version Control \(TFVC\)](/azure/devops/repos/tfvc/) through its **Team Explorer** window. -::: moniker range="msvc-160" +::: moniker range=">=msvc-160" -![Screenshot of the Team Explorer window in Visual Studio 2019.](media/vs2019-team-explorer.png "Visual Studio 2017 Team Explorer") +![Screenshot of the Team Explorer window in Visual Studio 2019.](media/vs2019-team-explorer.png ) ::: moniker-end ::: moniker range="<=msvc-150" -![Screenshot of the Team Explorer window in Visual Studio 2017.](media/vs2017-team-explorer.png "Visual Studio 2017 Team Explorer") +![Screenshot of the Team Explorer window in Visual Studio 2017.](media/vs2017-team-explorer.png ) ::: moniker-end @@ -58,7 +58,7 @@ For more information about Git integration with repos in Azure, see [Share your ## Obtain libraries -Use the [vcpkg](https://vcpkg.io/) package manager to obtain and install third-party libraries. Over 900 open-source libraries are currently available in the catalog. +Use the [vcpkg](https://vcpkg.io/) package manager to obtain and install third-party libraries. Over 1700 open-source library packages are currently available in the catalog. ## Create user interfaces with designers diff --git a/docs/overview/visual-cpp-tools-and-features-in-visual-studio-editions.md b/docs/overview/visual-cpp-tools-and-features-in-visual-studio-editions.md index 1c2c04f0dcf..574632ffc85 100644 --- a/docs/overview/visual-cpp-tools-and-features-in-visual-studio-editions.md +++ b/docs/overview/visual-cpp-tools-and-features-in-visual-studio-editions.md @@ -1,7 +1,7 @@ --- description: "Learn more about: C++ Tools and Features in Visual Studio Editions" title: "C++ Tools and Features in Visual Studio Editions" -ms.date: "05/21/2019" +ms.date: 10/27/2021 helpviewer_keywords: ["tools and platforms [C++]"] ms.assetid: 3d88607b-9cc4-490a-8d4c-31ee7610a26f --- @@ -53,7 +53,7 @@ The following tables show Visual C++ features that are available in Visual Studi - MSVC 64-bit compiler for x86, x64, ARM, and ARM64 - GCC cross-compiler for ARM - Clang/LLVM - - On Windows, Clang/LLVM 7.0, targeting x86 or x64 (CMake support only). Other Clang versions might work but are not officially supported. + - On Windows, Clang/LLVM 12.0, targeting x86 or x64 (CMake support only). - On Linux, any Clang/LLVM installation supported by the distro. ::: moniker-end @@ -106,7 +106,9 @@ Optional Components: - C++ Clang tools for Windows (12.0.0 - x64/x86) - JavaScript diagnostics - IncrediBuild - Build Acceleration +- Windows 11 SDK - Windows 10 SDK (other versions) +- MSVC v142 - VS 2019 C++ x64/x86 build tools (v14.29) - MSVC v141 - VS 2017 C++ x64/x86 build tools (v14.16) - MSVC v140 - VS 2015 C++ build tools (v14.00) @@ -133,6 +135,7 @@ Optional Components: - C++ Clang tools for Windows - JavaScript diagnostics - IncrediBuild - Build Acceleration +- Windows 11 SDK - Windows 10 SDK (other versions) - MSVC v141 - VS 2017 C++ x64/x86 build tools (v14.16) - MSVC v140 - VS 2015 C++ build tools (v14.00) @@ -174,9 +177,12 @@ Optional Components: - IntelliTrace (Enterprise only) - USB Device Connectivity - C++ (v143) Universal Windows Platform tools +- C++ (v142) Universal Windows Platform tools - C++ (v141) Universal Windows Platform tools - Graphics debugger and GPU profiler for DirectX +- Windows 11 SDK - Windows 10 SDK (other versions) +- Architecture and analysis tools ::: moniker-end @@ -188,6 +194,7 @@ Optional Components: - C++ (v142) Universal Windows Platform tools - C++ (v141) Universal Windows Platform tools - Graphics debugger and GPU profiler for DirectX +- Windows 11 SDK - Windows 10 SDK (other versions) - Architecture and analysis tools @@ -215,6 +222,7 @@ Optional Components: - Windows 10 SDK (latest for this Visual Studio version) - IntelliCode - IntelliTrace (Enterprise only) +- Windows 11 SDK - Windows 10 SDK (other versions) - IncrediBuild - Build Acceleration - Cocos @@ -236,6 +244,7 @@ Optional Components: - Windows 10 SDK (latest for this Visual Studio version) - IntelliCode - IntelliTrace (Enterprise only) +- Windows 11 SDK - Windows 10 SDK (other versions) - IncrediBuild - Build Acceleration - Cocos diff --git a/docs/parallel/amp/walkthrough-debugging-a-cpp-amp-application.md b/docs/parallel/amp/walkthrough-debugging-a-cpp-amp-application.md index ffcecd040c2..ea0a3d6bc94 100644 --- a/docs/parallel/amp/walkthrough-debugging-a-cpp-amp-application.md +++ b/docs/parallel/amp/walkthrough-debugging-a-cpp-amp-application.md @@ -1,7 +1,7 @@ --- description: "Learn more about: Walkthrough: Debugging a C++ AMP application" title: "Walkthrough: Debugging a C++ AMP application" -ms.date: 03/07/2021 +ms.date: 10/27/2021 helpviewer_keywords: ["debugging, C++ Accelerated Massive Parallelism", "C++ AMP, debugging", "C++ Accelerated Massive Parallelism, debugging", "debugging, C++ AMP"] --- # Walkthrough: Debugging a C++ AMP application @@ -36,9 +36,9 @@ Before you start this walkthrough: The instructions for creating a project vary depending on which version of Visual Studio you're using. Make sure you have the correct documentation version selected above the table of contents on this page. -::: moniker range="msvc-160" +::: moniker range=">=msvc-160" -### To create the sample project in Visual Studio 2019 +### To create the sample project in Visual Studio 1. On the menu bar, choose **File** > **New** > **Project** to open the **Create a New Project** dialog box. @@ -46,7 +46,7 @@ The instructions for creating a project vary depending on which version of Visua 1. From the filtered list of project types, choose **Console App** then choose **Next**. In the next page, enter `AMPMapReduce` in the **Name** box to specify a name for the project, and specify the project location if you want a different one. - ![Name the project.](../../build/media/mathclient-project-name-2019.png "Name the project") + ![Screenshot showing the Create a new project dialog with the Console App template selected.](../../build/media/mathclient-project-name-2019.png) 1. Choose the **Create** button to create the client project. @@ -76,7 +76,7 @@ Next: 1. Open AMPMapReduce.cpp and replace its content with the following code. -```cpp + ```cpp // AMPMapReduce.cpp defines the entry point for the program. // The program performs a parallel-sum reduction that computes the sum of an array of integers. @@ -191,7 +191,7 @@ Next: return 0; } -``` + ``` 1. On the menu bar, choose **File** > **Save All**. diff --git a/docs/parallel/amp/walkthrough-matrix-multiplication.md b/docs/parallel/amp/walkthrough-matrix-multiplication.md index 17480f95fbb..b15b747b13f 100644 --- a/docs/parallel/amp/walkthrough-matrix-multiplication.md +++ b/docs/parallel/amp/walkthrough-matrix-multiplication.md @@ -1,7 +1,7 @@ --- description: "Learn more about: Walkthrough: Matrix Multiplication" title: "Walkthrough: Matrix Multiplication" -ms.date: "04/23/2019" +ms.date: 10/27/2021 ms.assetid: 61172e8b-da71-4200-a462-ff3a908ab0cf --- # Walkthrough: Matrix Multiplication @@ -22,9 +22,9 @@ Before you start: Instructions for creating a new project vary depending on which version of Visual Studio you have installed. To see the documentation for your preferred version of Visual Studio, use the **Version** selector control. It's found at the top of the table of contents on this page. -::: moniker range="msvc-160" +::: moniker range=">=msvc-160" -### To create the project in Visual Studio 2019 +### To create the project in Visual Studio 1. On the menu bar, choose **File** > **New** > **Project** to open the **Create a New Project** dialog box. @@ -32,7 +32,7 @@ Instructions for creating a new project vary depending on which version of Visua 1. From the filtered list of project types, choose **Empty Project** then choose **Next**. In the next page, enter *MatrixMultiply* in the **Name** box to specify a name for the project, and specify the project location if desired. - ![New console app.](../../build/media/mathclient-project-name-2019.png "New console app") + ![Screenshot showing the Create a new project dialog with the Console App template selected.](../../build/media/mathclient-project-name-2019.png) 1. Choose the **Create** button to create the client project. diff --git a/docs/parallel/concrt/walkthrough-creating-an-agent-based-application.md b/docs/parallel/concrt/walkthrough-creating-an-agent-based-application.md index 3c96d545f5e..db7339cb137 100644 --- a/docs/parallel/concrt/walkthrough-creating-an-agent-based-application.md +++ b/docs/parallel/concrt/walkthrough-creating-an-agent-based-application.md @@ -1,7 +1,7 @@ --- description: "Learn more about: Walkthrough: Creating an Agent-Based Application" title: "Walkthrough: Creating an Agent-Based Application" -ms.date: "04/25/2019" +ms.date: 10/27/2021 helpviewer_keywords: ["asynchronous agents, creating", "agent class, example"] ms.assetid: 730f42ce-6d58-4753-b948-fd9c9ef2ce6c --- @@ -35,9 +35,9 @@ This walkthrough demonstrates how to perform the following tasks: This section shows how to create a C++ console application that references the header files that the program will use. The initial steps vary depending on which version of Visual Studio you are using. To see the documentation for your preferred version of Visual Studio, use the **Version** selector control. It's found at the top of the table of contents on this page. -::: moniker range="msvc-160" +::: moniker range=">=msvc-160" -### To create a C++ console application in Visual Studio 2019 +### To create a C++ console application in Visual Studio 1. From the main menu, choose **File** > **New** > **Project** to open the **Create a New Project** dialog box. @@ -63,13 +63,17 @@ This section shows how to create a C++ console application that references the h ::: moniker-end -1. In *pch.h* (*stdafx.h* in Visual Studio 2017 and earlier), add the following code: +**Update the header file** + +In the *pch.h* (*stdafx.h* in Visual Studio 2017 and earlier) file, add the following code: [!code-cpp[concrt-basic-agent#1](../../parallel/concrt/codesnippet/cpp/walkthrough-creating-an-agent-based-application_1.h)] - The header file agents.h contains the functionality of the [concurrency::agent](../../parallel/concrt/reference/agent-class.md) class. +The header file *agents.h* contains the functionality of the [concurrency::agent](../../parallel/concrt/reference/agent-class.md) class. + +**Verify the application** -1. Verify that the application was created successfully by building and running it. To build the application, on the **Build** menu, click **Build Solution**. If the application builds successfully, run the application by clicking **Start Debugging** on the **Debug** menu. +Finally, verify the application was created successfully by building and running it. To build the application, on the **Build** menu, click **Build Solution**. If the application builds successfully, run the application by clicking **Start Debugging** on the **Debug** menu. [[Top](#top)] @@ -83,37 +87,37 @@ This section shows how to create the `file_reader` class. The runtime schedules 1. In file_reader.h, add the following code. -[!code-cpp[concrt-basic-agent#17](../../parallel/concrt/codesnippet/cpp/walkthrough-creating-an-agent-based-application_2.h)] + [!code-cpp[concrt-basic-agent#17](../../parallel/concrt/codesnippet/cpp/walkthrough-creating-an-agent-based-application_2.h)] 1. In file_reader.h, create a class that is named `file_reader` that derives from `agent`. -[!code-cpp[concrt-basic-agent#2](../../parallel/concrt/codesnippet/cpp/walkthrough-creating-an-agent-based-application_3.h)] + [!code-cpp[concrt-basic-agent#2](../../parallel/concrt/codesnippet/cpp/walkthrough-creating-an-agent-based-application_3.h)] 1. Add the following data members to the **`private`** section of your class. -[!code-cpp[concrt-basic-agent#3](../../parallel/concrt/codesnippet/cpp/walkthrough-creating-an-agent-based-application_4.h)] + [!code-cpp[concrt-basic-agent#3](../../parallel/concrt/codesnippet/cpp/walkthrough-creating-an-agent-based-application_4.h)] - The `_file_name` member is the file name that the agent reads from. The `_target` member is a [concurrency::ITarget](../../parallel/concrt/reference/itarget-class.md) object that the agent writes the contents of the file to. The `_error` member holds any error that occurs during the life of the agent. + The `_file_name` member is the file name that the agent reads from. The `_target` member is a [concurrency::ITarget](../../parallel/concrt/reference/itarget-class.md) object that the agent writes the contents of the file to. The `_error` member holds any error that occurs during the life of the agent. 1. Add the following code for the `file_reader` constructors to the **`public`** section of the `file_reader` class. -[!code-cpp[concrt-basic-agent#4](../../parallel/concrt/codesnippet/cpp/walkthrough-creating-an-agent-based-application_5.h)] + [!code-cpp[concrt-basic-agent#4](../../parallel/concrt/codesnippet/cpp/walkthrough-creating-an-agent-based-application_5.h)] - Each constructor overload sets the `file_reader` data members. The second and third constructor overload enables your application to use a specific scheduler with your agent. The first overload uses the default scheduler with your agent. + Each constructor overload sets the `file_reader` data members. The second and third constructor overload enables your application to use a specific scheduler with your agent. The first overload uses the default scheduler with your agent. 1. Add the `get_error` method to the public section of the `file_reader` class. -[!code-cpp[concrt-basic-agent#5](../../parallel/concrt/codesnippet/cpp/walkthrough-creating-an-agent-based-application_6.h)] + [!code-cpp[concrt-basic-agent#5](../../parallel/concrt/codesnippet/cpp/walkthrough-creating-an-agent-based-application_6.h)] - The `get_error` method retrieves any error that occurs during the life of the agent. + The `get_error` method retrieves any error that occurs during the life of the agent. 1. Implement the [concurrency::agent::run](reference/agent-class.md#run) method in the **`protected`** section of your class. -[!code-cpp[concrt-basic-agent#6](../../parallel/concrt/codesnippet/cpp/walkthrough-creating-an-agent-based-application_7.h)] + [!code-cpp[concrt-basic-agent#6](../../parallel/concrt/codesnippet/cpp/walkthrough-creating-an-agent-based-application_7.h)] The `run` method opens the file and reads data from it. The `run` method uses exception handling to capture any errors that occur during file processing. - Each time this method reads data from the file, it calls the [concurrency::asend](reference/concurrency-namespace-functions.md#asend) function to send that data to the target buffer. It sends the empty string to its target buffer to indicate the end of processing. +Each time this method reads data from the file, it calls the [concurrency::asend](reference/concurrency-namespace-functions.md#asend) function to send that data to the target buffer. It sends the empty string to its target buffer to indicate the end of processing. The following example shows the complete contents of file_reader.h. @@ -129,37 +133,37 @@ This section shows how to use the `file_reader` class to read the contents of a 1. In BasicAgent.cpp, add the following `#include` statement. -[!code-cpp[concrt-basic-agent#8](../../parallel/concrt/codesnippet/cpp/walkthrough-creating-an-agent-based-application_9.cpp)] + [!code-cpp[concrt-basic-agent#8](../../parallel/concrt/codesnippet/cpp/walkthrough-creating-an-agent-based-application_9.cpp)] 1. In BasicAgent.cpp, add the following **`using`** directives. -[!code-cpp[concrt-basic-agent#9](../../parallel/concrt/codesnippet/cpp/walkthrough-creating-an-agent-based-application_10.cpp)] + [!code-cpp[concrt-basic-agent#9](../../parallel/concrt/codesnippet/cpp/walkthrough-creating-an-agent-based-application_10.cpp)] 1. In the `_tmain` function, create a [concurrency::event](../../parallel/concrt/reference/event-class.md) object that signals the end of processing. -[!code-cpp[concrt-basic-agent#10](../../parallel/concrt/codesnippet/cpp/walkthrough-creating-an-agent-based-application_11.cpp)] + [!code-cpp[concrt-basic-agent#10](../../parallel/concrt/codesnippet/cpp/walkthrough-creating-an-agent-based-application_11.cpp)] 1. Create a `call` object that updates the checksum when it receives data. -[!code-cpp[concrt-basic-agent#11](../../parallel/concrt/codesnippet/cpp/walkthrough-creating-an-agent-based-application_12.cpp)] + [!code-cpp[concrt-basic-agent#11](../../parallel/concrt/codesnippet/cpp/walkthrough-creating-an-agent-based-application_12.cpp)] - This `call` object also sets the `event` object when it receives the empty string to signal the end of processing. + This `call` object also sets the `event` object when it receives the empty string to signal the end of processing. 1. Create a `file_reader` object that reads from the file test.txt and writes the contents of that file to the `call` object. -[!code-cpp[concrt-basic-agent#12](../../parallel/concrt/codesnippet/cpp/walkthrough-creating-an-agent-based-application_13.cpp)] + [!code-cpp[concrt-basic-agent#12](../../parallel/concrt/codesnippet/cpp/walkthrough-creating-an-agent-based-application_13.cpp)] 1. Start the agent and wait for it to finish. -[!code-cpp[concrt-basic-agent#13](../../parallel/concrt/codesnippet/cpp/walkthrough-creating-an-agent-based-application_14.cpp)] + [!code-cpp[concrt-basic-agent#13](../../parallel/concrt/codesnippet/cpp/walkthrough-creating-an-agent-based-application_14.cpp)] 1. Wait for the `call` object to receive all data and finish. -[!code-cpp[concrt-basic-agent#14](../../parallel/concrt/codesnippet/cpp/walkthrough-creating-an-agent-based-application_15.cpp)] + [!code-cpp[concrt-basic-agent#14](../../parallel/concrt/codesnippet/cpp/walkthrough-creating-an-agent-based-application_15.cpp)] 1. Check the file reader for errors. If no error occurred, calculate the final Adler-32 sum and print the sum to the console. -[!code-cpp[concrt-basic-agent#15](../../parallel/concrt/codesnippet/cpp/walkthrough-creating-an-agent-based-application_16.cpp)] + [!code-cpp[concrt-basic-agent#15](../../parallel/concrt/codesnippet/cpp/walkthrough-creating-an-agent-based-application_16.cpp)] The following example shows the complete BasicAgent.cpp file. diff --git a/docs/windows/walkthrough-creating-a-standard-cpp-program-cpp.md b/docs/windows/walkthrough-creating-a-standard-cpp-program-cpp.md index 08be251823d..658af87c024 100644 --- a/docs/windows/walkthrough-creating-a-standard-cpp-program-cpp.md +++ b/docs/windows/walkthrough-creating-a-standard-cpp-program-cpp.md @@ -2,7 +2,7 @@ description: "Learn more about: Walkthrough: Creating a Standard C++ Program (C++)" title: "Walkthrough: Creating a Standard C++ Program (C++)" ms.custom: "get-started-article" -ms.date: "04/25/2019" +ms.date: 10/27/2021 helpviewer_keywords: ["command-line applications [C++], standard", "standard applications [C++]"] ms.assetid: 48217e35-d892-46b7-93e3-f6f0b7e2da35 --- @@ -23,9 +23,9 @@ To complete this walkthrough, you must understand the fundamentals of the C++ la The following steps vary depending on which version of Visual Studio you are using. To see the documentation for your preferred version of Visual Studio, use the **Version** selector control. It's found at the top of the table of contents on this page. -::: moniker range="msvc-160" +::: moniker range=">=msvc-160" -### To create a C++ project in Visual Studio 2019 +### To create a C++ project in Visual Studio 1. From the main menu, choose **File** > **New** > **Project** to open the **Create a New Project** dialog box. diff --git a/docs/windows/walkthrough-creating-windows-desktop-applications-cpp.md b/docs/windows/walkthrough-creating-windows-desktop-applications-cpp.md index 702fba7c5d1..b7e0dc7ca29 100644 --- a/docs/windows/walkthrough-creating-windows-desktop-applications-cpp.md +++ b/docs/windows/walkthrough-creating-windows-desktop-applications-cpp.md @@ -2,7 +2,7 @@ title: "Walkthrough: Create a traditional Windows Desktop application (C++)" description: "How to create a minimal, traditional Windows Desktop application using Visual Studio, C++, and the Win32 API" ms.custom: "get-started-article" -ms.date: "05/28/2020" +ms.date: 10/27/2021 helpviewer_keywords: ["Windows applications [C++], Win32", "Windows Desktop applications [C++]", "Windows API [C++]"] --- # Walkthrough: Create a traditional Windows Desktop application (C++) @@ -30,9 +30,9 @@ The Windows API (also known as the Win32 API, Windows Desktop API, and Windows C Follow these steps to create your first Windows desktop project. As you go, you'll enter the code for a working Windows desktop application. To see the documentation for your preferred version of Visual Studio, use the **Version** selector control. It's found at the top of the table of contents on this page. -::: moniker range="msvc-160" +::: moniker range=">=msvc-160" -### To create a Windows desktop project in Visual Studio 2019 +### To create a Windows desktop project in Visual Studio 1. From the main menu, choose **File** > **New** > **Project** to open the **Create a New Project** dialog box. @@ -46,11 +46,11 @@ Follow these steps to create your first Windows desktop project. As you go, you' 1. In **Solution Explorer**, right-click the **DesktopApp** project, choose **Add**, and then choose **New Item**. - ![Short video showing the user adding a new item to DesktopApp Project in Visual Studio 2019.](../build/media/desktop-app-project-add-new-item-153.gif "Add new item to DesktopApp Project") + ![Short video showing the user adding a new item to DesktopApp Project in Visual Studio 2019.](../build/media/desktop-app-project-add-new-item-153.gif) 1. In the **Add New Item** dialog box, select **C++ File (.cpp)**. In the **Name** box, type a name for the file, for example, *HelloWindowsDesktop.cpp*. Choose **Add**. - ![Screenshot of the Add New Item dialog box in Visual Studio 2019 with Installed > Visual C plus plus selected and the C plus plus File option highlighted.](../build/media/desktop-app-add-cpp-file-153.png "Add .cpp file to DesktopApp Project") + ![Screenshot of the Add New Item dialog box in Visual Studio 2019 with Installed > Visual C plus plus selected and the C plus plus File option highlighted.](../build/media/desktop-app-add-cpp-file-153.png) Your project is now created and your source file is opened in the editor. To continue, skip ahead to [Create the code](#create-the-code).