moved some compiler topics to reference

Author: mikeblome

docs/TOC.md

@@ -1,5 +1,6 @@
 # [Visual C++ in Visual Studio 2017](visual-cpp-in-visual-studio.md)
 # [What's New for Visual C++ in Visual Studio 2017](what-s-new-for-visual-cpp-in-visual-studio.md)
+# [Overview of C++ development in Visual Studio](ide-and-tools-for-visual-cpp-development.md)
 # Visual C++ Tutorial
 ## [Install C++ support in Visual Studio](build/vscpp-step-0-installation.md)
 ## [Create a C++ console app project](build/vscpp-step-1-create.md)
@@ -19,9 +20,9 @@
 # [Data Access](data/data-access-in-cpp.md)
 # [Text and Strings](text/text-and-strings-in-visual-cpp.md)
 # [vcpkg: A Package Manager for C++](vcpkg.md)
-# [IDE and Tools for Visual C++](ide/ide-and-tools-for-visual-cpp-development.md)
-# [Compilers and Build Tools](build/building-c-cpp-programs.md)
-# [Porting and Upgrading Visual C++ Code](porting/visual-cpp-porting-and-upgrading-guide.md)
+
+# [Configure and compile C++ projects](build/building-c-cpp-programs.md)
+# [Port and Upgrade C++ Code](porting/visual-cpp-porting-and-upgrading-guide.md)
 # [Security Best Practices for C++](security/security-best-practices-for-cpp.md)
 ## [Running as a Member of the Users Group](security/running-as-a-member-of-the-users-group.md)
 ## [How User Account Control (UAC) Affects Your Application](security/how-user-account-control-uac-affects-your-application.md)

docs/atl/reference/default-atl-project-configurations.md

@@ -18,7 +18,7 @@ The ATL Project Wizard creates two project configurations by default:
 ## See Also
 
 [Programming with ATL and C Run-Time Code](../../atl/programming-with-atl-and-c-run-time-code.md)<br/>
-[Working with Project Properties](../../build/working-with-project-properties.md)<br/>
+[Set compiler and build properties](../../build/working-with-project-properties.md)<br/>
 [Configuration Manager Dialog Box](/visualstudio/ide/understanding-build-configurations)<br/>
 [Compiling and Building](/visualstudio/ide/compiling-and-building-in-visual-studio)
 

docs/build/TOC.md

@@ -1,7 +1,7 @@
 # [Building C/C++ Projects](building-c-cpp-programs.md)
 # [Visual Studio Projects - C++](creating-and-managing-visual-cpp-projects.md)
 ## [Set compiler and build properties](working-with-project-properties.md)
-### [Share or resuse Visual Studio project settings](create-reusable-property-configurations.md)
+### [Share or reuse Visual Studio project settings](create-reusable-property-configurations.md)
 ### [Project property inheritance](project-property-inheritance.md)
 ### [Modify properties and targets without changing the project file](modify-project-properties-without-changing-project-file.md)
 ## [Reference libraries and components at build time](adding-references-in-visual-cpp-projects.md)
@@ -47,14 +47,6 @@
 ## [Walkthrough: Compiling a C++/CLI Program on the Command Line](walkthrough-compiling-a-cpp-cli-program-on-the-command-line.md)
 ## [Walkthrough: Compiling a C++/CX Program on the Command Line](walkthrough-compiling-a-cpp-cx-program-on-the-command-line.md)
 ## [Set the Path and Environment Variables for Command-Line Builds](setting-the-path-and-environment-variables-for-command-line-builds.md)
-## [Compiler Command-Line Syntax](compiler-command-line-syntax.md)
-### [CL Filename Syntax](cl-filename-syntax.md)
-### [Order of CL Options](order-of-cl-options.md)
-### [Return Value of cl.exe](return-value-of-cl-exe.md)
-## [CL Environment Variables](cl-environment-variables.md)
-## [CL Command Files](cl-command-files.md)
-## [Fast Compilation](fast-compilation.md)
-## [CL Invokes the Linker](cl-invokes-the-linker.md)
 # [Use MSBuild from the command line](msbuild-visual-cpp.md)
 ## [Walkthrough: Using MSBuild to Create a C++ Project](walkthrough-using-msbuild-to-create-a-visual-cpp-project.md)
 ## [How to: Use Build Events in MSBuild Projects](how-to-use-build-events-in-msbuild-projects.md)

