Merge pull request #2079 from MicrosoftDocs/master

5/22 AM Publish

Author: Taojunshen

.openpublishing.redirection.json

@@ -690,6 +690,11 @@
             "redirect_url": "/visualstudio/debugger/error-the-microsoft-visual-studio-remote-debugging-monitor-no-permission",
             "redirect_document_id": false
         },
+        {
+            "source_path": "docs/debugger/how-to-debug-with-code-center-premium-source.md",
+            "redirect_url": "/visualstudio/debugger/index",
+            "redirect_document_id": false
+        },
         {
             "source_path": "docs/deployment/installshield-limited-edition.md",
             "redirect_url": "/visualstudio/deployment/deploying-applications-services-and-components",

docs/code-quality/ca1032-implement-standard-exception-constructors.md

@@ -18,6 +18,7 @@ ms.workload:
   - "multiple"
 ---
 # CA1032: Implement standard exception constructors
+
 |||
 |-|-|
 |TypeName|ImplementStandardExceptionConstructors|
@@ -26,28 +27,41 @@ ms.workload:
 |Breaking Change|Non-breaking|
 
 ## Cause
- A type extends <xref:System.Exception?displayProperty=fullName> and does not declare all the required constructors.
 
-## Rule Description
- Exception types must implement the following constructors:
+A type extends <xref:System.Exception?displayProperty=fullName> but doesn't declare all the required constructors.
+
+## Rule description
+
+Exception types must implement the following three constructors:
+
+- public NewException()
+
+- public NewException(string)
 
--   public NewException()
+- public NewException(string, Exception)
 
--   public NewException(string)
+Additionally, if you're running legacy FxCop static code analysis as opposed to [Roslyn-based FxCop analyzers](../code-quality/roslyn-analyzers-overview.md), the absence of a fourth constructor also generates a violation:
 
--   public NewException(string, Exception)
+- protected or private NewException(SerializationInfo, StreamingContext)
 
--   protected or private NewException(SerializationInfo, StreamingContext)
+Failure to provide the full set of constructors can make it difficult to correctly handle exceptions. For example, the constructor that has the signature `NewException(string, Exception)` is used to create exceptions that are caused by other exceptions. Without this constructor, you can't create and throw an instance of your custom exception that contains an inner (nested) exception, which is what managed code should do in such a situation.
 
- Failure to provide the full set of constructors can make it difficult to correctly handle exceptions. For example, the constructor that has the signature `NewException(string, Exception)` is used to create exceptions that are caused by other exceptions. Without this constructor you cannot create and throw an instance of your custom exception that contains an inner (nested) exception, which is what managed code should do in such a situation. The first three exception constructors are public by convention. The fourth constructor is protected in unsealed classes, and private in sealed classes. For more information, see [CA2229: Implement serialization constructors](../code-quality/ca2229-implement-serialization-constructors.md)
+The first three exception constructors are public by convention. The fourth constructor is protected in unsealed classes, and private in sealed classes. For more information, see [CA2229: Implement serialization constructors](../code-quality/ca2229-implement-serialization-constructors.md)
 
-## How to Fix Violations
- To fix a violation of this rule, add the missing constructors to the exception, and make sure that they have the correct accessibility.
+## How to fix violations
 
-## When to Suppress Warnings
- It is safe to suppress a warning from this rule when the violation is caused by using a different access level for the public constructors.
+To fix a violation of this rule, add the missing constructors to the exception, and make sure that they have the correct accessibility.
+
+## When to suppress warnings
+
+It's safe to suppress a warning from this rule when the violation is caused by using a different access level for the public constructors. Additionally, it's okay to suppress the warning for the `NewException(SerializationInfo, StreamingContext)` constructor if you're building a Portable Class Library (PCL).
 
 ## Example
- The following example contains an exception type that violates this rule and an exception type that is correctly implemented.
 
- [!code-csharp[FxCop.Design.ExceptionMultipleCtors#1](../code-quality/codesnippet/CSharp/ca1032-implement-standard-exception-constructors_1.cs)]
+The following example contains an exception type that violates this rule and an exception type that is correctly implemented.
+
+[!code-csharp[FxCop.Design.ExceptionMultipleCtors#1](../code-quality/codesnippet/CSharp/ca1032-implement-standard-exception-constructors_1.cs)]
+
+## See also
+
+[CA2229: Implement serialization constructors](../code-quality/ca2229-implement-serialization-constructors.md)