update links to compiler options area

Most of these updates were straightforward substitutions of the new option for the old. There are a few exceptions:

- Some of the links were from Visual Basic content, but the destination was C# content. Where possible, the link changed to the appropriate VB equivalent.
- The displayed hyperlink text was not changed for the F# links.
- Some warning and error messages only applied when the command line (older) syntax was used. In those cases, the link was updated, but the displayed text remained the same.
- A small number of links were to options no longer supported. These were from error messages for those options. The corresponding supported option was linked in a note about updating.

Author: BillWagner

docs/core/compatibility/code-analysis/5.0/ca1416-platform-compatibility-analyzer.md

@@ -88,7 +88,7 @@ public void PlayCMajor()
 
 If you don't want to fix all your call sites, you can choose one of the following options to suppress the warning:
 
-- To suppress rule CA1416, you can do so using `#pragma` or the [-nowarn](../../../../csharp/language-reference/compiler-options/nowarn-compiler-option.md) compiler flag, or by [setting the rule's severity](../../../../fundamentals/code-analysis/configuration-options.md#severity-level) to `none` in an .editorconfig file.
+- To suppress rule CA1416, you can do so using `#pragma` or the [**DisabledWarnings**](../../../../csharp/language-reference/compiler-options/errors-and-warnings.md#disabledwarnings) compiler flag, or by [setting the rule's severity](../../../../fundamentals/code-analysis/configuration-options.md#severity-level) to `none` in an .editorconfig file.
 
   ```csharp
   public void PlayCMajor()

docs/csharp/codedoc.md

@@ -29,7 +29,7 @@ You can generate the XML file at compile time by doing one of the following:
 
 - If you are developing an application using Visual Studio, right-click on the project and select **Properties**. In the properties dialog, select the **Build** tab, and check **XML documentation file**. You can also change the location to which the compiler writes the file.
 
-- If you are compiling a .NET application from the command line, add the [-doc compiler option](language-reference/compiler-options/doc-compiler-option.md) when compiling.  
+- If you are compiling a .NET application from the command line, add the [**Doc** compiler option](language-reference/compiler-options/output.md#doc) when compiling.  
 
 XML documentation comments use triple forward slashes (`///`) and an XML formatted comment body. For example:
 

docs/csharp/language-reference/compiler-messages/cs0006.md

@@ -12,4 +12,4 @@ ms.assetid: fe029a0e-d85a-4d8e-8a46-01f6120092fe
 
 Metadata file 'dll_name' could not be found
 
- The program was compiled and explicitly passed the name of a file that contained metadata; however, the .dll was not found. For more information, see [-reference (C# Compiler Options)](../compiler-options/reference-compiler-option.md).
+ The program was compiled and explicitly passed the name of a file that contained metadata; however, the .dll was not found. For more information, see [**References** (C# Compiler Options)](../compiler-options/inputs.md#references).

docs/csharp/language-reference/compiler-messages/cs0122.md

@@ -14,7 +14,7 @@ ms.assetid: 5f639a66-c807-4166-b88a-93e5f272ceb7
 
  The [access modifier](../keywords/index.md) for a class member prevents accessing the member. For more information, see [Access Modifiers](../../programming-guide/classes-and-structs/access-modifiers.md).
 
- One cause of this (not shown in the sample below) can be omitting the **/out** compiler flag on the target of a friend assembly. For more information, see [Friend Assemblies](../../../standard/assembly/friend.md) and [-out (C# Compiler Options)](../compiler-options/out-compiler-option.md).
+ One cause of this (not shown in the sample below) can be omitting the **/out** compiler flag on the target of a friend assembly. For more information, see [Friend Assemblies](../../../standard/assembly/friend.md) and [**OutputAssembly** (C# Compiler Options)](../compiler-options/outputs.md#outputassembly).
 
 ## Example
 

docs/csharp/language-reference/compiler-messages/cs0234.md

@@ -14,7 +14,7 @@ The type or namespace name 'name' does not exist in the namespace 'namespace' (a
 
  A type was expected. Possible causes for this error include the following:  
 
-- An assembly that contains the definition of a type was not referenced in the compilation; use [-reference (Import Metadata)](../compiler-options/reference-compiler-option.md) to specify the assembly  
+- An assembly that contains the definition of a type was not referenced in the compilation; use [**References** (Import Metadata)](../compiler-options/inputs.md#references) to specify the assembly  
 
 - You passed a variable name to the [typeof](../operators/type-testing-and-cast.md#typeof-operator) operator.  
 

docs/csharp/language-reference/compiler-messages/cs0246.md

@@ -12,13 +12,13 @@ ms.assetid: 4948fae2-2cc0-4ce4-b98c-ea69a8120b71
 
 The type or namespace name 'type/namespace' could not be found (are you missing a using directive or an assembly reference?)  
 
-A type or namespace that is used in the program was not found. You might have forgotten to reference ([-reference](../compiler-options/reference-compiler-option.md)) the assembly that contains the type, or you might not have added the required [using directive](../keywords/using-directive.md).  Or, there might be an issue with the assembly you are trying to reference.  
+A type or namespace that is used in the program was not found. You might have forgotten to reference ([**References**](../compiler-options/inputs.md#references)) the assembly that contains the type, or you might not have added the required [using directive](../keywords/using-directive.md).  Or, there might be an issue with the assembly you are trying to reference.  
 
 The following situations cause compiler error CS0246.  
 
 - Did you misspell the name of the type or namespace? Without the correct name, the compiler cannot find the definition for the type or namespace. This often occurs because the casing used in the name of the type is not correct. For example, `Dataset ds;` generates CS0246 because the s in Dataset must be capitalized.  
 
-- If the error is for a namespace name, did you add a reference ([-reference](../compiler-options/reference-compiler-option.md)) to the assembly that contains the namespace? For example, your code might contain the directive `using Accessibility`. However, if your project does not reference the assembly Accessibility.dll, error CS0246 is reported. For more information, see [Managing references in a project](/visualstudio/ide/managing-references-in-a-project)  
+- If the error is for a namespace name, did you add a reference ([**References**](../compiler-options/inputs.md#references)) to the assembly that contains the namespace? For example, your code might contain the directive `using Accessibility`. However, if your project does not reference the assembly Accessibility.dll, error CS0246 is reported. For more information, see [Managing references in a project](/visualstudio/ide/managing-references-in-a-project)  
 
 - If the error is for a type name, did you include the proper [using directive](../keywords/using-directive.md), or, alternatively, fully qualify the name of the type? Consider the following declaration: `DataSet ds`. To use the `DataSet` type, you need two things. First, you need a reference to the assembly that contains the definition for the `DataSet` type. Second, you need a `using` directive for the namespace where `DataSet` is located. For example, because `DataSet` is located in the **System.Data** namespace, you need the following directive at the beginning of your code: `using System.Data`.  
 

docs/csharp/language-reference/compiler-messages/cs0433.md

@@ -14,7 +14,7 @@ The type TypeName1 exists in both TypeName2 and TypeName3
 
  Two different assemblies referenced in your application contain the same namespace and type, which produces ambiguity.  
 
- To resolve this error, use the alias feature of the [-reference (C# Compiler Options)](../compiler-options/reference-compiler-option.md) compiler option or do not reference one of your assemblies.  
+ To resolve this error, use the alias feature of the ([**References**](../compiler-options/inputs.md#references)) compiler option or do not reference one of your assemblies.  
 
 This error can also occur in ASP.NET Web Forms if:
 

docs/csharp/language-reference/compiler-messages/cs0518.md

@@ -14,7 +14,7 @@ Predefined type 'type' is not defined or imported
 
  The main cause for this problem is that the project is not importing mscorlib.dll, which defines the entire System namespace. This can be caused by one of the following:  
 
-- The [-nostdlib](../compiler-options/nostdlib-compiler-option.md) option from the command line compiler has been specified. The /nostdlib option prevents the import of mscorlib.dll. Use this option if you want to define or create a user-specific System namespace.  
+- The [**NoStandardLib**](../compiler-options/advanced.md#nostandardlib) option from the command line compiler has been specified. The **NoStandardLib** option prevents the import of mscorlib.dll. Use this option if you want to define or create a user-specific System namespace.  
 
 - An incorrect mscorlib.dll is referenced.  
 

docs/csharp/language-reference/compiler-messages/cs1548.md

@@ -16,7 +16,7 @@ Cryptographic failure while signing assembly 'assembly' — 'reason'
 
  To fully sign an assembly, you must provide a valid key file that contains information about the public and private keys. To delay sign an assembly, you must select the **Delay sign only** check box and provide a valid key file that contains information about the public key information. The private key is not necessary when an assembly is delay-signed.  
 
- For more information, see [How to: Sign an Assembly with a Strong Name](../../../standard/assembly/sign-strong-name.md), [-keyfile (C# Compiler Options)](../compiler-options/keyfile-compiler-option.md) and [-delaysign (C# Compiler Options)](../compiler-options/delaysign-compiler-option.md).  
+ For more information, see [How to: Sign an Assembly with a Strong Name](../../../standard/assembly/sign-strong-name.md), [**KeyFile** (C# Compiler Options)](../compiler-options/security.md#keyfile) and [**DelaySign** (C# Compiler Options)](../compiler-options/security.md#delaysign).  
 
  When creating an assembly, the C# compiler calls into a utility called al.exe. If there is a failure in the assembly creation, the reason for the failure is reported by al.exe. See [Al.exe Tool Errors and Warnings](../../../framework/tools/al-exe-assembly-linker.md#errors-and-warnings) and search that topic for the text reported by the compiler in 'reason'.  
 

docs/csharp/language-reference/compiler-messages/cs1564.md

@@ -38,5 +38,5 @@ public class Test
 
 ## See also
 
-- [-win32manifest (C# Compiler Options)](../compiler-options/win32manifest-compiler-option.md)
-- [-win32res (C# Compiler Options)](../compiler-options/win32res-compiler-option.md)
+- [**Win32Manifest** (C# Compiler Options)](../compiler-options/resources.md#win32manifest)
+- [**Win32Resource** (C# Compiler Options)](../compiler-options/resources.md#win32resource)