docs/build/adding-references-in-visual-cpp-projects.md

@@ -158,4 +158,4 @@ The following properties are found on COM and .NET assembly references, and cann
 ## See Also
 
 [Property Pages](reference/property-pages-visual-cpp.md)<br>
-[Working with Project Properties](working-with-project-properties.md)
+[Set compiler and build properties](working-with-project-properties.md)

docs/build/building-on-the-command-line.md

@@ -22,7 +22,7 @@ To work correctly, the tools require several specific environment variables to b
 
 The required environment variables are specific to your installation and to the build architecture you choose, and might be changed by product updates or upgrades. Therefore, we strongly recommend that you use one of the installed command prompt shortcuts or command files instead of setting the environment variables in Windows yourself. For more information, see [Set the Path and Environment Variables for Command-Line Builds](setting-the-path-and-environment-variables-for-command-line-builds.md).
 
-## Developer command prompt shortcuts
+## <a name="developer_command_prompt_shortcuts"></a> Developer command prompt shortcuts
 
 The command prompt shortcuts are installed in a version-specific Visual Studio folder in your Start menu. Here's a list of the base command prompt shortcuts and the build architectures they support:
 
@@ -36,16 +36,15 @@ The actual Start menu folder and shortcut names vary depending on the version of
 
 If you've installed the [Build Tools for Visual Studio 2017](https://go.microsoft.com/fwlink/p/?linkid=875721) (which also includes the Visual Studio 2015 Update 3 compiler toolset), only the architecture-specific native or cross tools developer command prompt options are installed, and not the general **Developer Command Prompt** shortcut.
 
-<a name="developer_command_prompt"></a>
-### To open a developer command prompt window
+## <a name="developer_command_prompt"></a> To open a developer command prompt window
 
 1. On the desktop, open the Windows **Start** menu, and then scroll to find and open the folder for your version of Visual Studio, for example, **Visual Studio 2017**. In some older versions of Visual Studio, the shortcuts are in a subfolder called **Visual Studio Tools**.
 
 1. In the folder, choose the **Developer Command Prompt** for your version of Visual Studio. This shortcut starts a developer command prompt window that uses the default build architecture of 32-bit, x86-native tools to build 32-bit, x86-native code. If you prefer a non-default build architecture, choose one of the native or cross tools command prompts to specify the host and target architecture.
 
 An even faster way to open a developer command prompt window is to enter *developer command prompt* in the desktop search box, then choose the desired result.
 
-## Developer command file locations
+## <a name="developer_command_prompt_file_locations"></a>Developer command file locations
 
 If you prefer to set the build architecture environment in an existing command prompt window, you can use one of the command files (batch files) created by the installer to set the required environment. We only recommend you do this in a new command prompt window, and we do not recommend you later switch environments in the same command window. The location of these files depends on the version of Visual Studio you have installed, and on location and naming choices you made during installation. For Visual Studio 2017, the typical installation location on a 64-bit computer is in \Program Files (x86)\Microsoft Visual Studio\2017\\*edition*, where *edition* may be Community, Professional, Enterprise, BuildTools, or another name you supplied. For Visual Studio 2015, the typical installation location is in \Program Files (x86)\Microsoft Visual Studio 14.0.
 
@@ -160,19 +159,19 @@ Describes how to start a command prompt window that has the required environment
 
 [Compiler Command-Line Syntax](compiler-command-line-syntax.md)<br/>
 
-[CL Filename Syntax](cl-filename-syntax.md)<br/>
+[CL Filename Syntax](reference/cl-filename-syntax.md)<br/>
 
