4/20/2022 AM Publish (MicrosoftDocs#4236)

* Update open-wopen.md

Clarify that _O_TEMPORARY sets FILE_SHARE_DELETE.

* Update other pages that mention _O_TEMPORARY effects.

* New article - IDL method wizard

* update after review

* update after review

* Update after review

* Update after review

* Updating - Add property wizard for VS2022

* Updating broken links

* Update after review

* New article - Add an IDL Property

* link updation

* Update after review

* update after review

* update after review

* New article - IDL MFC property wizard

* Broken link fixed

* Broken link fixed

* Update virtual-functions.md

* update for links

* Updating links

* Address cpp-docs 3780 3782 3790 3791 3805

* Attempt correction of table format

* Add documentation for compiler error C2956 and update error text (MicrosoftDocs#4176)

* Add documentation for compiler error C2956 and update error text

* Add TOC entry

* Update for grammar and my own comprehension.

Sometimes, you just get carried away. This version could use some simplification.

* Simplify.

Address remarks, attempt simplification.
Acrolinx all the things.

* More updates per review

Co-authored-by: Colin Robertson <corob@microsoft.com>

* Address cpp-docs 3816

* Address non-blocking issues from 4207

* fix for sample program.

* edits

* edit pass. Move to ide location

* minor edit

* fix link

* Final update

* final update

* final update

* resolving blocking issue

* resolving blocking issue

* ToC update for new article

* ToC update

* link update

* Correct inconsistent formatting for the `_O_EXCL` constant in the docs for the open functions

* Update c28195.md

* Update in alt-text

* Update in alt-text

* Final Update- See also section

* edit pass

* edit pass

* more cleanup

* typo

* small edit

* Final update

* edit pass

* edit pass

* formatting for scannability

* acrolinx

* one more try at spacing

* final update

* VMCS -> VMXON

According to the intel IA32 development manual (Volume 3 C3 23.7):

"Before executing VMXON, software should allocate a naturally aligned 4-KByte region of memory that a logical
processor may use to support VMX operation. This region is called the VMXON region."

* edit and add links

* fix links

* add code example

* click->tick

* Update date, link to Intel docs

* Another go at updating the description

* Fix stray double-quote

* Address issue in DD PR 1393452

* add /interface and /internal-partition - draft (MicrosoftDocs#4227)

* add /interface and /internal-partition - draft

* add example

* fix formatting

* update text regarding example

* tech review

* link updates

* fix switch name and link

* edits

* reorder version info

* cleanup

* add /tp flag

* fix command line

Co-authored-by: TylerMSFT <Tyler.Whitney@microsoft.com>

* Update os-ot-favor-small-code-favor-fast-code.md

Change "minimize or maximize size" to "minimize size or maximize speed"

* Expand into a whole SEO-friendly sentence

* Clarify when _matherr will be invoked (#4230)

Customer here https://developercommunity.visualstudio.com/t/_matherr-example-does-not-work-for-me/1676341#T-ND10016474 expressed confusion over when _matherr is called. This change points out that the only setting that will enable/disable this is the presence of _matherr, but it will not be triggered when using intrinsics.

* acrolinx and other fixes

* fix typo

* more code escape

* another code escape

* better formatting for retval possibilities

* fix backslashes

* incorp feedback

* SEO work (MicrosoftDocs#4234)

* SEO work

* acrolinx

Co-authored-by: TylerMSFT <Tyler.Whitney@microsoft.com>

Co-authored-by: Steve Wishnousky <stwish@microsoft.com>
Co-authored-by: rachana-satao <83084319+rachana-satao@users.noreply.github.com>
Co-authored-by: opbld15 <opbld15@microsoft.com>
Co-authored-by: Colin Robertson <corob@microsoft.com>
Co-authored-by: opbld16 <opbld16@microsoft.com>
Co-authored-by: opbld17 <opbld17@microsoft.com>
Co-authored-by: atikmapari <31974726+atikmapari@users.noreply.github.com>
Co-authored-by: PRMerger19 <prmrgr19@microsoft.com>
Co-authored-by: Ming Ho <94572161+homing1@users.noreply.github.com>
Co-authored-by: PRMerger5 <prmergr5@microsoft.com>
Co-authored-by: Regan Downer <97987445+v-regandowner@users.noreply.github.com>
Co-authored-by: Jonathan Emmett <joemmett@microsoft.com>
Co-authored-by: Tamara K <93546702+tamarakhader@users.noreply.github.com>
Co-authored-by: TylerMSFT <Tyler.Whitney@microsoft.com>
Co-authored-by: PRMerger17 <prmrgr17@microsoft.com>
Co-authored-by: Paula Miller <v-paulmi@microsoft.com>
Co-authored-by: Martin Storsjö <martin@martin.st>
Co-authored-by: Sunny Chatterjee <sunnych@microsoft.com>
Co-authored-by: Tyler Whitney <TylerMSFT@users.noreply.github.com>
Co-authored-by: Colin Cooper <72402153+v-ccolin@users.noreply.github.com>
Co-authored-by: krispy <monstertyo@gmail.com>
Co-authored-by: PRMerger8 <prmrgr8@microsoft.com>
Co-authored-by: PRMerger10 <prmrgr10@microsoft.com>
Co-authored-by: Tech Stuff <103606018+teknixstuff@users.noreply.github.com>
Co-authored-by: Dennis Rea <v-denrea@microsoft.com>

Author: 26 people

docs/build/creating-and-managing-visual-cpp-projects.md

@@ -1,80 +1,76 @@
 ---
-description: "Learn more about: Visual Studio projects - C++"
+description: "Learn more about: creating and configuring Visual Studio C++ projects"
 title: "Visual Studio Projects - C++"
-ms.date: "10/25/2019"
-helpviewer_keywords: ["ATL projects, creating", "Visual Studio C++ projects, creating", "projects [C++], creating", "Visual Studio C++ projects", "ATL projects"]
-ms.assetid: 11003cd8-9046-4630-a189-a32bf3b88047
+ms.date: 04/19/2022
+helpviewer_keywords: ["Visual Studio C++ projects, creating", "projects [C++], creating", "Visual Studio C++ projects"]
 ---
 # Visual Studio projects - C++
 
-A *Visual Studio project* is a project based on the MSBuild build system. MSBuild is the native build system for Visual Studio and is generally the best build system to use for Windows-specific programs. MSBuild is tightly integrated with Visual Studio, but you can also use it from the command line. For cross-platform projects, or projects that use open-source libraries, we recommend using [CMake projects in Visual Studio](cmake-projects-in-visual-studio.md) in Visual Studio 2017 and later. For information about upgrading MSBuild projects from older versions of Visual Studio, see the [Microsoft C++ Porting and Upgrading Guide](../porting/visual-cpp-porting-and-upgrading-guide.md).
+A *Visual Studio project* is a collection of code files and assets such as icons, images, and so on, that are built together using the MSBuild build system. MSBuild is the native build system for Visual Studio and is generally the best build system to use for Windows-specific programs. MSBuild is tightly integrated with Visual Studio, but you can also use it from the command line.
 
-## Create a project
+For cross-platform projects, or projects that use open-source libraries, we recommend using [CMake projects in Visual Studio](cmake-projects-in-visual-studio.md) in Visual Studio 2017 and later. For information about upgrading MSBuild projects from older versions of Visual Studio, see the [Microsoft C++ Porting and Upgrading Guide](../porting/visual-cpp-porting-and-upgrading-guide.md).
+
+## Create a Visual Studio C++ project
 
 ::: 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.
+1. Create a C++ project by choosing **File** > **New** > **Project**.
+1. Set the **Language** to C++.
+1. In the results list, you'll see a list of project templates. Filter the templates them by setting the **Platform** or **Project Type** and then by typing keywords into the search box.
 
-   ![Screenshot of the Create a new project wizard in Visual Studio.](../build/media/vs2019-choose-console-app.png "Visual Studio 2019 New Project Dialog")
+   ![Screenshot of the Create a new project wizard. The Console App project template is selected.](../build/media/vs2019-choose-console-app.png)
 
 ::: moniker-end
 
 ::: moniker range="msvc-150"
 
-You can create C++ projects by choosing **File** > **New** > **Project**, then choosing Visual C++ in the left pane. In the center pane you see a list of project templates:
+1. Create a C++ project by choosing **File** > **New** > **Project**.
+1. Choose **Visual C++** in the left pane. In the center pane, a list of project templates will appear:
 
-   ![Screenshot of the New Project dialog, showing available project templates.](../overview/media/vs2017-new-project.png "Visual Studio 2017 New Project Dialog")
+   ![Screenshot of the New Project dialog, showing available project templates for C++ such as Windows Console Application.](../overview/media/vs2017-new-project.png "Visual Studio 2017 New Project Dialog")
 
 ::: moniker-end
 
-For more information about all the default project templates that are included in Visual Studio, see [C++ project templates in Visual Studio](reference/visual-cpp-project-types.md). You can create your own project templates. For more information, see [How to: Create project templates](/visualstudio/ide/how-to-create-project-templates).
+For more information about the default project templates included in Visual Studio, see [C++ project templates in Visual Studio](reference/visual-cpp-project-types.md).
+
+You can create your own project templates. For more information, see [How to: Create project templates](/visualstudio/ide/how-to-create-project-templates).
 
 After you create a project, it appears in the [Solution Explorer](/visualstudio/ide/solutions-and-projects-in-visual-studio) window:
 
-   ![Screenshot of the Solution Explorer window.](media/mathlibrary-solution-explorer-153.png)
+   ![Screenshot of the Solution Explorer window, showing source files, header files, and resource files.](media/mathlibrary-solution-explorer-153.png)
+
+When you create a new project, a solution file (.sln) is also created. A *Visual Studio solution* is a collection of one or more projects. You can add another project to the solution by right-clicking the solution name in **Solution Explorer** > **Add** > **New project**.
 
-When you create a new project, a solution file (.sln) is also created. You can add additional projects to the solution by right-clicking on it in **Solution Explorer**. The solution file is used to coordinate build dependencies when you have multiple related projects but doesn't do much more than that. All the compiler options are set at the project level.
+The solution file coordinates build dependencies when you have multiple related projects. Compiler options are set at the project level.
 
-## Add items
+## Add code, icons, and other assets to a project
 
 Add source code files, icons, or any other items to your project by right-clicking on the project in **Solution Explorer** and choosing **Add > New** or **Add > Existing**.
 
-## Add third party libraries
+## Add third party libraries to a project
 
 To add third-party libraries, use the [vcpkg](https://vcpkg.io/) package manager. Run the Visual Studio integration step to set up the paths to that library when you reference it from any Visual Studio project.
 
-## Set compiler options and other build properties
+## Set compiler options and build properties
 
 To configure build settings for a project, right-click on the project in **Solution Explorer** and choose **Properties**. For more information, see [Set C++ compiler and build properties in Visual Studio](working-with-project-properties.md).
 
-## Compile and run
+## Compile and run a project
 
 To compile and run the new project, press **F5** or click the *debug dropdown* with the green arrow on the main toolbar. The *configuration dropdown* is where you choose whether to perform a *Debug* or *Release* build (or some other custom configuration).
 
-A new project compiles without errors. When adding your own code, you may occasionally introduce an error or trigger a warning. An error prevents the build from completing; a warning does not. All errors and warnings will appear both in the Output Window and in the Error List when you build the project.
+A new project compiles without errors. When adding your own code, you may occasionally introduce an error or trigger a warning. An error prevents the build from completing; a warning doesn't. All errors and warnings will appear both in the Output Window and in the Error List when you build the project.
 
    ![Screenshot of the Output window and Error list.](../overview/media/vs2017-output-error-list.png)
 
-In the Error List, you can press **F1** on a highlighted error to go to its documentation topic.
-
-## In This Section
-
-[Set C++ compiler and build properties in Visual Studio](working-with-project-properties.md)<br/>
-How to use Property Pages and Property Sheets to specify your project settings.
-
-[Reference libraries and components at build time](adding-references-in-visual-cpp-projects.md)<br/>
-How to include libs, DLLs, COM and .NET components in a project.
-
-[Organize Project Output Files](how-to-organize-project-output-files-for-builds.md)<br/>
-How to customize the location of the executable files created in the build process.
-
-[Custom Build Steps and Build Events](understanding-custom-build-steps-and-build-events.md)<br/>
-How to add any arbitrary command to the build process at specified points.
-
-[Create a project from existing code](how-to-create-a-cpp-project-from-existing-code.md)<br/>
-How to create a new Visual Studio project from a loose collection of source files.
+In the **Error List**, you can press **F1** on the highlighted error to go to its documentation topic.
 
 ## See also
 
-[Projects and build systems](projects-and-build-systems-cpp.md)<br>
-[Microsoft C++ Porting and Upgrading Guide](../porting/visual-cpp-porting-and-upgrading-guide.md)
+[Create a project from existing code](how-to-create-a-cpp-project-from-existing-code.md)\
+[Set C++ compiler and build properties in Visual Studio](working-with-project-properties.md)\
+[Custom build steps and build events](understanding-custom-build-steps-and-build-events.md)\
+[Reference libraries and components at build time](adding-references-in-visual-cpp-projects.md)\
+[Organize project output files](how-to-organize-project-output-files-for-builds.md)\
+[Projects and build systems](projects-and-build-systems-cpp.md)\
+[Microsoft C++ porting and upgrade guide](../porting/visual-cpp-porting-and-upgrading-guide.md)