Merge branch 'master' into Release_Archive_master_2020-09-29-02-07-42

Author: ghogen

.openpublishing.redirection.json

@@ -4,7 +4,7 @@
     "rootDirectory": "docs/",
     "docLinkSettings": {
         "linkFormat": "relative",
-        "relativeLinkPrefix": "/visualstudio/"
+        "relativeLinkPrefix": "../"
     },
     "inclusionCriteria": {
         "additionalMicrosoftOrgs": [

.whatsnew.json

@@ -20,7 +20,9 @@ At this point, your development team is quite small and you're simply building a
 
 ## Get the app
 
-Before you can run the application, you need to get the application source code onto your machine. For real projects, you will typically clone the repo. But, for this tutorial, you have created a ZIP file containing the application.
+Before you can run the application, you need to get the application source code onto your machine. For real projects, you will typically clone the repo. But, for this tutorial, we have created a ZIP file containing the application.
+
+1. Make sure that you have Docker for Windows or Docker Community Edition installed on the local machine. See [Docker for Windows installation documentation](https://docs.docker.com/docker-for-windows/install/). The install process makes the ZIP file containing the sample available at the localhost address.
 
 1. [Download the ZIP](http://localhost/assets/app.zip). Open the ZIP file and make sure you extract the contents.
 

docker/index.md

@@ -10,7 +10,7 @@
       tocHref: /visualstudio/ide/
       topicHref: /visualstudio/ide/
       items:
-      - name: Code Quality
+      - name: Code Analysis
         tocHref: /visualstudio/code-quality/
         topicHref: /visualstudio/code-quality/analyzing-application-quality-by-using-code-analysis-tools
       - name: Cross Platform

docker/tutorials/your-application.md

@@ -1,5 +1,7 @@
 ---
 title: Create an AI project from existing code
+description: Learn how to use Visual Studio Tools for AI to bring existing Python code into a Visual Studio project.
+ms.custom: SEO-VS-2020
 author: jillre
 ms.author: jillfra
 manager: jillfra

docs/_breadcrumb/toc.yml

@@ -1,5 +1,7 @@
 ---
 title: Clone a repo
+description: Learn how to use Visual Studio Tools for AI to clone a repository of Python code and create a project from it.
+ms.custom: SEO-VS-2020
 author: jillre
 ms.author: jillfra
 manager: jillfra

docs/ai/create-project-existing.md

@@ -1,5 +1,7 @@
 ---
 title: Create an AI project from a template
+description: Learn how to use Visual Studio Tools for AI to create an AI project from a variety of templates.
+ms.custom: SEO-VS-2020
 author: jillre
 ms.author: jillfra
 manager: jillfra

docs/ai/create-project-repo.md

@@ -1,5 +1,7 @@
 ---
 title: View recent jobs
+description: Learn that once jobs are submitted, you can view the list of jobs to see their status, duration, and more.
+ms.custom: SEO-VS-2020
 author: jillre
 ms.author: jillfra
 manager: jillfra

docs/ai/create-project.md

@@ -1,5 +1,7 @@
 ---
 title: Browse storage to upload data
+description: Learn how you can browse all storage on the remote machine or Azure file share to enable uploading data or downloading models and logs.
+ms.custom: SEO-VS-2020
 author: jillre
 ms.author: jillfra
 manager: jillfra

docs/ai/job-details.md

@@ -1,5 +1,7 @@
 ---
 title: Monitor GPU utilization
+description: Learn about GPU utilization. Specifically, learn how to monitor GPU utilization of remote Linux machines.
+ms.custom: SEO-VS-2020
 author: jillre
 ms.author: jillfra
 manager: jillfra

docs/ai/manage-storage.md

@@ -1,5 +1,7 @@
 ---
 title: Monitor with TensorBoard
+description: Learn how you can use Visual Studio to visualize your model training progress with TensorBoard.
+ms.custom: SEO-VS-2020
 author: jillre
 ms.author: jillfra
 manager: jillfra

docs/ai/monitor-gpu.md

@@ -1,5 +1,7 @@
 ---
 title: Overview of Visual Studio Tools for AI
+description: Learn how Visual Studio Tools for AI is an integrated development environment (IDE) that you can use to build, test, and deploy deep learning solutions.
+ms.custom: SEO-VS-2020
 author: jillre
 ms.author: jillfra
 manager: jillfra

docs/ai/monitor-tensorboard.md

@@ -51,7 +51,7 @@ landingContent:
         - text: Container tools in Visual Studio
           url: ../containers/overview.md
         - text: Kubernetes tools
-          url: ../containers/tutorial-kubernetes-tools.md
+          url: ../containers/bridge-to-kubernetes.md
 
   - title: Debug Azure services and analyze performance
     linkLists:

docs/ai/overview.md

@@ -5,13 +5,13 @@
   expanded: true
   items:
   - name: Deploy an ASP.NET Core app to Azure
-    href: /aspnet/core/tutorials/publish-to-azure-webapp-using-vs?view=aspnetcore-2.1
+    href: /aspnet/core/tutorials/publish-to-azure-webapp-using-vs?view=aspnetcore-2.1&preserve-view=true
   - name: Deploy a .NET TODO List Web App to Azure
-    href: /dotnet/azure/dotnet-quickstart-vs?view=azure-dotnet
+    href: /dotnet/azure/dotnet-quickstart-vs?view=azure-dotnet&preserve-view=true
   - name: Continuous deployment to Azure with Visual Studio and Git with ASP.NET Core
-    href: /aspnet/core/host-and-deploy/azure-apps/azure-continuous-deployment?view=aspnetcore-2.1
+    href: /aspnet/core/host-and-deploy/azure-apps/azure-continuous-deployment?view=aspnetcore-2.1&preserve-view=true
   - name: Continuous deployment to Azure with Azure Pipelines
-    href: /azure/devops/pipelines/get-started-yaml?view=vsts
+    href: /azure/devops/pipelines/get-started-yaml?view=vsts&preserve-view=true
   - name: Deploy an ASP.NET Web App to an Azure VM
     href: /azure/virtual-machines/windows/publish-web-app-from-visual-studio?toc=/visualstudio/azure/toc.json&bc=/visualstudio/azure/breadcrumb/toc.json
 - name: Connect to Azure services

docs/azure/index.yml

@@ -14,4 +14,4 @@ The All Rules rule set contains all of the rules for both native and managed cod
 
 - [Code Analysis for C/C++ Warnings](/cpp/code-quality/code-analysis-for-c-cpp-warnings)
 
-- [Code Analysis for Managed Code Warnings](../code-quality/code-analysis-for-managed-code-warnings.md)
+- [Code Analysis for Managed Code Warnings](/dotnet/fundamentals/code-analysis/quality-rules/index)

docs/azure/toc.yml

@@ -18,7 +18,7 @@ This page contains answers to some frequently asked questions about .NET Compile
 
 **Q**: Should I use code analysis or EditorConfig for checking code style?
 
-**A**: Code analysis and EditorConfig files work hand-in-hand. When you define code styles [in an EditorConfig file](../ide/editorconfig-code-style-settings-reference.md) or on the [text editor Options](../ide/code-styles-and-code-cleanup.md) page, you're actually configuring the code analyzers that are built into Visual Studio. EditorConfig files can be used to enable or disable analyzer rules, and also to configure NuGet analyzer packages.
+**A**: Code analysis and EditorConfig files work hand-in-hand. When you define code styles [in an EditorConfig file](/dotnet/fundamentals/code-analysis/code-style-rule-options) or on the [text editor Options](../ide/code-styles-and-code-cleanup.md) page, you're actually configuring the code analyzers that are built into Visual Studio. EditorConfig files can be used to enable or disable analyzer rules, and also to configure NuGet analyzer packages.
 
 ## EditorConfig versus rule sets
 
@@ -28,8 +28,8 @@ This page contains answers to some frequently asked questions about .NET Compile
 
 However, EditorConfig files offer additional ways to configure rules too:
 
-- For the .NET code-quality analyzers, EditorConfig files let you [define which types of code to analyze](fxcop-analyzer-options.md).
-- For the .NET code-style analyzers that are built into Visual Studio, EditorConfig files let you [define the preferred code styles](../ide/editorconfig-code-style-settings-reference.md) for a codebase.
+- For the .NET code-quality analyzers, EditorConfig files let you [define which types of code to analyze](/dotnet/fundamentals/code-analysis/code-quality-rule-options).
+- For the .NET code-style analyzers that are built into Visual Studio, EditorConfig files let you [define the preferred code styles](/dotnet/fundamentals/code-analysis/code-style-rule-options) for a codebase.
 
 In addition to rule sets and EditorConfig files, some analyzers are configured through the use of text files marked as [additional files](../ide/build-actions.md#build-action-values) for the C# and VB compilers.
 
@@ -91,4 +91,4 @@ In addition to rule sets and EditorConfig files, some analyzers are configured t
 ## See also
 
 - [Analyzers overview](roslyn-analyzers-overview.md)
-- [.NET coding convention settings for EditorConfig](../ide/editorconfig-code-style-settings-reference.md)
+- [.NET coding convention settings for EditorConfig](/dotnet/fundamentals/code-analysis/code-style-rule-options)

docs/code-quality/all-rules-rule-set.md

@@ -17,29 +17,29 @@ The following table describes all the rules in the Microsoft Basic Correctness R
 
 |Rule|Description|
 |----------|-----------------|
-|[CA1001](../code-quality/ca1001.md)|Types that own disposable fields should be disposable|
+|[CA1001](/dotnet/fundamentals/code-analysis/quality-rules/ca1001)|Types that own disposable fields should be disposable|
 |[CA1009](../code-quality/ca1009.md)|Declare event handlers correctly|
-|[CA1016](../code-quality/ca1016.md)|Mark assemblies with AssemblyVersionAttribute|
-|[CA1033](../code-quality/ca1033.md)|Interface methods should be callable by child types|
+|[CA1016](/dotnet/fundamentals/code-analysis/quality-rules/ca1016)|Mark assemblies with AssemblyVersionAttribute|
+|[CA1033](/dotnet/fundamentals/code-analysis/quality-rules/ca1033)|Interface methods should be callable by child types|
 |[CA1049](../code-quality/ca1049.md)|Types that own native resources should be disposable|
-|[CA1060](../code-quality/ca1060.md)|Move P/Invokes to NativeMethods class|
-|[CA1061](../code-quality/ca1061.md)|Do not hide base class methods|
-|[CA1063](../code-quality/ca1063.md)|Implement IDisposable correctly|
-|[CA1065](../code-quality/ca1065.md)|Do not raise exceptions in unexpected locations|
+|[CA1060](/dotnet/fundamentals/code-analysis/quality-rules/ca1060)|Move P/Invokes to NativeMethods class|
+|[CA1061](/dotnet/fundamentals/code-analysis/quality-rules/ca1061)|Do not hide base class methods|
+|[CA1063](/dotnet/fundamentals/code-analysis/quality-rules/ca1063)|Implement IDisposable correctly|
+|[CA1065](/dotnet/fundamentals/code-analysis/quality-rules/ca1065)|Do not raise exceptions in unexpected locations|
 |[CA1301](../code-quality/ca1301.md)|Avoid duplicate accelerators|
 |[CA1400](../code-quality/ca1400.md)|P/Invoke entry points should exist|
-|[CA1401](../code-quality/ca1401.md)|P/Invokes should not be visible|
+|[CA1401](/dotnet/fundamentals/code-analysis/quality-rules/ca1401)|P/Invokes should not be visible|
 |[CA1403](../code-quality/ca1403.md)|Auto layout types should not be COM visible|
 |[CA1404](../code-quality/ca1404.md)|Call GetLastError immediately after P/Invoke|
 |[CA1405](../code-quality/ca1405.md)|COM visible type base types should be COM visible|
 |[CA1410](../code-quality/ca1410.md)|COM registration methods should be matched|
 |[CA1415](../code-quality/ca1415.md)|Declare P/Invokes correctly|
-|[CA1821](../code-quality/ca1821.md)|Remove empty finalizers|
+|[CA1821](/dotnet/fundamentals/code-analysis/quality-rules/ca1821)|Remove empty finalizers|
 |[CA1900](../code-quality/ca1900.md)|Value type fields should be portable|
 |[CA1901](../code-quality/ca1901.md)|P/Invoke declarations should be portable|
-|[CA2002](../code-quality/ca2002.md)|Do not lock on objects with weak identity|
-|[CA2100](../code-quality/ca2100.md)|Review SQL queries for security vulnerabilities|
-|[CA2101](../code-quality/ca2101.md)|Specify marshaling for P/Invoke string arguments|
+|[CA2002](/dotnet/fundamentals/code-analysis/quality-rules/ca2002)|Do not lock on objects with weak identity|
+|[CA2100](/dotnet/fundamentals/code-analysis/quality-rules/ca2100)|Review SQL queries for security vulnerabilities|
+|[CA2101](/dotnet/fundamentals/code-analysis/quality-rules/ca2101)|Specify marshaling for P/Invoke string arguments|
 |[CA2108](../code-quality/ca2108.md)|Review declarative security on value types|
 |[CA2111](../code-quality/ca2111.md)|Pointers should not be visible|
 |[CA2112](../code-quality/ca2112.md)|Secured types should not expose fields|
@@ -61,32 +61,32 @@ The following table describes all the rules in the Microsoft Basic Correctness R
 |[CA2146](../code-quality/ca2146.md)|Types must be at least as critical as their base types and interfaces|
 |[CA2147](../code-quality/ca2147.md)|Transparent methods may not use security asserts|
 |[CA2149](../code-quality/ca2149.md)|Transparent methods must not call into native code|
-|[CA2200](../code-quality/ca2200.md)|Rethrow to preserve stack details|
+|[CA2200](/dotnet/fundamentals/code-analysis/quality-rules/ca2200)|Rethrow to preserve stack details|
 |[CA2202](../code-quality/ca2202.md)|Do not dispose objects multiple times|
-|[CA2207](../code-quality/ca2207.md)|Initialize value type static fields inline|
+|[CA2207](/dotnet/fundamentals/code-analysis/quality-rules/ca2207)|Initialize value type static fields inline|
 |[CA2212](../code-quality/ca2212.md)|Do not mark serviced components with WebMethod|
-|[CA2213](../code-quality/ca2213.md)|Disposable fields should be disposed|
-|[CA2214](../code-quality/ca2214.md)|Do not call overridable methods in constructors|
-|[CA2216](../code-quality/ca2216.md)|Disposable types should declare finalizer|
+|[CA2213](/dotnet/fundamentals/code-analysis/quality-rules/ca2213)|Disposable fields should be disposed|
+|[CA2214](/dotnet/fundamentals/code-analysis/quality-rules/ca2214)|Do not call overridable methods in constructors|
+|[CA2216](/dotnet/fundamentals/code-analysis/quality-rules/ca2216)|Disposable types should declare finalizer|
 |[CA2220](../code-quality/ca2220.md)|Finalizers should call base class finalizer|
-|[CA2229](../code-quality/ca2229.md)|Implement serialization constructors|
-|[CA2231](../code-quality/ca2231.md)|Overload operator equals on overriding ValueType.Equals|
+|[CA2229](/dotnet/fundamentals/code-analysis/quality-rules/ca2229)|Implement serialization constructors|
+|[CA2231](/dotnet/fundamentals/code-analysis/quality-rules/ca2231)|Overload operator equals on overriding ValueType.Equals|
 |[CA2232](../code-quality/ca2232.md)|Mark Windows Forms entry points with STAThread|
-|[CA2235](../code-quality/ca2235.md)|Mark all non-serializable fields|
+|[CA2235](/dotnet/fundamentals/code-analysis/quality-rules/ca2235)|Mark all non-serializable fields|
 |[CA2236](../code-quality/ca2236.md)|Call base class methods on ISerializable types|
-|[CA2237](../code-quality/ca2237.md)|Mark ISerializable types with SerializableAttribute|
+|[CA2237](/dotnet/fundamentals/code-analysis/quality-rules/ca2237)|Mark ISerializable types with SerializableAttribute|
 |[CA2238](../code-quality/ca2238.md)|Implement serialization methods correctly|
 |[CA2240](../code-quality/ca2240.md)|Implement ISerializable correctly|
-|[CA2241](../code-quality/ca2241.md)|Provide correct arguments to formatting methods|
-|[CA2242](../code-quality/ca2242.md)|Test for NaN correctly|
-|[CA1008](../code-quality/ca1008.md)|Enums should have zero value|
+|[CA2241](/dotnet/fundamentals/code-analysis/quality-rules/ca2241)|Provide correct arguments to formatting methods|
+|[CA2242](/dotnet/fundamentals/code-analysis/quality-rules/ca2242)|Test for NaN correctly|
+|[CA1008](/dotnet/fundamentals/code-analysis/quality-rules/ca1008)|Enums should have zero value|
 |[CA1013](../code-quality/ca1013.md)|Overload operator equals on overloading add and subtract|
-|[CA1303](../code-quality/ca1303.md)|Do not pass literals as localized parameters|
-|[CA1308](../code-quality/ca1308.md)|Normalize strings to uppercase|
-|[CA1806](../code-quality/ca1806.md)|Do not ignore method results|
-|[CA1816](../code-quality/ca1816.md)|Call GC.SuppressFinalize correctly|
-|[CA1819](../code-quality/ca1819.md)|Properties should not return arrays|
-|[CA1820](../code-quality/ca1820.md)|Test for empty strings using string length|
+|[CA1303](/dotnet/fundamentals/code-analysis/quality-rules/ca1303)|Do not pass literals as localized parameters|
+|[CA1308](/dotnet/fundamentals/code-analysis/quality-rules/ca1308)|Normalize strings to uppercase|
+|[CA1806](/dotnet/fundamentals/code-analysis/quality-rules/ca1806)|Do not ignore method results|
+|[CA1816](/dotnet/fundamentals/code-analysis/quality-rules/ca1816)|Call GC.SuppressFinalize correctly|
+|[CA1819](/dotnet/fundamentals/code-analysis/quality-rules/ca1819)|Properties should not return arrays|
+|[CA1820](/dotnet/fundamentals/code-analysis/quality-rules/ca1820)|Test for empty strings using string length|
 |[CA1903](../code-quality/ca1903.md)|Use only API from targeted framework|
 |[CA2004](../code-quality/ca2004.md)|Remove calls to GC.KeepAlive|
 |[CA2006](../code-quality/ca2006.md)|Use SafeHandle to encapsulate native resources|
@@ -95,16 +95,16 @@ The following table describes all the rules in the Microsoft Basic Correctness R
 |[CA2105](../code-quality/ca2105.md)|Array fields should not be read only|
 |[CA2106](../code-quality/ca2106.md)|Secure asserts|
 |[CA2115](../code-quality/ca2115.md)|Call GC.KeepAlive when using native resources|
-|[CA2119](../code-quality/ca2119.md)|Seal methods that satisfy private interfaces|
+|[CA2119](/dotnet/fundamentals/code-analysis/quality-rules/ca2119)|Seal methods that satisfy private interfaces|
 |[CA2120](../code-quality/ca2120.md)|Secure serialization constructors|
 |[CA2121](../code-quality/ca2121.md)|Static constructors should be private|
 |[CA2130](../code-quality/ca2130.md)|Security critical constants should be transparent|
 |[CA2205](../code-quality/ca2205.md)|Use managed equivalents of Win32 API|
-|[CA2215](../code-quality/ca2215.md)|Dispose methods should call base class dispose|
+|[CA2215](/dotnet/fundamentals/code-analysis/quality-rules/ca2215)|Dispose methods should call base class dispose|
 |[CA2221](../code-quality/ca2221.md)|Finalizers should be protected|
 |[CA2222](../code-quality/ca2222.md)|Do not decrease inherited member visibility|
 |[CA2223](../code-quality/ca2223.md)|Members should differ by more than return type|
 |[CA2224](../code-quality/ca2224.md)|Override equals on overloading operator equals|
-|[CA2226](../code-quality/ca2226.md)|Operators should have symmetrical overloads|
-|[CA2227](../code-quality/ca2227.md)|Collection properties should be read only|
+|[CA2226](/dotnet/fundamentals/code-analysis/quality-rules/ca2226)|Operators should have symmetrical overloads|
+|[CA2227](/dotnet/fundamentals/code-analysis/quality-rules/ca2227)|Collection properties should be read only|
 |[CA2239](../code-quality/ca2239.md)|Provide deserialization methods for optional fields|