Fix Bug 976235 : [LSI]Link to enum fields were incorrectly migrated (dotnet#2070)

* fix enum reference

* fix enum field reference

Author: yishengjin1413

xml/Microsoft.Build.BuildEngine/Project.xml

@@ -461,7 +461,7 @@
 ## Remarks  
  If the <xref:Microsoft.Build.BuildEngine.Project.ToolsVersion%2A> attribute is not present on the [Project Element (MSBuild)](http://msdn.microsoft.com/library/d1cda56a-dbef-4109-9201-39e962e3f653) element, getting the value returns the default Tools version of the parent <xref:Microsoft.Build.BuildEngine>.  
   
- The <xref:Microsoft.Build.BuildEngine.Project.DefaultToolsVersion%2A> value can differ from the Tools version used during a build if its value is overridden during construction of the <xref:Microsoft.Build.BuildEngine.Project> instance or it is set to a specific value with the <xref:Microsoft.Build.BuildEngine.Project.ToolsVersion%2A> property. Setting the <xref:Microsoft.Build.BuildEngine.Project.DefaultToolsVersion%2A> value cannot change the Tools version if it has been overridden, but you can change the Tools version using the <xref:Microsoft.Build.BuildEngine.Project.ToolsVersion%2A> property.  
+ The <xref:Microsoft.Build.BuildEngine.Project.DefaultToolsVersion%2A> value can differ from the Tools version used during a build if its value is overridden during construction of the <xref:Microsoft.Build.BuildEngine.Project.DefaultToolsVersion%2A> instance or it is set to a specific value with the <xref:Microsoft.Build.BuildEngine.Project.ToolsVersion%2A> property. Setting the <xref:Microsoft.Build.BuildEngine.Project.DefaultToolsVersion%2A> value cannot change the Tools version if it has been overridden, but you can change the Tools version using the <xref:Microsoft.Build.BuildEngine.Project.ToolsVersion%2A> property.  
   
  For more information about Tools versions, see `MSBuild Tool Set (ToolsVersion)`.  
   

xml/Microsoft.Build.Tasks.Deployment.Bootstrapper/BuildSettings.xml

@@ -149,7 +149,7 @@
 ## Remarks  
  If you specify <xref:Microsoft.Build.Tasks.Deployment.Bootstrapper.BuildSettings.ApplicationFile%2A>, the bootstraper will be published to the location specified by this value.  
   
- If <xref:Microsoft.Build.Tasks.Deployment.Bootstrapper.BuildSettings.ComponentsLocation%2A> is set to <xref:Microsoft.Build.Tasks.Deployment.Bootstrapper.ComponentsLocation>, required component files will be published to a location relative to this value.  
+ If <xref:Microsoft.Build.Tasks.Deployment.Bootstrapper.BuildSettings.ComponentsLocation%2A> is set to <xref:Microsoft.Build.Tasks.Deployment.Bootstrapper.ComponentsLocation.Relative>, required component files will be published to a location relative to this value.  
   
  Set this value to null if Setup.exe is not to be published to the Web.  
   

xml/Microsoft.Build.Tasks.Deployment.Bootstrapper/IBuildSettings.xml

@@ -142,7 +142,7 @@
 ## Remarks  
  If you have specified <xref:Microsoft.Build.Tasks.Deployment.Bootstrapper.BuildSettings.ApplicationFile%2A>, the bootstraper will be published to the location specified by this value.  
   
- If <xref:Microsoft.Build.Tasks.Deployment.Bootstrapper.BuildSettings.ComponentsLocation%2A> is set to <xref:Microsoft.Build.Tasks.Deployment.Bootstrapper.ComponentsLocation>, required component files will be published to a location relative to this value.  
+ If <xref:Microsoft.Build.Tasks.Deployment.Bootstrapper.BuildSettings.ComponentsLocation%2A> is set to <xref:Microsoft.Build.Tasks.Deployment.Bootstrapper.ComponentsLocation.Relative>, required component files will be published to a location relative to this value.  
   
  Set this value to null if Setup.exe is not to be published to the Web.  
   

xml/Microsoft.Build.Tasks.Deployment.ManifestUtilities/OutputMessage.xml

@@ -94,7 +94,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The values can be <xref:Microsoft.Build.Tasks.Deployment.ManifestUtilities.OutputMessageType>, <xref:Microsoft.Build.Tasks.Deployment.ManifestUtilities.OutputMessageType>, or <xref:Microsoft.Build.Tasks.Deployment.ManifestUtilities.OutputMessageType>. For more information, see <xref:Microsoft.Build.Tasks.Deployment.ManifestUtilities.OutputMessageType>.  
+ The values can be <xref:Microsoft.Build.Tasks.Deployment.ManifestUtilities.OutputMessageType.Error>, <xref:Microsoft.Build.Tasks.Deployment.ManifestUtilities.OutputMessageType.Info>, or <xref:Microsoft.Build.Tasks.Deployment.ManifestUtilities.OutputMessageType.Warning>. For more information, see <xref:Microsoft.Build.Tasks.Deployment.ManifestUtilities.OutputMessageType>.  
   
  ]]></format>
         </remarks>