-[Order of CL Options](order-of-cl-options.md)<br/>
+[Order of CL Options](reference/order-of-cl-options.md)<br/>
 
-[Return Value of cl.exe](return-value-of-cl-exe.md)<br/>
+[Return Value of cl.exe](reference/return-value-of-cl-exe.md)<br/>
 
-[CL Environment Variables](cl-environment-variables.md)<br/>
+[CL Environment Variables](reference/cl-environment-variables.md)<br/>
 
-[CL Command Files](cl-command-files.md)<br/>
+[CL Command Files](reference/cl-command-files.md)<br/>
 
-[Fast Compilation](fast-compilation.md)<br/>
+[Fast Compilation](reference/fast-compilation.md)<br/>
 
-[CL Invokes the Linker](cl-invokes-the-linker.md)<br/>
+[CL Invokes the Linker](reference/cl-invokes-the-linker.md)<br/>
 
 ## Related Sections
 

docs/build/fast-compilation.md

@@ -12,7 +12,7 @@ You can use the project configurations in the Visual Studio IDE to set up C++ ap
 
 1. Open the C++ project that you want to configure.
 
-1. Open the property pages for that project. For more information, see [Working with Project Properties](working-with-project-properties.md).
+1. Open the property pages for that project. For more information, see [Set compiler and build properties](working-with-project-properties.md).
 
    > [!NOTE]
    > For .NET projects, make sure that the **Configuration Properties** node, or one of its child nodes, is selected in the **\<Projectname> Property Pages** dialog box; otherwise, the **Configuration Manager** button remains unavailable.

docs/build/how-to-configure-visual-cpp-projects-to-target-64-bit-platforms.md

@@ -10,7 +10,7 @@ You can debug a release build of an application.
 
 ### To debug a release build
 
-1. Open the **Property Pages** dialog box for the project. For details, see [Working with Project Properties](working-with-project-properties.md).
+1. Open the **Property Pages** dialog box for the project. For details, see [Set compiler and build properties](working-with-project-properties.md).
 
 1. Click the **C/C++** node. Set **Debug Information Format** to [C7 compatible (/Z7)](reference/z7-zi-zi-debug-information-format.md) or **Program Database (/Zi)**.
 

docs/build/how-to-debug-a-release-build.md

@@ -17,11 +17,11 @@ When you install a C++ workload in the Visual Studio installer, it always instal
 
 ## Use a 64-bit hosted developer command prompt shortcut
 
