Merge pull request #282 from Microsoft/master

merge to live

Author: ghogen

docs/build/calling-dll-functions-from-visual-basic-applications.md

@@ -78,7 +78,7 @@ EXPORTS
    INITCODE=_InitCode@0  
 ```  
 
- For DLLs to be called by programs written in Visual Basic, the alias technique shown in this topic is needed in the .def file. If the alias is done in the Visual Basic program, use of aliasing in the .def file is not necessary. It can be done in the Visual Basic program by adding an alias clause to the [Declare](/dotnet/articles/visual-basic/language-reference/statements/declare-statement) statement.  
+ For DLLs to be called by programs written in Visual Basic, the alias technique shown in this topic is needed in the .def file. If the alias is done in the Visual Basic program, use of aliasing in the .def file is not necessary. It can be done in the Visual Basic program by adding an alias clause to the [Declare](/dotnet/visual-basic/language-reference/statements/declare-statement) statement.  
 
 ## What do you want to know more about?  
 

docs/build/reference/TOC.md

@@ -145,15 +145,6 @@
 #### [-Zs (Syntax Check Only)](zs-syntax-check-only.md)
 #### [-ZW (Windows Runtime Compilation)](zw-windows-runtime-compilation.md)
 ## [Creating Precompiled Header Files](creating-precompiled-header-files.md)
-### [When to Precompile Source Code](when-to-precompile-source-code.md)
-### [Two Choices for Precompiling Code](two-choices-for-precompiling-code.md)
-### [Precompiled Header Consistency Rules](precompiled-header-consistency-rules.md)
-#### [Consistency Rules for Per-File Use of Precompiled Headers](consistency-rules-for-per-file-use-of-precompiled-headers.md)
-#### [Consistency Rules for -Yc and -Yu](consistency-rules-for-yc-and-yu.md)
-### [Using Precompiled Headers in a Project](using-precompiled-headers-in-a-project.md)
-#### [PCH Files in the Build Process](pch-files-in-the-build-process.md)
-#### [Sample Makefile for PCH](sample-makefile-for-pch.md)
-#### [Example Code for PCH](example-code-for-pch.md)
 ## [Unicode Support in the Compiler and Linker](unicode-support-in-the-compiler-and-linker.md)
 # [Linking](linking.md)
 ## [Setting Linker Options](setting-linker-options.md)

docs/build/reference/assemblylinkresource-link-to-dotnet-framework-resource.md

@@ -55,7 +55,7 @@ translation.priority.ht:
 
  /ASSEMBLYLINKRESOURCE requires that the compilation include [/clr](../../build/reference/clr-common-language-runtime-compilation.md); [/LN](../../build/reference/ln-create-msil-module.md) or [/NOASSEMBLY](../../build/reference/noassembly-create-a-msil-module.md) is not allowed with /ASSEMBLYLINKRESOURCE.  
 
- If *filename* is a .NET Framework resource file created, for example, by [Resgen.exe](http://msdn.microsoft.com/Library/8ef159de-b660-4bec-9213-c3fbc4d1c6f4) or in the development environment, it can be accessed with members in the **System.Resources** namespace. For more information, see [System.Resources.ResourceManager](https://msdn.microsoft.com/en-us/library/system.resources.resourcemanager.aspx). For all other resources, use the **GetManifestResource**\* methods in the **System.Reflection.Assembly** class to access the resource at run time.  
+ If *filename* is a .NET Framework resource file created, for example, by [Resgen.exe](/dotnet/framework/tools/resgen-exe-resource-file-generator) or in the development environment, it can be accessed with members in the **System.Resources** namespace. For more information, see [System.Resources.ResourceManager](https://msdn.microsoft.com/en-us/library/system.resources.resourcemanager.aspx). For all other resources, use the **GetManifestResource**\* methods in the **System.Reflection.Assembly** class to access the resource at run time.  
 
  *filename* can be any file format. For example, you may want to make a native DLL part of the assembly, so it can be installed into the Global Assembly Cache and accessed from managed code in the assembly.  
 

docs/build/reference/assemblyresource-embed-a-managed-resource.md

@@ -58,7 +58,7 @@ translation.priority.ht:
 
  Resources are public in the assembly when created with the linker. The linker does not allow you to rename the resource in the assembly.  
 
- If *filename* is a .NET Framework resource (.resources) file created, for example, by the [Resource File Generator (Resgen.exe)](http://msdn.microsoft.com/Library/8ef159de-b660-4bec-9213-c3fbc4d1c6f4) or in the development environment, it can be accessed with members in the **System.Resources** namespace (see [System.Resources.ResourceManager](https://msdn.microsoft.com/en-us/library/system.resources.resourcemanager.aspx) for more information). For all other resources, use the **GetManifestResource**\* methods in **System.Reflection.Assembly** class to access the resource at run time.  
+ If *filename* is a .NET Framework resource (.resources) file created, for example, by the [Resource File Generator (Resgen.exe)](/dotnet/framework/tools/resgen-exe-resource-file-generator) or in the development environment, it can be accessed with members in the **System.Resources** namespace (see [System.Resources.ResourceManager](https://msdn.microsoft.com/en-us/library/system.resources.resourcemanager.aspx) for more information). For all other resources, use the **GetManifestResource**\* methods in **System.Reflection.Assembly** class to access the resource at run time.  
 
  Other linker options that affect assembly generation are:  
 

docs/build/reference/clr-common-language-runtime-compilation.md

@@ -72,7 +72,7 @@ Enables applications and components to use features from the common language run
  /clr:pure is deprecated. A future version of the compiler may not support this option. We recommend that you port code that must be pure MSIL to C#.  
 
  **/clr:safe**  
- Produces an MSIL-only (no native executable code), verifiable output file. **/clr:safe** enables verification diagnostics ([PEVerify Tool (Peverify.exe)](http://msdn.microsoft.com/Library/f4f46f9e-8d08-4e66-a94b-0c69c9b0bbfa)).  
+ Produces an MSIL-only (no native executable code), verifiable output file. **/clr:safe** enables verification diagnostics ([PEVerify Tool (Peverify.exe)](/dotnet/framework/tools/peverify-exe-peverify-tool)).  
 
 
  /clr:safe is deprecated. A future version of the compiler may not support this option. We recommend that you port code that must be pure, verifiable MSIL to C#.  
@@ -121,7 +121,7 @@ Enables applications and components to use features from the common language run
 
  The global variables in a native object file are initialized first (during DllMain if the executable is a DLL), and then the global variables in the managed section are initialized (before any managed code is run). `#pragma`[init_seg](../../preprocessor/init-seg.md) only affects the order of initialization in the managed and unmanaged categories.  
 
