Merge pull request #4939 from MicrosoftDocs/master637199760928234372

For protected CLA branch, push strategy should use PR and merge to target branch method to work around git push error

Author: ghogen

.openpublishing.redirection.json

@@ -11615,10 +11615,15 @@
       "redirect_url": "/visualstudio/subscriptions",
       "redirect_document_id": false
     },
+    {
+      "source_path": "docs/code-quality/how-to-enable-and-disable-full-solution-analysis-for-managed-code.md",
+      "redirect_url": "/visualstudio/code-quality/configure-live-code-analysis-scope-managed-code",
+      "redirect_document_id": true
+    },
     {
       "source_path": "docs/azure/cognitive-services-connected-services.yml",
       "redirect_url": "/visualstudio/azure",
       "redirect_document_id": false
     }
   ]
-}
+}

docs/code-quality/automatic-feature-suspension.md

@@ -3,9 +3,12 @@ title: Automatic feature suspension
 ms.date: 11/04/2016
 ms.topic: conceptual
 helpviewer_keywords:
-- full solution analysis
-- performance
-- low-memory
+  - "live code analysis"
+  - "background analysis"
+  - "analysis scope"
+  - "full solution analysis"
+  - "performance"
+  - "low-memory"
 ms.assetid: 572c15aa-1fd0-468c-b6be-9fa50e170914
 author: TerryGLee
 ms.author: tglee
@@ -23,7 +26,7 @@ When Visual Studio detects a low memory condition, it automatically suspends cer
 
 In a low memory condition, the following actions take place:
 
-- Full solution analysis for Visual C# and Visual Basic is disabled.
+- Live code analysis for Visual C# and Visual Basic is reduced to minimal scope.
 
 - [Garbage Collection](/dotnet/standard/garbage-collection/index) (GC) low-latency mode for Visual C# and Visual Basic is disabled.
 
