Merge pull request #1723 from gewarren/gewarren-rule-sets

Updated rule sets topics

Author: GitHubber17

.openpublishing.redirection.json

@@ -97,6 +97,11 @@
             "redirect_url": "/visualstudio/code-quality/code-analysis-for-c-cpp-overview",
             "redirect_document_id": false
         },
+        {
+            "source_path": "docs/code-quality/code-analysis-rule-set-reference.md",
+            "redirect_url": "/visualstudio/code-quality/managed-minimun-rules-rule-set-for-managed-code",
+            "redirect_document_id": false
+        },
         {
             "source_path": "docs/code-quality/creating-and-using-code-analysis-check-in-policies.md",
             "redirect_url": "/visualstudio/code-quality/how-to-create-or-update-standard-code-analysis-check-in-policies",

docs/code-quality/TOC.md

@@ -24,10 +24,9 @@
 ### [Anonymous Methods and Code Analysis](anonymous-methods-and-code-analysis.md)
 ### [Create a Work Item for a Managed Code Defect](how-to-create-a-work-item-for-a-managed-code-defect.md)
 ## Code Analysis for C/C++
-### [Use Rule Sets to Specify the C++ Rules to Run](using-rule-sets-to-specify-the-cpp-rules-to-run.md)
 ### [Use the C++ Core Guidelines checkers](using-the-cpp-core-guidelines-checkers.md)
-### [Set Code Analysis Properties for C/C++ Projects](how-to-set-code-analysis-properties-for-c-cpp-projects.md)
-### [Use SAL Annotations to Reduce C/C++ Code Defects](using-sal-annotations-to-reduce-c-cpp-code-defects.md)
+### [Set Code Analysis Properties](how-to-set-code-analysis-properties-for-c-cpp-projects.md)
+### [Use SAL Annotations to Reduce Code Defects](using-sal-annotations-to-reduce-c-cpp-code-defects.md)
 #### [Understand SAL](understanding-sal.md)
 #### [Annotate Function Parameters and Return Values](annotating-function-parameters-and-return-values.md)
 #### [Annotate Function Behavior](annotating-function-behavior.md)
@@ -38,27 +37,14 @@
 #### [Best Practices and Examples (SAL)](best-practices-and-examples-sal.md)
 ### [Specify Additional Code Information by Using __analysis_assume](how-to-specify-additional-code-information-by-using-analysis-assume.md)
 ## [Use Rule Sets to Group Code Analysis Rules](using-rule-sets-to-group-code-analysis-rules.md)
-### [Configure Code Analysis for a Managed Code Project](how-to-configure-code-analysis-for-a-managed-code-project.md)
-### [Configure Code Analysis for an ASP.NET Web Application](how-to-configure-code-analysis-for-an-aspnet-web-application.md)
-### [Synchronize Code Project Rule Sets with Team Project Check-in Policy](how-to-synchronize-code-project-rule-sets-with-team-project-check-in-policy.md)
-### [Specify Managed Code Rule Sets for Multiple Projects in a Solution](how-to-specify-managed-code-rule-sets-for-multiple-projects-in-a-solution.md)
-### [Create Custom Code Analysis Rule Sets](creating-custom-code-analysis-rule-sets.md)
+### [Use Rule Sets for Managed Code](how-to-configure-code-analysis-for-a-managed-code-project.md)
+#### [Configure Code Analysis for an ASP.NET Web Application](how-to-configure-code-analysis-for-an-aspnet-web-application.md)
+#### [Specify Rule Sets for Multiple Projects](how-to-specify-managed-code-rule-sets-for-multiple-projects-in-a-solution.md)
+### [Use Rule Sets for C++ Code](using-rule-sets-to-specify-the-cpp-rules-to-run.md)
+### [Synchronize Project Rule Sets with Team Project Check-in Policy](how-to-synchronize-code-project-rule-sets-with-team-project-check-in-policy.md)
+### [Create Custom Rule Sets](creating-custom-code-analysis-rule-sets.md)
 #### [Create a Custom Rule Set](how-to-create-a-custom-rule-set.md)
-#### [Use the Code Analysis Rule Set Editor](working-in-the-code-analysis-rule-set-editor.md)
-### [Code analysis rule set reference](code-analysis-rule-set-reference.md)
-#### [All Rules rule set](all-rules-rule-set.md)
-#### [Basic Correctness Rules rule set for managed code](basic-correctness-rules-rule-set-for-managed-code.md)
-#### [Basic Design Guideline Rules rule set for managed code](basic-design-guideline-rules-rule-set-for-managed-code.md)
-#### [Extended Correctness Rules rule set for managed code](extended-correctness-rules-rule-set-for-managed-code.md)
-#### [Extended Design Guidelines Rules rule set for managed code](extended-design-guidelines-rules-rule-set-for-managed-code.md)
-#### [Globalization Rules rule set for managed code](globalization-rules-rule-set-for-managed-code.md)
-#### [Managed Minimun Rules rule set for managed code](managed-minimun-rules-rule-set-for-managed-code.md)
-#### [Managed Recommended Rules rule set for managed code](managed-recommended-rules-rule-set-for-managed-code.md)
-#### [Mixed Minimum Rules rule set](mixed-minimum-rules-rule-set.md)
-#### [Mixed Recommended Rules rule set](mixed-recommended-rules-rule-set.md)
-#### [Native Minimum Rules rule set](native-minimum-rules-rule-set.md)
-#### [Native Recommended Rules rule set](native-recommended-rules-rule-set.md)
-#### [Security Rules rule set for managed code](security-rules-rule-set-for-managed-code.md)
+#### [Use the Rule Set Editor](working-in-the-code-analysis-rule-set-editor.md)
 ## [Create Code Analysis Check-in Policies](how-to-create-or-update-standard-code-analysis-check-in-policies.md)
 ### [Implement Custom Code Analysis Check-in Policies for Managed Code](implementing-custom-code-analysis-check-in-policies-for-managed-code.md)
 ### [Enforce Maintainable Code](how-to-enforce-maintainable-code-with-a-code-analysis-check-in-policy.md)
@@ -67,6 +53,20 @@
 ### [Generate Code Metrics Data](how-to-generate-code-metrics-data.md)
 ### [Work with Code Metrics Data](working-with-code-metrics-data.md)
 # Reference
+## Rule sets
+### [All Rules rule set](all-rules-rule-set.md)
+### [Basic Correctness Rules rule set for managed code](basic-correctness-rules-rule-set-for-managed-code.md)
+### [Basic Design Guideline Rules rule set for managed code](basic-design-guideline-rules-rule-set-for-managed-code.md)
+### [Extended Correctness Rules rule set for managed code](extended-correctness-rules-rule-set-for-managed-code.md)
+### [Extended Design Guidelines Rules rule set for managed code](extended-design-guidelines-rules-rule-set-for-managed-code.md)
+### [Globalization Rules rule set for managed code](globalization-rules-rule-set-for-managed-code.md)
+### [Managed Minimun Rules rule set for managed code](managed-minimun-rules-rule-set-for-managed-code.md)
+### [Managed Recommended Rules rule set for managed code](managed-recommended-rules-rule-set-for-managed-code.md)
+### [Mixed Minimum Rules rule set](mixed-minimum-rules-rule-set.md)
+### [Mixed Recommended Rules rule set](mixed-recommended-rules-rule-set.md)
+### [Native Minimum Rules rule set](native-minimum-rules-rule-set.md)
+### [Native Recommended Rules rule set](native-recommended-rules-rule-set.md)
+### [Security Rules rule set for managed code](security-rules-rule-set-for-managed-code.md)
 ## [Code Analysis for Managed Code Warnings](code-analysis-for-managed-code-warnings.md)
 ### [Code Analysis Warnings for Managed Code by CheckId](code-analysis-warnings-for-managed-code-by-checkid.md)
 ### [Cryptography Warnings](cryptography-warnings.md)

docs/code-quality/code-analysis-rule-set-reference.md

@@ -1,56 +1,52 @@
 ---
-title: "FxCopCmd Errors | Microsoft Docs"
-ms.custom: ""
+title: "FxCopCmd errors | Microsoft Docs"
 ms.date: "10/19/2016"
-ms.reviewer: ""
-ms.suite: ""
-ms.technology: 
-  - "vs-ide-code-analysis"
-ms.tgt_pltfrm: ""
+ms.technology: vs-ide-code-analysis
 ms.topic: "article"
-helpviewer_keywords: 
+helpviewer_keywords:
   - "FxCopCmd errors"
 ms.assetid: bb614ed0-1b7c-4b56-99ae-da50ef6cfef9
-caps.latest.revision: 12
 ms.author: "gewarren"
 author: "gewarren"
 manager: ghogen
-ms.workload: 
+ms.workload:
   - "multiple"
 ---
-# FxCopCmd Errors
-FxCopCmd does not consider all errors to be fatal. If FxCopCmd has sufficient information to perform a partial analysis, it performs the analysis and reports errors that occurred. The error code, which is a 32-bit integer, contains a bitwise combination of numeric values that correspond to errors.  
-  
- The following table describes the error codes returned by FxCopCmd:  
-  
-|Error|Numeric value|  
-|-----------|-------------------|  
-|No errors|0x0|  
-|Analysis error|0x1|  
-|Rule exceptions|0x2|  
-|Project load error|0x4|  
-|Assembly load error|0x8|  
-|Rule library load error|0x10|  
-|Import report load error|0x20|  
-|Output error|0x40|  
-|Command line switch error|0x80|  
-|Initialization error|0x100|  
-|Assembly references error|0x200|  
-|BuildBreakingMessage|0x400|  
-|Unknown error|0x1000000|  
-  
- The Analysis error is returned for fatal errors. It indicates that the analysis could not be completed. When applicable, the error code also contains the underlying cause of the fatal error. The following conditions generate fatal errors:  
-  
--   The analysis could not be performed caused by insufficient input.  
-  
--   The analysis threw an exception that is not handled by FxCopCmd.  
-  
--   The specified project file could not be found or is corrupted.  
-  
--   The output option was not specified or the file could not be written.  
-  
-    > [!NOTE]
-    >  The FxCopCmd return code "Assembly references error" 0x200 by itself is a warning rather than an error. This return code indicates that missing indirect references were found but that FxCopCmd was able to handle them. It is a warning that there is a possibility that some analysis results might have been compromised. Consider "Assembly references error" return code as an error when it is combined with any other return code.  
-  
-## See Also  
- [Code Analysis Application Errors](../code-quality/code-analysis-application-errors.md)
+# FxCopCmd tool errors
+
+FxCopCmd does not consider all errors to be fatal. If FxCopCmd has sufficient information to perform a partial analysis, it performs the analysis and reports errors that occurred. The error code, which is a 32-bit integer, contains a bitwise combination of numeric values that correspond to errors.
+
+The following table describes the error codes returned by FxCopCmd:
+
+|Error|Numeric value|
+|-----------|-------------------|
+|No errors|0x0|
+|Analysis error|0x1|
+|Rule exceptions|0x2|
+|Project load error|0x4|
+|Assembly load error|0x8|
+|Rule library load error|0x10|
+|Import report load error|0x20|
+|Output error|0x40|
+|Command line switch error|0x80|
+|Initialization error|0x100|
+|Assembly references error|0x200|
+|BuildBreakingMessage|0x400|
+|Unknown error|0x1000000|
+
+**Analysis error** is returned for fatal errors. It indicates that the analysis could not be completed. When applicable, the error code also contains the underlying cause of the fatal error. The following conditions generate fatal errors:
+
+- The analysis could not be performed because of insufficient input.
+
+- The analysis threw an exception that is not handled by FxCopCmd.
+
+- The specified project file could not be found or is corrupted.
+
+- The output option was not specified or the file could not be written.
+
+> [!NOTE]
+> The FxCopCmd return code **Assembly references error** 0x200 by itself is a warning rather than an error. This return code indicates that there are missing indirect references, but that FxCopCmd was able to handle them. The warning means there's a possibility that some analysis results might have been compromised. Treat **Assembly references error** as an error when it is combined with any other return code.
+
+## See also
+
+- [Code Analysis Application Errors](../code-quality/code-analysis-application-errors.md)