Merge pull request #853 from MicrosoftDocs/master

5/30 AM Publish

Author: Taojunshen

docs/build/reference/defaultlib-specify-default-library.md

@@ -1,7 +1,7 @@
 ---
-title: "-DEFAULTLIB (Specify Default Library) | Microsoft Docs"
+title: "/DEFAULTLIB (Specify Default Library) | Microsoft Docs"
 ms.custom: ""
-ms.date: "11/04/2016"
+ms.date: "05/29/2018"
 ms.technology: ["cpp-tools"]
 ms.topic: "reference"
 f1_keywords: ["VC.Project.VCLinkerTool.DefaultLibraries", "/defaultlib"]
@@ -13,29 +13,38 @@ ms.author: "corob"
 ms.workload: ["cplusplus"]
 ---
 # /DEFAULTLIB (Specify Default Library)
-```  
-/DEFAULTLIB:library  
-```  
-  
-## Remarks  
- where:  
-  
- *library*  
- The name of a library to search when resolving external references.  
-  
-## Remarks  
- The /DEFAULTLIB option adds one *library* to the list of libraries that LINK searches when resolving references. A library specified with /DEFAULTLIB is searched after libraries specified on the command line and before default libraries named in .obj files.  
-  
- The [Ignore All Default Libraries](../../build/reference/nodefaultlib-ignore-libraries.md) (/NODEFAULTLIB) option overrides /DEFAULTLIB:*library*. The [Ignore Libraries](../../build/reference/nodefaultlib-ignore-libraries.md) (/NODEFAULTLIB:*library*) option overrides /DEFAULTLIB:*library* when the same *library* name is specified in both.  
-  
-### To set this linker option in the Visual Studio development environment  
-  
--   This linker option is not available from the Visual Studio development environment. To add a library to the link phase, use the **Additional Dependencies** property from the **Input** property page.  
-  
-### To set this linker option programmatically  
-  
--   See <xref:Microsoft.VisualStudio.VCProjectEngine.VCLinkerTool.AdditionalOptions%2A>.  
-  
-## See Also  
- [Setting Linker Options](../../build/reference/setting-linker-options.md)   
- [Linker Options](../../build/reference/linker-options.md)
+
+Specify a default library to search to resolve external references.
+
+## Syntax
+
+> **/DEFAULTLIB**:_library_
+
+### Arguments
+
+|Argument|Description|
+|-|-|
+*library*|The name of a library to search when resolving external references.
+
+## Remarks
+
+The **/DEFAULTLIB** option adds one *library* to the list of libraries that LINK searches when resolving references. A library specified with **/DEFAULTLIB** is searched after libraries specified explicitly on the command line and before default libraries named in .obj files.
+
+When used without arguments, the [/NODEFAULTLIB (Ignore All Default Libraries)](../../build/reference/nodefaultlib-ignore-libraries.md) option overrides all **/DEFAULTLIB**:*library* options. The **/NODEFAULTLIB**:*library* option overrides **/DEFAULTLIB**:*library* when the same *library* name is specified in both.
+
+### To set this linker option in the Visual Studio development environment
+
+1. Open the project **Property Pages** dialog box. For more information, see [Working with Project Properties](../../ide/working-with-project-properties.md).
+
+1. Select the **Configuration Properties** > **Linker** > **Command Line** property page.
+
+1. In **Additional Options**, enter a **/DEFAULTLIB**:*library* option for each library to search. Choose **OK** to save your changes.
+
+### To set this linker option programmatically
+
+- See <xref:Microsoft.VisualStudio.VCProjectEngine.VCLinkerTool.AdditionalOptions%2A>.
+
+## See also
+
+- [Setting Linker Options](../../build/reference/setting-linker-options.md)
+- [Linker Options](../../build/reference/linker-options.md)

docs/c-runtime-library/reference/get-osfhandle.md

@@ -1,7 +1,7 @@
 ---
 title: "_get_osfhandle | Microsoft Docs"
 ms.custom: ""
-ms.date: "12/12/2017"
+ms.date: "05/29/2018"
 ms.technology: ["cpp-standard-libraries"]
 ms.topic: "reference"
 apiname: ["_get_osfhandle"]
@@ -34,7 +34,7 @@ An existing file descriptor.
 
 ## Return Value
 
-Returns an operating-system file handle if *fd* is valid. Otherwise, the invalid parameter handler is invoked, as described in [Parameter Validation](../../c-runtime-library/parameter-validation.md). If execution is allowed to continue, this function returns **INVALID_HANDLE_VALUE** (-1) and sets **errno** to **EBADF**, indicating an invalid file handle.
+Returns an operating-system file handle if *fd* is valid. Otherwise, the invalid parameter handler is invoked, as described in [Parameter Validation](../../c-runtime-library/parameter-validation.md). If execution is allowed to continue, this function returns **INVALID_HANDLE_VALUE** (-1) and sets **errno** to **EBADF**, indicating an invalid file handle. To avoid a compiler warning when the result is used in routines that expect a Win32 file handle, cast it to a **HANDLE** type.
 
 ## Remarks
 