@@ -33,9 +36,9 @@ In a low memory condition, the following actions take place:
 
 For tips and tricks on how to improve Visual Studio performance when dealing with large solutions or low-memory conditions, see [Performance considerations for large solutions](https://github.com/dotnet/roslyn/wiki/Performance-considerations-for-large-solutions).
 
-## Full solution analysis suspended
+## Live code analysis is reduced to minimal scope
 
-By default, full solution analysis is enabled for Visual Basic and disabled for Visual C#. However, in a low memory condition, full solution analysis is automatically disabled for both Visual Basic and Visual C#, regardless of their settings in the Options dialog box. However, you can re-enable full solution analysis by choosing the **Re-enable** button in the info bar when it appears, by selecting the **Enable full solution analysis** check box in the Options dialog, or by restarting Visual Studio. The Options dialog box always shows the current full solution analysis settings. For more information, see [How to: Enable and Disable Full Solution Analysis](../code-quality/how-to-enable-and-disable-full-solution-analysis-for-managed-code.md).
+By default, live code analysis executes for open documents and projects. You can customize this analysis scope to be reduced to current document or increased to entire solution. For more information, see [How to: Configure live code analysis scope for managed code](./configure-live-code-analysis-scope-managed-code.md). In a low memory condition, Visual Studio forces the live analysis scope to be reduced to current document. However, you can re-enable your preferred analysis scope by choosing the **Re-enable** button in the info bar when it appears or by restarting Visual Studio. The Options dialog box always shows the current live code analysis scope settings.
 
 ## GC low-latency disabled
 
@@ -58,6 +61,6 @@ In addition, caches used for internal Visual Studio operations are also cleared.
 
 ## See also
 
-- [How to: Enable and Disable Full Solution Analysis](../code-quality/how-to-enable-and-disable-full-solution-analysis-for-managed-code.md)
+- [How to: Configure live code analysis scope for managed code](./configure-live-code-analysis-scope-managed-code.md)
 - [Fundamentals of Garbage Collection](/dotnet/standard/garbage-collection/fundamentals)
 - [Performance considerations for large solutions](https://github.com/dotnet/roslyn/wiki/Performance-considerations-for-large-solutions)

docs/code-quality/configure-live-code-analysis-scope-managed-code.md

@@ -0,0 +1,74 @@
+---
+title: "Configure live code analysis scope for managed code"
+ms.date: 03/23/2018
+ms.topic: "conceptual"
+helpviewer_keywords:
+  - "live code analysis"
+  - "background analysis"
+  - "analysis scope"
+  - "full solution analysis"
+author: jillre
+ms.author: jillfra
+manager: jillfra
+ms.workload:
+  - "dotnet"
+---
+# How to: Configure live code analysis scope for managed code
+
+## What is "Live code analysis" for managed code?
+Visual Studio executes a bunch of live code analyses, also referred to as *background analysis*, while you are editing source files in the editor. Some of it is required minimal analysis for an acceptable Visual Studio IDE editing experience. Some of it is for improved responsiveness for IDE features. While some of it is to enable additional IDE functionality, such as diagnostics and code fixes from Roslyn analyzers. Based on the functionality, these analyses can be grouped as follows:
+
+- **Background computation of diagnostics**: Analysis to compute errors, warnings, and suggestions in source files. These diagnostics show up as entries in the error list and as squiggles in the editor. They can be classified into two categories:
+    - C# and Visual Basic compiler diagnostics
+    - Roslyn analyzer diagnostics, which includes:
+
+        - Built-in IDE analyzers for code style suggestions and
+        - Third party analyzer packages [installed](./install-roslyn-analyzers.md) for projects in the current solution.
+
+- **Other background analyses**: Analysis to improve the responsiveness and Visual Studio interaction for IDE features. Some examples of such analyses are:
+    - Background parsing of open files.
+    - Background compilation of projects with open files to realize symbols for improved responsiveness of certain IDE features.
+    - Building syntax and symbol caches.
+    - Detecting designer association for source files, such as forms, controls, etc.
+
+## Default analysis scope
+
+By default, live code analysis for background computation of diagnostics executes for all the files that are _opened_ in Visual Studio. Few of the _other background analyses_ mentioned above execute for all the projects, which have at least one open file. While few background analyses execute for the entire solution.
+
+## Custom analysis scope
+
+The default scope of each background analysis has been tuned for the optimal user experience, functionality, and performance for majority of customer scenarios and solutions. However, there are cases where customers may want to customize this scope to decrease or increase the background analysis. For example:
+
+- Power save mode: If users are running on laptop battery, they may want to minimize the power consumption for longer battery life. In this scenario, they would want to minimize background analysis.
+- On-demand code analysis: If users prefer turning off live analyzer execution and manually running code analysis on-demand, they would want to minimize background analysis. See [How to: Manually run code analysis on-demand](./how-to-run-code-analysis-manually-for-managed-code.md).
+- Full solution analysis: If users want to always see all diagnostics in all files in the solution, regardless of whether they are open in the editor or not. In this scenario, they would want to maximize background analysis scope to entire solution.
+
+Starting in Visual Studio 2019 version 16.5, users can explicitly customize the scope of all live code analysis, including diagnostics computation, for C# and Visual Basic projects. Available analysis scopes are:
+
+- **Current document**: Minimizes the live code analysis scope to only execute for the current or visible file in the editor.
+- **Open documents**: Default live code analysis scope, as described in the above section.
+- **Entire solution**: Maximizes the live code analysis scope to execute for all files and projects in the entire solution.
+
+You can choose one of the above custom analysis scopes in Tools Options dialog by following the below steps:
+
+1. To open the **Options** dialog box, on the menu bar in Visual Studio choose **Tools** > **Options**.
+
+2. In the **Options** dialog box, choose **Text Editor** > **C#** or **Basic** > **Advanced**.
+
+3. Select the desired **Background analysis scope** to customize the analysis scope. Choose **OK** when you're done.
+
+![Analysis scope.](./media/background-analysis-scope.png)
+
+> [!NOTE]
+> Prior to Visual Studio 2019 version 16.5, users can customize the analysis scope for diagnostics computation to entire solution using the **Enable full solution analysis** check box from **Tools** > **Options** > **Text Editor** > **C#** or **Basic** > **Advanced** tab. There is no support to minimize the background analysis scope in prior Visual Studio versions.
+
+## Automatically minimize live code analysis scope
+
+If Visual Studio detects that 200 MB or less of system memory is available to it, it automatically minimizes the live code analysis scope to "Current Document". If this occurs, an alert appears informing you that Visual Studio has disabled some features. A button lets you switch back to the prior analysis scope if you want.
+
+![Alert text minimizing analysis scope](./media/fsa_alert.png)
+
+## See also
+
+- [Automatic feature suspension](./automatic-feature-suspension.md)
+- [Power save mode feature request](https://github.com/dotnet/roslyn/issues/38429)

docs/code-quality/disable-code-analysis.md

@@ -19,17 +19,13 @@ This page helps you disable code analysis in Visual Studio. There are limitation
 
   .NET Core and .NET Standard projects have options on their Code Analysis properties page that let you turn off code analysis from analyzers installed as a NuGet package. For more information, see [.NET Core and .NET Standard projects](#net-core-and-net-standard-projects). To turn off source code analysis for .NET Framework projects, see [.NET Framework projects](#net-framework-projects).
 
-- NuGet analyzer package versus VSIX or built-in analyzers
-
-  Currently, you cannot disable live code analysis for the built-in analyzers, for example, rule ID IDE0067. Similarly, you cannot disable live code analysis for analyzers that were installed as part of a Visual Studio extension (VSIX). To suppress errors and warnings from built-in and VSIX-based analyzers, choose **Analyze** > **Build and Suppress Active Issues** on the menu bar. You *can* disable live and built-time analysis for analyzers installed as part of a NuGet package.
-
 - Source analysis versus legacy analysis
 
   This topic applies to source code analysis and not to legacy (binary) analysis. For information about disabling legacy analysis, see [How to: Enable and disable legacy code analysis](how-to-enable-and-disable-automatic-code-analysis-for-managed-code.md).
 
 ## .NET Core and .NET Standard projects
 
-Starting in Visual Studio 2019 version 16.3, there are two checkboxes available in the Code Analysis properties page that let you control whether NuGet-based analyzers run at build time and design time. These options are project specific.
+Starting in Visual Studio 2019 version 16.3, there are two checkboxes available in the Code Analysis properties page that let you control whether analyzers run at build time and design time. These options are project-specific.
 
 ![Enable or disable live code analysis or on build in Visual Studio](media/run-on-build-run-live-analysis.png)
 
@@ -39,17 +35,17 @@ To open this page, right-click on the project node in **Solution Explorer** and
 - To disable live source analysis, uncheck the **Run on live analysis** option.
 
 > [!NOTE]
-> Built-in and VSIX-based analyzers will continue to provide live analysis of your code, even if **Run on live analysis** is unchecked. If you want to suppress errors and warnings from these analyzers, choose **Analyze** > **Build and Suppress Active Issues** on the menu bar.
+> Starting in Visual Studio 2019 version 16.5, if you prefer the on-demand code analysis execution workflow, you can disable analyzer execution during live analysis and/or build and manually trigger code analysis once on a project or a solution on demand. For information about running code analysis manually, see [How to: Run Code Analysis Manually for Managed Code](how-to-run-code-analysis-manually-for-managed-code.md).  
 
 ## .NET Framework projects
 
-To turn off source code analysis for analyzers installed as part of a NuGet package, add one or more of the following MSBuild properties to the [project file](../ide/solutions-and-projects-in-visual-studio.md#project-file).
+To turn off source code analysis for analyzers, add one or more of the following MSBuild properties to the [project file](../ide/solutions-and-projects-in-visual-studio.md#project-file).
 
 | MSBuild property | Description | Default |
 | - | - | - |
-| `RunAnalyzersDuringBuild` | Controls whether NuGet-based analyzers run at build time. | `true` |
-| `RunAnalyzersDuringLiveAnalysis` | Controls whether NuGet-based analyzers analyze code live at design time. | `true` |
-| `RunAnalyzers` | Disables NuGet-based analyzers at both build and design time. This property takes precedence over `RunAnalyzersDuringBuild` and `RunAnalyzersDuringLiveAnalysis`. | `true` |
+| `RunAnalyzersDuringBuild` | Controls whether analyzers run at build time. | `true` |
+| `RunAnalyzersDuringLiveAnalysis` | Controls whether analyzers analyze code live at design time. | `true` |
+| `RunAnalyzers` | Disables analyzers at both build and design time. This property takes precedence over `RunAnalyzersDuringBuild` and `RunAnalyzersDuringLiveAnalysis`. | `true` |
 
 Examples:
 
@@ -67,7 +63,7 @@ Examples:
 
 You cannot turn off [source analysis](roslyn-analyzers-overview.md) in Visual Studio 2017. If you want to clear analyzer errors from the Error List, you can suppress all the current violations by choosing **Analyze** > **Run Code Analysis and Suppress Active Issues** on the menu bar. For more information, see [Suppress violations](use-roslyn-analyzers.md#suppress-violations).
 
-Starting in Visual Studio 2019 version 16.3, you can turn off NuGet-based source code analysis. Consider upgrading to Visual Studio 2019.
+Starting in Visual Studio 2019 version 16.3, you can turn off source code analysis or execute it on demand. Consider upgrading to Visual Studio 2019.
 
 ## Legacy analysis
 

docs/code-quality/fxcop-analyzers-faq.md

@@ -25,11 +25,11 @@ FxCop analyzers are based on the .NET Compiler Platform ("Roslyn"). You [install
 
 ## Does the Run Code Analysis command run FxCop analyzers?
 
-No. When you select **Analyze** > **Run Code Analysis**, it executes legacy analysis. **Run Code Analysis** has no effect on Roslyn-based analyzers, including the Roslyn-based FxCop analyzers.
+Prior to Visual Studio 2019 16.5 release, when you select **Analyze** > **Run Code Analysis**, it executes legacy analysis. Starting Visual Studio 2019 16.5, **Run Code Analysis** menu option executes Roslyn-based analyzers for the selected project or solution. If you have installed Roslyn-based FxCop analyzers, they would also be executed. For more information, see [How to: Run Code Analysis Manually for Managed Code](how-to-run-code-analysis-manually-for-managed-code.md).
 
 ## Does the RunCodeAnalysis msbuild project property run analyzers?
 
-No. The **RunCodeAnalysis** property in a project file (for example, *.csproj*) is only used to execute legacy FxCop. It runs a post-build msbuild task that invokes **FxCopCmd.exe**. This is equivalent to selecting **Analyze** > **Run Code Analysis** in Visual Studio.
+No. The **RunCodeAnalysis** property in a project file (for example, *.csproj*) is only used to execute legacy FxCop. It runs a post-build msbuild task that invokes **FxCopCmd.exe**.
 
 ## So how do I run FxCop analyzers then?
 

docs/code-quality/how-to-configure-code-analysis-for-a-managed-code-project.md

@@ -39,7 +39,7 @@ In Visual Studio, you can choose from a list of code analysis [rule sets](../cod
 
 ::: moniker range=">=vs-2019"
 
-3. To run code analysis every time the project is built using the selected configuration, select **Run on build** in the **Binary analyzers** section. You can also run code analysis manually by selecting **Analyze** > **Run Code Analysis** > **Run Code Analysis on \<projectname>**.
+3. To run code analysis every time the project is built using the selected configuration, select **Run on build** in the **Binary analyzers** section. You can also run legacy code analysis manually, see [How to: Run Legacy Code Analysis Manually for Managed Code](how-to-run-legacy-code-analysis-manually-for-managed-code.md) for more details.
 
 ::: moniker-end