xml/Microsoft.JScript/ArrayWrapper.xml

@@ -55,7 +55,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This property throws an <xref:Microsoft.JScript.JSError> exception if you try to set it.  
+ This property throws an <xref:Microsoft.JScript.JSError.AssignmentToReadOnly> exception if you try to set it.  
   
  ]]></format>
         </remarks>

xml/Microsoft.SqlServer.Server/SqlFunctionAttribute.xml

@@ -68,7 +68,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The default is <xref:Microsoft.SqlServer.Server.DataAccessKind>.<xref:Microsoft.SqlServer.Server.SqlFunctionAttribute.DataAccess%2A> is also required when connecting to remote servers if transactions integration is required (the default).  
+ The default is <xref:Microsoft.SqlServer.Server.DataAccessKind.None>.<xref:Microsoft.SqlServer.Server.SqlFunctionAttribute.DataAccess%2A> is also required when connecting to remote servers if transactions integration is required (the default).  
   
  If a Transact-SQL query is executed from inside a table-valued function (TVF), the <xref:Microsoft.SqlServer.Server.DataAccessKind>.`Read` property should be set.  
   
@@ -229,7 +229,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The default is <xref:Microsoft.SqlServer.Server.SystemDataAccessKind>.  
+ The default is <xref:Microsoft.SqlServer.Server.SystemDataAccessKind.None>.  
   
  ]]></format>
         </remarks>

xml/Microsoft.SqlServer.Server/SqlTriggerContext.xml

@@ -24,7 +24,7 @@
    
   
 ## Examples  