- Compiling by using **/clr:safe** is analogous to compiling by using [/platform:anycpu](/dotnet/articles/csharp/language-reference/compiler-options/platform-compiler-option) in languages such as C#.  
+ Compiling by using **/clr:safe** is analogous to compiling by using [/platform:anycpu](/dotnet/csharp/language-reference/compiler-options/platform-compiler-option) in languages such as C#.  
 
 ## Safe and Pure Images  
  A pure image uses a CLR version of the C run-time (CRT) library. However, the CRT is not verifiable, so you cannot use the CRT when you compile by using **/clr:safe**. For more information, see [CRT Library Features](../../c-runtime-library/crt-library-features.md).  

docs/build/reference/consistency-rules-for-per-file-use-of-precompiled-headers.md

@@ -1,79 +1,3 @@
 ---
-title: "Consistency Rules for Per-File Use of Precompiled Headers | Microsoft Docs"
-ms.custom: ""
-ms.date: "11/04/2016"
-ms.reviewer: ""
-ms.suite: ""
-ms.technology:  
-  - "cpp-tools"
-ms.tgt_pltfrm: ""
-ms.topic: "article"
-dev_langs: 
-  - "C++"
-helpviewer_keywords: 
-  - "precompiled header files, consistency rules"
-  - "PCH files, consistency rules"
-  - ".pch files, consistency rules"
-ms.assetid: afd49365-48bc-41f4-b700-fe8297b944a1
-caps.latest.revision: 6
-author: "corob-msft"
-ms.author: "corob"
-manager: "ghogen"
-translation.priority.ht: 
-  - "cs-cz"
-  - "de-de"
-  - "es-es"
-  - "fr-fr"
-  - "it-it"
-  - "ja-jp"
-  - "ko-kr"
-  - "pl-pl"
-  - "pt-br"
-  - "ru-ru"
-  - "tr-tr"
-  - "zh-cn"
-  - "zh-tw"
----
-# Consistency Rules for Per-File Use of Precompiled Headers
-The [/Yu](../../build/reference/yu-use-precompiled-header-file.md) compiler option lets you specify which precompiled header (PCH) file to use.  
-  
- When you use a PCH, the compiler assumes the same compilation environment — using consistent compiler options, pragmas, and so on — that was in effect when you created the PCH, unless you specify otherwise. If the compiler detects an inconsistency, it issues a warning and identifies the inconsistency where possible. Such warnings do not necessarily indicate a problem with the PCH; they simply warn you of possible conflicts. Consistency requirements for PCHs are described in the following sections.  
-  
-## Compiler Option Consistency  
- The following compiler options can trigger an inconsistency warning when using a PCH:  
-  
--   Macros created using the Preprocessor (/D) option must be the same between the compilation that created the PCH and the current compilation. The state of defined constants is not checked, but unpredictable results can occur if these change.  
-  
--   PCHs do not work with the /E and /EP options.  
-  
--   PCHs must be created using either the Generate Browse Info (/FR) option or the Exclude Local Variables (/Fr) option before subsequent compilations that use the PCH can use these options.  
-  
-## C 7.0-Compatible (/Z7)  
- If this option is in effect when the PCH is created, subsequent compilations that use the PCH can use the debugging information.  
-  
- If the C 7.0-Compatible (/Z7) option is not in effect when the PCH is created, subsequent compilations that use the PCH and /Z7 trigger a warning. The debugging information is placed in the current .obj file, and local symbols defined in the PCH are not available to the debugger.  
-  
-## Include Path Consistency  
- A PCH does not contain information about the include path that was in effect when it was created. When you use a .pch file, the compiler always uses the include path specified in the current compilation.  
-  
-## Source File Consistency  
- When you specify the Use Precompiled Header File (/Yu) option, the compiler ignores all preprocessor directives (including pragmas) that appear in the source code that will be precompiled. The compilation specified by such preprocessor directives must be the same as the compilation used for the Create Precompiled Header File (/Yc) option.  
-  
-## Pragma Consistency  
- Pragmas processed during the creation of a PCH usually affect the file with which the PCH is subsequently used. The comment and message pragmas do not affect the remainder of the compilation.  
-  
- The following pragmas are retained as part of a PCH, and affect the remainder of a compilation that uses the PCH.  
-  
-||||  
-|-|-|-|  
-|alloc_text|include_alias|pack|  
-|auto_inline|init_seg|pointers_to_members|  
-|check_stack|inline_depth|setlocale|  
-|code_seg|inline_recursion|vtordisp|  
-|data_seg|intrinsic|warning|  
-|function|optimize||  
-  
-## See Also  
- [Precompiled Header Consistency Rules](../../build/reference/precompiled-header-consistency-rules.md)   
- [/Yu (Use Precompiled Header File)](../../build/reference/yu-use-precompiled-header-file.md)   
- [Compiler Options](../../build/reference/compiler-options.md)
+redirect_url: /cpp/build/reference/creating-precompiled-header-files#consistency-rules-for-per-file-use-of-precompiled-headers
+---