-When Visual Studio is installed on a 64-bit Windows operating system, additional developer command prompt shortcuts for the 64-bit, x64-hosted native and cross compilers are available. To access these command prompts on Windows 10, on the **Start** menu, open the folder for your version of Visual Studio, for example **Visual Studio 2017**, and then choose one of the x64 native or cross-tool developer command prompts. To access these command prompts on Windows 8, on the **Start** screen, open **All apps**. Under the heading for the installed version of Visual Studio, open the **Visual Studio** folder (in older versions of Visual Studio, it may be named **Visual Studio Tools**). On earlier versions of Windows, choose **Start**, expand **All Programs**, the folder for your version of **Visual Studio** (and on older versions of Visual Studio, **Visual Studio Tools**). For more information, see [Developer command prompt shortcuts](building-on-the-command-line.md#developer-command-prompt-shortcuts).
+When Visual Studio is installed on a 64-bit Windows operating system, additional developer command prompt shortcuts for the 64-bit, x64-hosted native and cross compilers are available. To access these command prompts on Windows 10, on the **Start** menu, open the folder for your version of Visual Studio, for example **Visual Studio 2017**, and then choose one of the x64 native or cross-tool developer command prompts. To access these command prompts on Windows 8, on the **Start** screen, open **All apps**. Under the heading for the installed version of Visual Studio, open the **Visual Studio** folder (in older versions of Visual Studio, it may be named **Visual Studio Tools**). On earlier versions of Windows, choose **Start**, expand **All Programs**, the folder for your version of **Visual Studio** (and on older versions of Visual Studio, **Visual Studio Tools**). For more information, see [Developer command prompt shortcuts](building-on-the-command-line.md#developer_command_prompt_shortcuts).
 
 ## Use Vcvarsall.bat to set a 64-bit hosted build architecture
 
-Any of the native or cross compiler tools build configurations can be used on the command line by running the vcvarsall.bat command file. This command file configures the path and environment variables that enable a particular build architecture in an existing command prompt window. For specific instructions, see [Developer command files and locations](building-on-the-command-line.md#developer-command-files-and-locations).
+Any of the native or cross compiler tools build configurations can be used on the command line by running the vcvarsall.bat command file. This command file configures the path and environment variables that enable a particular build architecture in an existing command prompt window. For specific instructions, see [Developer command files and locations](building-on-the-command-line.md#developer_command_files_and_locations).
 
 ## See also
 

docs/build/how-to-enable-a-64-bit-visual-cpp-toolset-on-the-command-line.md

@@ -11,9 +11,9 @@
 ### [Files Created for CLR Projects](files-created-for-clr-projects.md)
 ### [ATL Program or Control Source and Header Files](atl-program-or-control-source-and-header-files.md)
 ### [MFC Program or Control Source and Header Files](mfc-program-or-control-source-and-header-files.md)
-### [Help Files](help-files-html-help.md)
-### [Help Files](help-files-winhelp.md)
-### [Hint Files](hint-files.md)
+### [HTML Help Files](help-files-html-help.md)
+### [Winhelp Help Files](help-files-winhelp.md)
+### [Hint Files for Intellisense](hint-files.md)
 ### [Property Page XML Files](property-page-xml-files.md)
 ### [.vcxproj and .props file structure](vcxproj-file-structure.md)
 ### [Example project file](project-files.md)
@@ -44,6 +44,13 @@
 #### [HLSL Property Pages: Advanced](hlsl-property-pages-advanced.md)
 #### [HLSL Property Pages: Output Files](hlsl-property-pages-output-files.md)
 # [Compiling a C/C++ Program](compiling-a-c-cpp-program.md)
+## [Compiler Command-Line Syntax](compiler-command-line-syntax.md)
+### [CL Filename Syntax](cl-filename-syntax.md)
+### [Order of CL Options](order-of-cl-options.md)
+### [Return Value of cl.exe](return-value-of-cl-exe.md)
+## [CL Environment Variables](cl-environment-variables.md)
+## [CL Command Files](cl-command-files.md)
+## [CL Invokes the Linker](cl-invokes-the-linker.md)
 ## [Compiler Options](compiler-options.md)
 ### [Compiler Options Listed by Category](compiler-options-listed-by-category.md)
 ### [Compiler Options Listed Alphabetically](compiler-options-listed-alphabetically.md)

docs/build/reference/TOC.md

@@ -25,4 +25,4 @@ To access this property page dialog box, open the property pages for your projec
 [\<file> Element](/visualstudio/deployment/file-element-clickonce-application)<br>
 [ClickOnce Application Manifest](/visualstudio/deployment/clickonce-application-manifest)<br>
 [Manifest Tool Property Pages](manifest-tool-property-pages.md)<br>
-[Working with Project Properties](../working-with-project-properties.md)
+[Set compiler and build properties](../working-with-project-properties.md)

docs/build/reference/advanced-manifest-tool.md

@@ -24,7 +24,7 @@ Only one directory can be passed to an **/AI** invocation. Specify one **/AI** o
 
 ### To set this compiler option in the Visual Studio development environment
 
-1. Open the project's **Property Pages** dialog box. For details, see [Working with Project Properties](../working-with-project-properties.md).
+1. Open the project's **Property Pages** dialog box. For details, see [Set compiler and build properties](../working-with-project-properties.md).
 
 1. Select the **Configuration Properties** > **C/C++** > **General** property page.
 
@@ -37,5 +37,5 @@ Only one directory can be passed to an **/AI** invocation. Specify one **/AI** o
 ## See Also
 
 [Compiler Options](compiler-options.md)<br/>
-[Compiler Command Line Syntax](../compiler-command-line-syntax.md)<br/>
+[Compiler Command Line Syntax](compiler-command-line-syntax.md)<br/>
 [#using Directive](../../preprocessor/hash-using-directive-cpp.md)

docs/build/reference/ai-specify-metadata-directories.md

@@ -19,7 +19,7 @@ You can edit an existing DLL for /ALLOWBIND functionality with the [/ALLOWBIND](
 
 ### To set this linker option in the Visual Studio development environment
 
-1. Open the project's **Property Pages** dialog box. For details, see [Working with Project Properties](../working-with-project-properties.md).
+1. Open the project's **Property Pages** dialog box. For details, see [Set compiler and build properties](../working-with-project-properties.md).
 
 1. Expand **Configuration Properties**, **Linker**, and select **Command Line**.
 

docs/build/reference/allowbind-prevent-dll-binding.md

@@ -29,7 +29,7 @@ For more information, see [Manifest Files Reference](/windows/desktop/SbsCs/mani
 
 ### To set this linker option in the Visual Studio development environment
 
-1. Open the project's **Property Pages** dialog box. For details, see [Working with Project Properties](../working-with-project-properties.md).
+1. Open the project's **Property Pages** dialog box. For details, see [Set compiler and build properties](../working-with-project-properties.md).
 
 1. Select the **Configuration Properties** > **Linker** > **Manifest File** property page.
 

docs/build/reference/allowisolation-manifest-lookup.md

@@ -75,7 +75,7 @@ For more information, see [Code Analysis for C/C++ Overview](/visualstudio/code-
 
 ### To set this compiler option in the Visual Studio development environment
 
-1. Open the project's **Property Pages** dialog box. For details, see [Working with Project Properties](../working-with-project-properties.md).
+1. Open the project's **Property Pages** dialog box. For details, see [Set compiler and build properties](../working-with-project-properties.md).
 
 1. Expand the **Configuration Properties** node.
 
@@ -92,4 +92,4 @@ For more information, see [Code Analysis for C/C++ Overview](/visualstudio/code-
 ## See Also
 
 - [Compiler Options](compiler-options.md)
-- [Compiler Command Line Syntax](../compiler-command-line-syntax.md)
+- [Compiler Command Line Syntax](compiler-command-line-syntax.md)

docs/build/reference/analyze-code-analysis.md

@@ -23,7 +23,7 @@ The /APPCONTAINER option was introduced in Windows 8.
 
 ### To set this linker option in Visual Studio
 
-1. Open the project **Property Pages** dialog box. For more information, see [Working with Project Properties](../working-with-project-properties.md).
+1. Open the project **Property Pages** dialog box. For more information, see [Set compiler and build properties](../working-with-project-properties.md).
 
 1. Expand the **Configuration Properties** node.
 

docs/build/reference/appcontainer-windows-store-app.md

@@ -29,7 +29,7 @@ When you use [/clr](clr-common-language-runtime-compilation.md) to compile, **/a
 
 ### To set the /arch:ARMv7VE or /arch:VFPv4 compiler option in Visual Studio
 
-1. Open the **Property Pages** dialog box for the project. For more information, see [Working with Project Properties](../working-with-project-properties.md).
+1. Open the **Property Pages** dialog box for the project. For more information, see [Set compiler and build properties](../working-with-project-properties.md).
 
 1. Select the **C/C++** folder.
 
@@ -45,4 +45,4 @@ When you use [/clr](clr-common-language-runtime-compilation.md) to compile, **/a
 
 [/arch (Minimum CPU Architecture)](arch-minimum-cpu-architecture.md)<br/>
 [Compiler Options](compiler-options.md)<br/>
-[Compiler Command Line Syntax](../compiler-command-line-syntax.md)
+[Compiler Command Line Syntax](compiler-command-line-syntax.md)