Merge pull request #2952 from MicrosoftDocs/master

Taojunshen · web-flow · commit b9a32c3d94b1 · 2018-09-19T01:47:17.000+08:00
9/18 AM Publish
diff --git a/docs/code-quality/fxcop-analyzers-faq.md b/docs/code-quality/fxcop-analyzers-faq.md
@@ -0,0 +1,44 @@
+---
+title: FxCop code analysis and FxCop analyzers
+ms.date: 09/06/2018
+ms.prod: visual-studio-dev15
+ms.technology: vs-ide-code-analysis
+ms.topic: overview
+helpviewer_keywords:
+  - "code analysis FAQ"
+author: gewarren
+ms.author: gewarren
+manager: douge
+ms.workload:
+  - "dotnet"
+---
+# Frequently asked questions about FxCop and FxCop analyzers
+
+It can be a little confusing to understand the differences between legacy FxCop and FxCop analyzers. This article aims to address some of questions you might have.
+
+## What's the difference between legacy FxCop and FxCop analyzers?
+
+Legacy FxCop runs post-build analysis on a compiled assembly. It runs as a separate executable called **FxCopCmd.exe**. FxCopCmd.exe loads the compiled assembly, runs code analysis, and then reports the results (or *diagnostics*).
+
+FxCop analyzers are based on the .NET Compiler Platform ("Roslyn"). You [install them as a NuGet package](install-fxcop-analyzers.md#to-install-fxcop-analyzers-as-a-nuget-package) that's referenced by the project or solution. FxCop analyzers run source-code based analysis during compiler execution. FxCop analyzers are hosted within the compiler process, either **csc.exe** or **vbc.exe**, and run analysis when the project is built. Analyzer results are reported along with compiler results.
+
+> [!NOTE]
+> You can also [install FxCop analyzers as a Visual Studio extension](install-fxcop-analyzers.md#to-install-fxcop-analyzers-as-a-vsix). In this case, the analyzers execute as you type in the code editor, but they don't execute at build time. If you want to run FxCop analyzers as part of continuous integration (CI), install them as a NuGet package instead.
+
+## Does the Run Code Analysis command run FxCop analyzers?
+
+No. When you select **Analyze** > **Run Code Analysis** in Visual Studio 2017, it executes static code analysis or legacy FxCop. **Run Code Analysis** has no effect on Roslyn-based analyzers, including the Roslyn-based FxCop analyzers.
+
+## 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.
+
+## So how do I run FxCop analyzers then?
+
+To run FxCop analyzers, first [install the NuGet package](install-fxcop-analyzers.md) for them. Then build your project or solution from Visual Studio or using msbuild. The warnings and errors that the FxCop analyzers generate will appear in the **Error List** or the command window.
+
+## See also
+
+- [Overview of .NET Compiler Platform analyzers](roslyn-analyzers-overview.md)
+- [Get started with analyzers](fxcop-analyzers.yml)
+- [Install FxCop analyzers](install-fxcop-analyzers.md)
diff --git a/docs/code-quality/fxcop-analyzers.yml b/docs/code-quality/fxcop-analyzers.yml
@@ -21,6 +21,10 @@ abstract:
       src: https://docs.microsoft.com/media/illustrations/bcs-partner-advanced-management-settings-8.svg
     title:
 sections:
+- title: Frequently asked questions
+  items:
+  - html: Get answers to some <a href="fxcop-analyzers-faq.md">frequently asked questions</a> about the differences between FxCop and analyzers.
+
 - title: If you're new to code analysis...
   items:
   - type: list
diff --git a/docs/code-quality/toc.yml b/docs/code-quality/toc.yml
@@ -28,6 +28,8 @@
   items:
   - name: Code analysis for managed code
     items:
+    - name: FAQ for FxCop analyzers
+      href: fxcop-analyzers-faq.md
     - name: Migrate from FxCop
       href: fxcop-analyzers.yml
       items:
diff --git a/docs/extensibility/visual-cpp-project-extensibility.md b/docs/extensibility/visual-cpp-project-extensibility.md
@@ -13,7 +13,7 @@ ms.workload: ["vssdk"]
 ---
 # Visual Studio C++ Project system extensibility and toolset integration
 
-The *Visual C++ Project system* is used by .vcxproj files. It's based on the [Visual Studio Common Project System (CPS)](https://github.com/Microsoft/VSProjectSystem/blob/master/doc/Index.md) and provides additional, C++ specific extensibility points for easy integration of new toolsets, build architectures and target platforms. 
+The *Visual C++ Project system* is used for .vcxproj files. It's based on the [Visual Studio Common Project System (CPS)](https://github.com/Microsoft/VSProjectSystem/blob/master/doc/Index.md) and provides additional, C++ specific extensibility points for easy integration of new toolsets, build architectures and target platforms. 
 
 ## C++ MSBuild targets structure
 
@@ -220,13 +220,13 @@ If you look at the targets, such as `_ClCompile`, you'll see they don't do anyth
 </Target>
 ```
 
-`ClCompile` and other build tool-specific targets are defined as empty targets in Microsoft.CppBuild.targets:
+`ClCompile` and other build tool-specific targets are defined as empty targets in *Microsoft.CppBuild.targets*:
 
 ```xml
 <Target Name="ClCompile"/>
 ```
 
-Because the `ClCompile` target is defined as an empty target in *Microsoft.CppBuild.targets*, unless it is overridden by a toolset, no real build action is performed. The toolset targets can override the `ClCompile` target, that is, they can contain another `ClCompile` definition after importing *Microsoft.CppBuild.targets*: 
+Because the `ClCompile` target is empty, unless it is overridden by a toolset, no real build action is performed. The toolset targets can override the `ClCompile` target, that is, they can contain another `ClCompile` definition after importing *Microsoft.CppBuild.targets*: 
 
 ```xml
 <Target Name="ClCompile"
@@ -236,7 +236,7 @@ Because the `ClCompile` target is defined as an empty target in *Microsoft.CppBu
 </Target>
 ```
 
-Despite the name `ClCompile`, which was created before Visual Studio implemented cross-platform support, the `ClCompile` target doesn't have to call CL.exe. It can also call Clang, gcc, or other compilers by using appropriate MSBuild tasks.
+Despite its name, which was created before Visual Studio implemented cross-platform support, the `ClCompile` target doesn't have to call CL.exe. It can also call Clang, gcc, or other compilers by using appropriate MSBuild tasks.
 
 The `ClCompile` target should not have any dependencies except the `SelectClCompile` target, which is required for the single file compile command to work in the IDE.
 
@@ -282,7 +282,7 @@ If you need to create a new task for a build tool, you can choose from the follo
 
 1. If you want better task performance or just need more complex functionality, use the regular MSBuild [task writing](../msbuild/task-writing.md) process.
 
-   If not all inputs and outputs of the tool are listed on the tool command line, as in the `CL`, `MIDL`, and `RC` cases, and if you want automatic input and output file tracking and .tlog file creation, derive your task from `TrackedVCToolTask`.
+   If not all inputs and outputs of the tool are listed on the tool command line, as in the `CL`, `MIDL`, and `RC` cases, and if you want automatic input and output file tracking and .tlog file creation, derive your task from the `Microsoft.Build.CPPTasks.TrackedVCToolTask` class. At present, while there is documentation for the base [ToolTask](/dotnet/api/microsoft.build.utilities.tooltask) class, there are no examples or documentation for the details of the `TrackedVCToolTask` class. If this would be of particular interest, add your voice to a request on [developercommunity.visualstudio.com](https://developercommunity.visualstudio.com/spaces/62/index.html).
 
 ## Incremental builds and up-to-date checks
 
@@ -421,7 +421,7 @@ To use `Task.HostObject` to get the unsaved content of source files, the targets
 @="{83046B3F-8984-444B-A5D2-8029DEE2DB70}"
 ```
 
-## Project extensibility in the Visual Studio IDE
+## Visual C++ project extensibility in the Visual Studio IDE
 
 The Visual C++ project system is based on the [VS Project System](https://github.com/Microsoft/VSProjectSystem/blob/master/doc/Index.md), and uses its extensibility points. However, the project hierarchy implementation is specific to Visual C++ and not based on CPS, so hierarchy extensibility is limited to project items.
 
@@ -650,6 +650,6 @@ For information on how to create VSIX files, see [Shipping Visual Studio Extensi
 
 The Microsoft Build System ([MSBuild](../msbuild/msbuild.md)) provides the build engine and the extensible XML-based format for project files. You should be familiar with basic [MSBuild concepts](../msbuild/msbuild-concepts.md) and with how [MSBuild for Visual C++](/cpp/build/msbuild-visual-cpp-overview) works in order to extend the Visual C++ project system.
 
-The Managed Extensibility Framework ([MEF](/dotnet/framework/mef/)) provides the extension APIs that are used by CPS and the Visual C++ project system. For an overview of how MEF is used by CPS, see [MEF](https://github.com/Microsoft/VSProjectSystem/blob/master/doc/overview/mef.md).
+The Managed Extensibility Framework ([MEF](/dotnet/framework/mef/)) provides the extension APIs that are used by CPS and the Visual C++ project system. For an overview of how MEF is used by CPS, see [CPS and MEF](https://github.com/Microsoft/VSProjectSystem/blob/master/doc/overview/mef.md#cps-and-mef) in the [VSProjectSystem overview of MEF](https://github.com/Microsoft/VSProjectSystem/blob/master/doc/overview/mef.md).
 
 You can customize the existing build system to add build steps or new file types. For more information, see [MSBuild (Visual C++) Overview](/cpp/build/msbuild-visual-cpp-overview) and [Working with project properties](/cpp/ide/working-with-project-properties).
diff --git a/docs/ide/quickstart-aspnet-core.experimental.md b/docs/ide/quickstart-aspnet-core.experimental.md
@@ -16,7 +16,7 @@ ms.workload:
   - "aspnet"
   - "dotnetcore"
 experimental: false
-experiment_id: "eb51ee6c-71a8-45"
+experiment_id: "bef9e21b-00d0-4b"
 ---
 # Quickstart: Use Visual Studio to create your first ASP.NET Core web app
 
diff --git a/docs/ide/quickstart-aspnet-core.md b/docs/ide/quickstart-aspnet-core.md
@@ -16,7 +16,7 @@ ms.workload:
   - "aspnet"
   - "dotnetcore"
 experimental: true
-experiment_id: "eb51ee6c-71a8-45"
+experiment_id: "bef9e21b-00d0-4b"
 ---
 # Quickstart: Use Visual Studio to create your first ASP.NET Core web app
 
diff --git a/docs/install/create-an-offline-installation-of-visual-studio.md b/docs/install/create-an-offline-installation-of-visual-studio.md
@@ -1,5 +1,5 @@
 ---
-title: "Create an Offline Installation of Visual Studio"
+title: "Create an offline installation of Visual Studio"
 description: "Learn how to install Visual Studio offline when you have an unreliable internet connection or low bandwidth."
 ms.custom: ""
 ms.date: 08/28/2018
diff --git a/docs/test/create-unit-tests-menu.md b/docs/test/create-unit-tests-menu.md
@@ -1,16 +1,16 @@
 ---
-title: "Create unit test method stubs in Visual Studio"
+title: Create unit test method stubs
 ms.date: 05/02/2017
 ms.prod: visual-studio-dev15
 ms.technology: vs-ide-test
 ms.topic: conceptual
 helpviewer_keywords:
   - "unit testing, create unit tests"
+author: gewarren
 ms.author: gewarren
 manager: douge
 ms.workload:
   - "multiple"
-author: gewarren
 ---
 # Create unit test method stubs with the Create Unit Tests command
 
diff --git a/docs/test/intellitest-manual/getting-started.md b/docs/test/intellitest-manual/getting-started.md
@@ -1,14 +1,14 @@
 ---
-title: "Creating unit test method stubs with the Create Unit Tests command"
+title: "Introduction to IntelliTest"
 ms.date: 05/02/2017
 ms.prod: visual-studio-dev15
 ms.technology: vs-ide-test
 ms.topic: conceptual
-helpviewer_keywords: 
+helpviewer_keywords:
   - "IntelliTest, Get started"
 ms.author: gewarren
 manager: douge
-ms.workload: 
+ms.workload:
   - "multiple"
 author: gewarren
 ---
diff --git a/docs/test/lab-management/use-build-or-rm-instead-of-lab-management.md b/docs/test/lab-management/use-build-or-rm-instead-of-lab-management.md
@@ -1,5 +1,5 @@
 ---
-title: "Use Build or Release Management for automated testing in Visual Studio"
+title: "Use build or release management for automated testing"
 ms.date: 03/02/2018
 ms.prod: visual-studio-dev15
 ms.technology: vs-ide-test
@@ -12,7 +12,7 @@ ms.workload:
   - "multiple"
 author: gewarren
 ---
-# Use Build and Release Management instead of Lab Management for automated testing
+# Use Azure Test Plans instead of Lab Management for automated testing
 
 If you use Microsoft Test Manager (MTM) and Lab Management for automated testing or for build-deploy-test automation, this topic explains how you can achieve the same goals using the [build and release](/azure/devops/pipelines/index?view=vsts) features in Team Foundation Server (TFS) and Azure Test Plans.
 
@@ -58,7 +58,7 @@ The following table summarizes the typical activities you perform in Lab Center,
 | Connect to machines. | Open the lab environment in Environment viewer. | Use SCVMM administration console directly to connect to the virtual machines. Alternatively, use the IP address or DNS names of the virtual machines to open remote desktop sessions. |
 | Take a checkpoint of an environment, or restore an environment to a clean checkpoint. | Open the lab environment in Environment viewer. Select the option to take a checkpoint or to restore to a previous checkpoint. | Use SCVMM administration console directly to perform these operations on virtual machines. Or, to perform these steps as part of a larger automation, include the checkpoint tasks from the [SCVMM Integration extension](https://marketplace.visualstudio.com/items?itemname=ms-vscs-rm.scvmmapp) as part of the environment in a release definition. |
 
-## Creation of network isolated environments
+## Create network-isolated environments
 
 A network isolated lab environment is a group of SCVMM virtual machines that can be cloned safely without causing network conflicts. This was done in MTM using a series of instructions that used a set of network interface cards to configure the virtual machines in a private network, and another set of network interface cards to configure the virtual machines in a public network.
 
diff --git a/docs/vs-2015/msbuild/msbuild-inline-tasks.md b/docs/vs-2015/msbuild/msbuild-inline-tasks.md
@@ -103,7 +103,7 @@ MSBuild tasks are typically created by compiling a class that implements the <xr
     AssemblyFile="$(MSBuildToolsPath)\Microsoft.Build.Tasks.v4.0.dll" >  
     <ParameterGroup />  
     <Task>  
-      <Reference Include="System.Xml.dll"/>  
+      <Reference Include="System.Xml"/>  
       <Using Namespace="System"/>  
       <Using Namespace="System.IO"/>  
       <Code Type="Fragment" Language="cs">  
diff --git a/subscriptions/vscloud-overview.md b/subscriptions/vscloud-overview.md
@@ -1,5 +1,5 @@
 ---
-title: How to buy Visual Studio Enterprise and Visual Studio Professional cloud subscriptions
+title: How to purchase Visual Studio cloud subscriptions
 author: evanwindom
 ms.author: jaunger
 manager: evelynp