docs/build/reference/consistency-rules-for-yc-and-yu.md

@@ -1,89 +1,3 @@
 ---
-title: "Consistency Rules for -Yc and -Yu | Microsoft Docs"
-ms.custom: ""
-ms.date: "11/04/2016"
-ms.reviewer: ""
-ms.suite: ""
-ms.technology:  
-  - "cpp-tools"
-ms.tgt_pltfrm: ""
-ms.topic: "article"
-f1_keywords: 
-  - "/yc"
-  - "/yu"
-dev_langs: 
-  - "C++"
-helpviewer_keywords: 
-  - "Yu compiler option [C++]"
-  - "/Yu compiler option [C++]"
-  - "-Yu compiler option [C++]"
-  - "-Yc compiler option [C++]"
-  - "/Yc compiler option [C++]"
-  - "Yc compiler option [C++]"
-ms.assetid: 9dfb0e32-ec9b-4a36-9355-27a0e5fba512
-caps.latest.revision: 6
-author: "corob-msft"
-ms.author: "corob"
-manager: "ghogen"
-translation.priority.ht: 
-  - "cs-cz"
-  - "de-de"
-  - "es-es"
-  - "fr-fr"
-  - "it-it"
-  - "ja-jp"
-  - "ko-kr"
-  - "pl-pl"
-  - "pt-br"
-  - "ru-ru"
-  - "tr-tr"
-  - "zh-cn"
-  - "zh-tw"
----
-# Consistency Rules for /Yc and /Yu
-When you use a precompiled header created using /Yc or /Yu, the compiler compares the current compilation environment to the one that existed when you created the .pch file. Be sure to specify an environment consistent with the previous one (using consistent compiler options, pragmas, and so on) for the current compilation. If the compiler detects an inconsistency, it issues a warning and identifies the inconsistency where possible. Such warnings don't necessarily indicate a problem with the .pch file; they simply warn you of possible conflicts. The following sections explain the consistency requirements for precompiled headers.  
-  
-## Compiler Option Consistency  
- The following table lists compiler options that might trigger an inconsistency warning when using a precompiled header.  
-  
-|Option|Name|Rule|  
-|------------|----------|----------|  
-|/D|Define constants and macros|Must be the same between the compilation that created the precompiled header and the current compilation. The state of defined constants is not checked, but unpredictable results can occur if your files depend on the values of the changed constants.|  
-|/E or /EP|Copy preprocessor output to standard output|Precompiled headers do not work with the /E or /EP option.|  
-|/Fr or /FR|Generate Microsoft Source Browser information|For the /Fr and /FR options to be valid with the /Yu option, they must also have been in effect when the precompiled header was created. Subsequent compilations that use the precompiled header also generate Source Browser information. Browser information is placed in a single .sbr file and is referenced by other files in the same manner as CodeView information. You cannot override the placement of Source Browser information.|  
-|/GA, /GD, /GE, /Gw, or /GW|Windows protocol options|Must be the same between the compilation that created the precompiled header and the current compilation. If these options differ, a warning message results.|  
-|/Zi|Generate complete debugging information|If this option is in effect when the precompiled header is created, subsequent compilations that use the precompilation can use that debugging information. If /Zi is not in effect when the precompiled header is created, subsequent compilations that use the precompilation and the /Zi option trigger a warning. The debugging information is placed in the current object file, and local symbols defined in the precompiled header are not available to the debugger.|  
-  
-> [!NOTE]
->  The precompiled header facility is intended for use only with a file with C and C++ source files.  
-  
-## Include Path Consistency  
- A precompiled header created with /Yc does not contain information about the include path that was in effect when you created the .pch file. When you use a .pch file, the compiler always uses the include path specified in the current compilation.  
-  
-## Source File Consistency  
- When you use a precompiled header, the compiler ignores all preprocessor directives (including pragmas) that appear before the hdrstop pragma. The compilation specified by such preprocessor directives must be the same as the compilation used to create the precompiled header file.  
-  
-## Pragma Consistency  
- Pragmas processed during the compilation of a precompiled header usually affect the file in which the precompiled header is subsequently used. The following pragmas affect only the code within the .pch file; they do not affect code that subsequently uses the .pch file:  
-  
-||||  
-|-|-|-|  
-|Comment|page|subtitle|  
-|Linesize|pagesize|Title|  
-|Message|skip||  
-  
- The following pragmas are retained as part of a precompiled header, and affect the remainder of a compilation that uses the precompiled header:  
-  
-||||  
-|-|-|-|  
-|alloc_text|function|optimize|  
-|auto_inline|inline_depth|Pack|  
-|check_pointer|inline_recursion|same_seg|  
-|check_stack|intrinsic|warning|  
-|code_seg|loop_opt||  
-|data_seg|native_caller||  
-  
-## See Also  
- [Precompiled Header Consistency Rules](../../build/reference/precompiled-header-consistency-rules.md)   
- [/Yc (Create Precompiled Header File)](../../build/reference/yc-create-precompiled-header-file.md)   
- [/Yu (Use Precompiled Header File)](../../build/reference/yu-use-precompiled-header-file.md)
+redirect_url: /cpp/build/reference/creating-precompiled-header-files#consistency-rules-for-yc-and-yu
+---