docs/c-runtime-library/reference/open-osfhandle.md

@@ -1,7 +1,7 @@
 ---
 title: "_open_osfhandle | Microsoft Docs"
 ms.custom: ""
-ms.date: "12/12/2017"
+ms.date: "05/29/2018"
 ms.technology: ["cpp-standard-libraries"]
 ms.topic: "reference"
 apiname: ["_open_osfhandle"]
@@ -42,23 +42,18 @@ If successful, **_open_osfhandle** returns a C run-time file descriptor. Otherwi
 
 ## Remarks
 
-The **_open_osfhandle** function allocates a C run-time file descriptor and associates it with the operating-system file handle specified by *osfhandle*. The *flags* argument is an integer expression formed from one or more of the manifest constants defined in Fcntl.h. When two or more manifest constants are used to form the *flags* argument, the constants are combined with the bitwise-OR operator ( **|** ).
+The **_open_osfhandle** function allocates a C run-time file descriptor and associates it with the operating-system file handle specified by *osfhandle*. To avoid a compiler warning, cast the *osfhandle* argument from **HANDLE** to **intptr_t**. The *flags* argument is an integer expression formed from one or more of the manifest constants defined in \<fcntl.h>. When two or more manifest constants are used to form the *flags* argument, the constants are combined with the bitwise-OR operator ( **&#124;** ).
 
-Fcntl.h defines the following manifest constants:
+These manifest constants are defined in \<fcntl.h>:
 
-**\_O\_APPEND**
-Positions a file pointer to the end of the file before every write operation.
+|||
+|-|-|
+**\_O\_APPEND**|Positions a file pointer to the end of the file before every write operation.
+**\_O\_RDONLY**|Opens the file for reading only.
+**\_O\_TEXT**|Opens the file in text (translated) mode.
+**\_O\_WTEXT**|Opens the file in Unicode (translated UTF-16) mode.
 
-**\_O\_RDONLY**
-Opens the file for reading only.
-
-**\_O\_TEXT**
-Opens the file in text (translated) mode.
-
-**\_O\_WTEXT**
-Opens the file in Unicode (translated UTF-16) mode.
-
-To close a file opened with **_open_osfhandle**, call [\_close](close.md). The underlying OS file handle is also closed by a call to **_close**, so it is not necessary to call the Win32 function **CloseHandle** on the original handle. If the file descriptor is owned by a **FILE &#42;** stream, then calling [fclose](fclose-fcloseall.md) on that **FILE &#42;** stream also closes both the file descriptor and the underlying handle. In this case, do not call **_close** on the file descriptor.
+The **_open_osfhandle** call transfers ownership of the Win32 file handle to the file descriptor. To close a file opened with **_open_osfhandle**, call [\_close](close.md). The underlying OS file handle is also closed by a call to **_close**, so it is not necessary to call the Win32 function **CloseHandle** on the original handle. If the file descriptor is owned by a **FILE &#42;** stream, then calling [fclose](fclose-fcloseall.md) on that **FILE &#42;** stream also closes both the file descriptor and the underlying handle. In this case, do not call **_close** on the file descriptor.
 
 ## Requirements
 

docs/cpp/errors-and-exception-handling-modern-cpp.md

@@ -38,7 +38,7 @@ class MyClass
 public:  
    void MyFunc(char c)  
    {  
-      if(c < numeric_limits<char>::max())  
+      if(c > numeric_limits<char>::max())  
          throw invalid_argument("MyFunc argument too large.");  
       //...  
    }  

docs/error-messages/compiler-errors-1/fatal-error-c1083.md

@@ -96,6 +96,8 @@ When a project is configured to use precompiled headers, the relevant .pch files
 
 - The file is compiled by using a different **/analyze** compiler option setting than is used to precompile the headers. When the headers for a project are precompiled, all should use the same **/analyze** settings. For more information, see [/analyze (Code Analysis)](../../build/reference/analyze-code-analysis.md).
 
+- The file or directory was created by the Windows Subsystem for Linux, per-directory case sensitivity is enabled, and the specified case of a path or file does not match the case of the path or file on disk.
+
 - The file, the directory, or the disk is read-only.
 
 - Visual Studio or the command line tools do not have sufficient permissions to read the file or the directory. This can happen, for example, when the project files have different ownership than the process running Visual Studio or the command line tools. Sometimes this issue can be fixed by running Visual Studio or the developer command prompt as Administrator.
@@ -117,4 +119,4 @@ For information about how to build C/C++ projects in the IDE or on the command l
 
 ## See also
 
-[MSBuild Properties](/visualstudio/msbuild/msbuild-properties)
+- [MSBuild Properties](/visualstudio/msbuild/msbuild-properties)

docs/error-messages/tool-errors/TOC.md

@@ -155,6 +155,7 @@
 ## [Linker Tools Error LNK1312](linker-tools-error-lnk1312.md)
 ## [Linker Tools Error LNK1313](linker-tools-error-lnk1313.md)
 ## [Linker Tools Error LNK1314](linker-tools-error-lnk1314.md)
+## [Linker Tools Error LNK1318](linker-tools-error-lnk1318.md)
 ## [Linker Tools Error LNK1332](linker-tools-error-lnk1332.md)
 ## [Linker Tools Error LNK1561](linker-tools-error-lnk1561.md)
 ## [Linker Tools Error LNK2001](linker-tools-error-lnk2001.md)
@@ -185,6 +186,7 @@
 ## [Linker Tools Warning LNK4006](linker-tools-warning-lnk4006.md)
 ## [Linker Tools Warning LNK4010](linker-tools-warning-lnk4010.md)
 ## [Linker Tools Warning LNK4014](linker-tools-warning-lnk4014.md)
+## [Linker Tools Warning LNK4020](linker-tools-warning-lnk4020.md)
 ## [Linker Tools Warning LNK4022](linker-tools-warning-lnk4022.md)
 ## [Linker Tools Warning LNK4037](linker-tools-warning-lnk4037.md)
 ## [Linker Tools Warning LNK4039](linker-tools-warning-lnk4039.md)

docs/error-messages/tool-errors/linker-tools-error-lnk1318.md

@@ -0,0 +1,34 @@
+---
+title: "Linker Tools Error LNK1318 | Microsoft Docs"
+ms.custom: ""
+ms.date: "05/29/2018"
+ms.technology: ["cpp-diagnostics"]
+ms.topic: "error-reference"
+f1_keywords: ["LNK1318"]
+dev_langs: ["C++"]
+helpviewer_keywords: ["LNK1318"]
+author: "corob-msft"
+ms.author: "corob"
+ms.workload: ["cplusplus"]
+---
+# Linker Tools Error LNK1318
+
+> Unexpected PDB error; *cause* '*details*'
+
+The linker encountered an unexpected error when opening, reading, or writing to a PDB file.
+
+This error message is produced for uncommon issues in PDB files. The *cause* and *details* represent the information available to the linker when the failure occurred. This may not be very useful, as common errors when dealing with PDB files have separate, more informative error messages.
+
+Because the source of the error is uncommon, there is only generic advice available for resolving this issue:
+
+- Perform a clean operation in your build directories, and then do a full build of your solution.
+
+- Reboot your computer, or check for stray or hung mspdbsrv.exe processes and kill them in TaskManager.
+
+- Turn off antivirus checks in your project directories.
+
+- Use the [/Zf](../../build/reference/zf.md) compiler option if using [/MP](../../build/reference/mp-build-with-multiple-processes.md) with MSBuild or another parallel build process.
+
+- Try building by using the 64-bit hosted toolset.
+
+- Serialize linking to mitigate parallel link issues if needed. This error can be caused if mspdbsrv.exe is launched by one instance of link, and is shut down before another instance of link is done using it. The downside to this fix is that your project builds may take considerably longer to complete.

docs/error-messages/tool-errors/linker-tools-errors-and-warnings.md

@@ -121,6 +121,8 @@ LINK, LIB, DUMPBIN, and EDITBIN generate these errors and warnings.
 
 [Linker Tools Error LNK1314](../../error-messages/tool-errors/linker-tools-error-lnk1314.md)
 
+[Linker Tools Error LNK1318](../../error-messages/tool-errors/linker-tools-error-lnk1318.md)
+
 [Linker Tools Error LNK1332](../../error-messages/tool-errors/linker-tools-error-lnk1332.md)
 
 [Linker Tools Error LNK1561](../../error-messages/tool-errors/linker-tools-error-lnk1561.md)
@@ -171,6 +173,8 @@ LINK, LIB, DUMPBIN, and EDITBIN generate these errors and warnings.
 
 [Linker Tools Warning LNK4014](../../error-messages/tool-errors/linker-tools-warning-lnk4014.md)
 
+[Linker Tools Warning LNK4020](../../error-messages/tool-errors/linker-tools-warning-lnk4020.md)
+
 [Linker Tools Warning LNK4022](../../error-messages/tool-errors/linker-tools-warning-lnk4022.md)
 
 [Linker Tools Warning LNK4039](../../error-messages/tool-errors/linker-tools-warning-lnk4039.md)

docs/error-messages/tool-errors/linker-tools-warning-lnk4020.md

@@ -0,0 +1,20 @@
+---
+title: "Linker Tools Warning LNK4020 | Microsoft Docs"
+ms.custom: ""
+ms.date: "05/29/2018"
+ms.technology: ["cpp-diagnostics"]
+ms.topic: "error-reference"
+f1_keywords: ["LNK4020"]
+dev_langs: ["C++"]
+helpviewer_keywords: ["LNK4020"]
+author: "corob-msft"
+ms.author: "corob"
+ms.workload: ["cplusplus"]
+---
+# Linker Tools Warning LNK4020
+
+> a type record in '*filename*' is corrupted; some symbols and types may not be accessible from the debugger
+
+The PDB file *filename* has a corrupted type record.
+
+This issue is often secondary to other build issues; unless this is the first reported build issue, deal with the other errors and warnings first. If this is the first reported issue, you may need to clean your build directories and rebuild your project. If you use parallel build processes, see if the error persists when you serialize your build.