- The following example shows a <xref:Microsoft.SqlServer.Server.SqlTriggerContext> object being used to determine if an <xref:Microsoft.SqlServer.Server.TriggerAction> action occurred. If a row was inserted into the `user`'s table, the user name and real name are retrieved from the inserted row and then added to the **UserNameAudit** table.  
+ The following example shows a <xref:Microsoft.SqlServer.Server.SqlTriggerContext> object being used to determine if an <xref:Microsoft.SqlServer.Server.TriggerAction.Insert> action occurred. If a row was inserted into the `user`'s table, the user name and real name are retrieved from the inserted row and then added to the **UserNameAudit** table.  
   
  [!code-csharp[DataWorks SqlTriggerContext Sample#1](~/samples/snippets/csharp/VS_Snippets_ADO.NET/DataWorks SqlTriggerContext Sample/CS/source.cs#1)]
  [!code-vb[DataWorks SqlTriggerContext Sample#1](~/samples/snippets/visualbasic/VS_Snippets_ADO.NET/DataWorks SqlTriggerContext Sample/VB/source.vb#1)]  
@@ -130,7 +130,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Examples  
- The following example shows an auditing trigger. If an <xref:Microsoft.SqlServer.Server.TriggerAction> or <xref:Microsoft.SqlServer.Server.TriggerAction> action occurred, the affected rows are retrieved from the INSERTED and DELETED tables.  
+ The following example shows an auditing trigger. If an <xref:Microsoft.SqlServer.Server.TriggerAction.Insert> or <xref:Microsoft.SqlServer.Server.TriggerAction.Delete> action occurred, the affected rows are retrieved from the INSERTED and DELETED tables.  
   
  [!code-csharp[DataWorks SqlTriggerContext Sample#2](~/samples/snippets/csharp/VS_Snippets_ADO.NET/DataWorks SqlTriggerContext Sample/CS/source.cs#2)]
  [!code-vb[DataWorks SqlTriggerContext Sample#2](~/samples/snippets/visualbasic/VS_Snippets_ADO.NET/DataWorks SqlTriggerContext Sample/VB/source.vb#2)]  

xml/Microsoft.VisualBasic.ApplicationServices/ApplicationBase.xml

@@ -84,7 +84,7 @@
  Use the `My.Application.ChangeUICulture` method to change the culture that the current thread uses for retrieving culture-specific resources.  
   
 > [!IMPORTANT]
->  The `My.Application.ChangeCulture` method requires a <xref:System.Security.Permissions.SecurityPermission> with the <xref:System.Security.Permissions.SecurityPermissionFlag> set. Manipulating threads is dangerous because of the security state associated with threads. Therefore, this permission should be given only as necessary to trustworthy code. You cannot change a thread's culture in semi-trusted code.  
+>  The `My.Application.ChangeCulture` method requires a <xref:System.Security.Permissions.SecurityPermission> with the <xref:System.Security.Permissions.SecurityPermissionFlag.ControlThread> set. Manipulating threads is dangerous because of the security state associated with threads. Therefore, this permission should be given only as necessary to trustworthy code. You cannot change a thread's culture in semi-trusted code.  
   
 ## Availability by Project Type  
   

xml/Microsoft.VisualBasic.ApplicationServices/WindowsFormsApplicationBase.xml

@@ -79,9 +79,9 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- If the `authenticationMode` parameter is the <xref:Microsoft.VisualBasic.ApplicationServices.AuthenticationMode> enumeration value, then this constructor attempts to set the current thread's <xref:System.Threading.Thread.CurrentPrincipal%2A> property to the <xref:System.Security.Principal.WindowsPrincipal> for the current user.  
+ If the `authenticationMode` parameter is the <xref:Microsoft.VisualBasic.ApplicationServices.AuthenticationMode.Windows> enumeration value, then this constructor attempts to set the current thread's <xref:System.Threading.Thread.CurrentPrincipal%2A> property to the <xref:System.Security.Principal.WindowsPrincipal> for the current user.  
   
- If the `authenticationMode` parameter is the <xref:Microsoft.VisualBasic.ApplicationServices.AuthenticationMode> enumeration value, then this constructor leaves the current thread's <xref:System.Threading.Thread.CurrentPrincipal%2A> property unchanged.  
+ If the `authenticationMode` parameter is the <xref:Microsoft.VisualBasic.ApplicationServices.AuthenticationMode.ApplicationDefined> enumeration value, then this constructor leaves the current thread's <xref:System.Threading.Thread.CurrentPrincipal%2A> property unchanged.  
   
  ]]></format>
         </remarks>

xml/Microsoft.VisualBasic.Compatibility.VB6/BaseControlArray.xml

@@ -495,12 +495,10 @@
 
  The <see cref="T:Microsoft.VisualBasic.Compatibility.VB6.BaseControlArray" /> class is the base class for all control arrays that are used in applications upgraded from Visual Basic 6.0. Because this class is not typically used to create an instance of the class, this <see langword="Protected" /> method is usually not called directly but is instead called by a derived class.  
 
- <block subset="none" type="note">  
-<para>  
+ <block subset="none" type="note"><para>  
  Functions and objects in the <see cref="N:Microsoft.VisualBasic.Compatibility.VB6" /> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to [!INCLUDE[vbprvb](~/includes/vbprvb-md.md)]. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
 
-</para>  
-</block></returns>
+</para></block></returns>
         <remarks>To be added.</remarks>
         <block subset="none" type="overrides">
           <para>When you override <see langword="GetControlInstanceType" /> in a derived class, do not call the <see langword="GetControlInstanceType" /> method of the base class.</para>