Merge pull request #4920 from MicrosoftDocs/master

6/25/2019 AM Publish

Author: Taojunshen

.openpublishing.redirection.json

@@ -7855,6 +7855,11 @@
             "redirect_url": "/visualstudio/subscriptions",
             "redirect_document_id": false
         },
+        {
+            "source_path": "subscriptions/vs-opsgility.md",
+            "redirect_url": "/visualstudio/subscriptions",
+            "redirect_document_id": false
+        },
         {
             "source_path": "subscriptions/leave-vsde.md",
             "redirect_url": "/visualstudio/subscriptions/join-dev-essentials",

docs/code-quality/ca1801-review-unused-parameters.md

@@ -1,6 +1,6 @@
 ---
 title: "CA1801: Review unused parameters"
-ms.date: 11/04/2016
+ms.date: 06/24/2019
 ms.topic: reference
 f1_keywords:
   - "AvoidUnusedParameters"
@@ -26,7 +26,10 @@ ms.workload:
 |Breaking Change|Non Breaking - If the member is not visible outside the assembly, regardless of the change you make.<br /><br /> Non Breaking - If you change the member to use the parameter within its body.<br /><br /> Breaking - If you remove the parameter and it is visible outside the assembly.|
 
 ## Cause
- A method signature includes a parameter that is not used in the method body. This rule does not examine the following methods:
+
+A method signature includes a parameter that's not used in the method body.
+
+This rule does not examine the following kinds of methods:
 
 - Methods referenced by a delegate.
 
@@ -41,24 +44,33 @@ ms.workload:
 - Methods declared with the `extern` (`Declare` statement in Visual Basic) modifier.
 
 ## Rule description
- Review parameters in non-virtual methods that are not used in the method body to make sure no correctness exists around failure to access them. Unused parameters incur maintenance and performance costs.
 
- Sometimes a violation of this rule can point to an implementation bug in the method. For example, the parameter should have been used in the method body. Suppress warnings of this rule if the parameter has to exist because of backward compatibility.
+Review parameters in non-virtual methods that are not used in the method body to make sure no correctness exists around failure to access them. Unused parameters incur maintenance and performance costs.
+
+Sometimes a violation of this rule can point to an implementation bug in the method. For example, the parameter should have been used in the method body. Suppress warnings of this rule if the parameter has to exist because of backward compatibility.
 
 ## How to fix violations
- To fix a violation of this rule, remove the unused parameter (a breaking change) or use the parameter in the method body (a non-breaking change).
+
+To fix a violation of this rule, remove the unused parameter (a breaking change) or use the parameter in the method body (a non-breaking change).
 
 ## When to suppress warnings
- It is safe to suppress a warning from this rule for previously shipped code for which the fix would be a breaking change.
+
+It is safe to suppress a warning from this rule:
+
+- For previously shipped code for which the fix would be a breaking change.
+
+- For the `this` parameter in a custom extension method for <xref:Microsoft.VisualStudio.TestTools.UnitTesting.Assert?displayProperty=nameWithType>. The functions in the <xref:Microsoft.VisualStudio.TestTools.UnitTesting.Assert> class are static, so there's no need to access the `this` parameter in the method body.
 
 ## Example
- The following example shows two methods. One method violates the rule and the other method satisfies the rule.
 
- [!code-csharp[FxCop.Usage.ReviewUnusedParameters#1](../code-quality/codesnippet/CSharp/ca1801-review-unused-parameters_1.cs)]
+The following example shows two methods. One method violates the rule and the other method satisfies the rule.
+
+[!code-csharp[FxCop.Usage.ReviewUnusedParameters#1](../code-quality/codesnippet/CSharp/ca1801-review-unused-parameters_1.cs)]
 
 ## Related rules
- [CA1811: Avoid uncalled private code](../code-quality/ca1811-avoid-uncalled-private-code.md)
 
- [CA1812: Avoid uninstantiated internal classes](../code-quality/ca1812-avoid-uninstantiated-internal-classes.md)
+[CA1811: Avoid uncalled private code](../code-quality/ca1811-avoid-uncalled-private-code.md)
+
+[CA1812: Avoid uninstantiated internal classes](../code-quality/ca1812-avoid-uninstantiated-internal-classes.md)
 
- [CA1804: Remove unused locals](../code-quality/ca1804-remove-unused-locals.md)
+[CA1804: Remove unused locals](../code-quality/ca1804-remove-unused-locals.md)

docs/debugger/using-breakpoints.md

@@ -138,9 +138,9 @@ To visually trace breakpoints during code execution, see [Map methods on the cal
 
 4. Add the following to the **Function Name** box, and select **C++** language.
 
-    ```C++
-    ((my_class *) 0xcccccccc)->my_method
-    ```
+   ```cpp
+   ((my_class *) 0xcccccccc)->my_method
+   ```
 
 ::: moniker range=">= vs-2019"
 
@@ -161,7 +161,7 @@ Data breakpoints in .NET Core won't work for:
 - Properties that are not expandable in the tooltip, Locals, Autos, or Watch window
 - Static variables
 - Classes with the DebuggerTypeProxy Attribute
-- Fields inside of structs 
+- Fields inside of structs
 
 ::: moniker-end
 
@@ -183,11 +183,12 @@ Data breakpoints don't work under the following conditions:
 - A process that is not being debugged writes to the memory location.
 - The memory location is shared between two or more processes.
 - The memory location is updated within the kernel. For example, if memory is passed to the 32-bit Windows `ReadFile` function, the memory will be updated from kernel mode, so the debugger won't break on the update.
+- Where the watch expression is larger than 4 bytes on 32-bit hardware and 8 bytes on 64-bit hardware. This is a limitation of the x86 architecture.
 
->[!NOTE]
->- Data breakpoints depend on specific memory addresses. The address of a variable changes from one debugging session to the next, so data breakpoints are automatically disabled at the end of each debugging session.
+> [!NOTE]
+> - Data breakpoints depend on specific memory addresses. The address of a variable changes from one debugging session to the next, so data breakpoints are automatically disabled at the end of each debugging session.
 >
->- If you set a data breakpoint on a local variable, the breakpoint remains enabled when the function ends, but the memory address is no longer applicable, so the behavior of the breakpoint is unpredictable. If you set a data breakpoint on a local variable, you should delete or disable the breakpoint before the function ends.
+> - If you set a data breakpoint on a local variable, the breakpoint remains enabled when the function ends, but the memory address is no longer applicable, so the behavior of the breakpoint is unpredictable. If you set a data breakpoint on a local variable, you should delete or disable the breakpoint before the function ends.
 
 ## <a name="BKMK_Specify_advanced_properties_of_a_breakpoint_"></a> Manage breakpoints in the Breakpoints window
 

docs/extensibility/how-to-provide-an-asynchronous-visual-studio-service.md

@@ -68,7 +68,7 @@ If you want to obtain a service without blocking the UI thread, you should creat
             await TaskScheduler.Default;
             // do background operations that involve IO or other async methods
 
-            await this.JoinableTaskFactory.SwitchToMainThreadAsync(cancellationToken);
+            await ThreadHelper.JoinableTaskFactory.SwitchToMainThreadAsync(cancellationToken);
             // query Visual Studio services on main thread unless they are documented as free threaded explicitly.
             // The reason for this is the final cast to service interface (such as IVsShell) may involve COM operations to add/release references.
 

docs/get-started/csharp/media/exploreide-greetingswithcontrollabels-cs.png

@@ -173,8 +173,6 @@ You're now ready to add a bit of Python code to implement a minimal web app.
     ![Setting the startup file for a project in Solution Explorer](media/quickstart-python-05-set-as-startup-file-2019.png)
     ::: moniker-end
 
-1. Right-click *app.py* in **Solution Explorer** and select **Set as startup file**. This command identifies the code file to launch in Python when running the app.
-
 2. Right-click the project in **Solution Explorer** and select **Properties**. Then select the **Debug** tab and set the **Port Number** property to `4449`. This step ensures that Visual Studio launches a browser with `localhost:4449` to match the `app.run` arguments in the code.
 
 3. Select **Debug > Start Without Debugging** (**Ctrl**+**F5**), which saves changes to files and runs the app.

docs/ide/quickstart-python.md

@@ -261,9 +261,10 @@ We have other support options available, too. For a list, see our [Feedback](../
 
 ## See also
 
-* [Update a network-based installation of Visual Studio](update-a-network-installation-of-visual-studio.md)
-* [Control updates to network-based Visual Studio deployments](controlling-updates-to-visual-studio-deployments.md)
-* [Visual Studio product lifecycle and servicing](/visualstudio/releases/2019/servicing/)
-* [Visual Studio administrator guide](visual-studio-administrator-guide.md)
-* [Use command-line parameters to install Visual Studio](use-command-line-parameters-to-install-visual-studio.md)
-* [Visual Studio workload and component IDs](workload-and-component-ids.md)
+- [Visual Studio administrator guide](visual-studio-administrator-guide.md)
+- [Update a network-based installation of Visual Studio](update-a-network-installation-of-visual-studio.md)
+- [Control updates to network-based Visual Studio deployments](controlling-updates-to-visual-studio-deployments.md)
+- [Visual Studio product lifecycle and servicing](/visualstudio/releases/2019/servicing/)
+- [Update Visual Studio while on a servicing baseline](update-servicing-baseline.md)
+- [Use command-line parameters to install Visual Studio](use-command-line-parameters-to-install-visual-studio.md)
+- [Visual Studio workload and component IDs](workload-and-component-ids.md)

docs/install/create-a-network-installation-of-visual-studio.md

@@ -176,6 +176,7 @@ c:\vslayout\vs_community.exe --add Microsoft.VisualStudio.Workload.ManagedDeskto
 ## See also
 
 - [Create a network installation of Visual Studio](../install/create-a-network-installation-of-visual-studio.md)
+- [Update a network-based installation of Visual Studio](update-a-network-installation-of-visual-studio.md)
 - [Install certificates required for Visual Studio offline installation](../install/install-certificates-for-visual-studio-offline.md)
 - [Use command-line parameters to install Visual Studio](use-command-line-parameters-to-install-visual-studio.md)
 - [Visual Studio workload and component IDs](workload-and-component-ids.md)

docs/install/create-an-offline-installation-of-visual-studio.md

@@ -3,7 +3,7 @@ title: "Modify Visual Studio"
 titleSuffix: ""
 description: "Learn how to modify Visual Studio, step-by-step."
 ms.custom: "H1Hack27Feb2017,seodec18"
-ms.date: 03/30/2018
+ms.date: 06/25/2019
 ms.topic: conceptual
 helpviewer_keywords:
   - "modify Visual Studio"
@@ -40,7 +40,10 @@ Here's how.
  Workloads contain the features you need for the programming language or platform that you are using. Use workloads to modify Visual Studio so that it supports the work you want to do, when you want to do it.
 
 >[!IMPORTANT]
->To install, update, or modify Visual Studio, you must log on with an account that has administrative permissions. For more information, see [User Permissions and Visual Studio](../ide/user-permissions-and-visual-studio.md).
+>To install, update, or modify Visual Studio, you must log on with an account that has administrative permissions. For more information, see [User permissions and Visual Studio](../ide/user-permissions-and-visual-studio.md).
+
+>[!TIP]
+> The following procedure assumes that you have an internet connection. For more information about how to modify a previously created [offline installation](create-an-offline-installation-of-visual-studio.md) of Visual Studio, see the [Control updates to network-based Visual Studio deployments](controlling-updates-to-visual-studio-deployments.md) page.
 
 ::: moniker range="vs-2017"
 
@@ -116,4 +119,6 @@ If you don't want to install workloads to customize your Visual Studio installat
 
 * [Update Visual Studio](update-visual-studio.md)
 * [Update a network-based installation of Visual Studio](update-a-network-installation-of-visual-studio.md)
+* [Update Visual Studio while on a servicing baseline](update-servicing-baseline.md)
+* [Control updates to network-based Visual Studio deployments](controlling-updates-to-visual-studio-deployments.md)
 * [Uninstall Visual Studio](uninstall-visual-studio.md)

docs/install/modify-visual-studio.md

@@ -2,7 +2,7 @@
 title: "Using Visual Studio on an Azure Virtual Machine"
 titleSuffix: ""
 description: "Learn how to use Visual Studio on an Azure Virtual Machine"
-ms.date: 05/23/2019
+ms.date: 06/24/2019
 ms.custom: "seodec18"
 ms.topic: conceptual
 helpviewer_keywords:
@@ -30,10 +30,10 @@ Images for the most recent major versions, Visual Studio 2019, Visual Studio 201
 
 | Release version                                                                                                                                          | Editions              |    Product version    |
 |:--------------------------------------------------------------------------------------------------------------------------------------------------------:|:---------------------:|:-----------------------:|
-| [Visual Studio 2019: Latest (Version 16.1)](https://azuremarketplace.microsoft.com/marketplace/apps/microsoftvisualstudio.visualstudio2019latest?tab=Overview) | Enterprise, Community | Version 16.1.0    |
-| [Visual Studio 2019: RTW](https://azuremarketplace.microsoft.com/marketplace/apps/microsoftvisualstudio.visualstudio2019?tab=Overview)                         | Enterprise, Community | Version 16.0.4    |
-| [Visual Studio 2017: Latest (Version 15.9)](https://azuremarketplace.microsoft.com/marketplace/apps/microsoftvisualstudio.visualstudio?tab=Overview)           | Enterprise, Community | Version 15.9.12   |
-| [Visual Studio 2017: RTW](https://azuremarketplace.microsoft.com/marketplace/apps/microsoftvisualstudio.visualstudio?tab=Overview)                             | Enterprise, Community | Version 15.0.23   |
+| [Visual Studio 2019: Latest (Version 16.1)](https://azuremarketplace.microsoft.com/marketplace/apps/microsoftvisualstudio.visualstudio2019latest?tab=Overview) | Enterprise, Community | Version 16.1.3    |
+| [Visual Studio 2019: RTW](https://azuremarketplace.microsoft.com/marketplace/apps/microsoftvisualstudio.visualstudio2019?tab=Overview)                         | Enterprise, Community | Version 16.0.5    |
+| [Visual Studio 2017: Latest (Version 15.9)](https://azuremarketplace.microsoft.com/marketplace/apps/microsoftvisualstudio.visualstudio?tab=Overview)           | Enterprise, Community | Version 15.9.13   |
+| [Visual Studio 2017: RTW](https://azuremarketplace.microsoft.com/marketplace/apps/microsoftvisualstudio.visualstudio?tab=Overview)                             | Enterprise, Community | Version 15.0.24   |
 | [Visual Studio 2015: Latest (Update 3)](https://azuremarketplace.microsoft.com/marketplace/apps/microsoftvisualstudio.visualstudio?tab=Overview)               | Enterprise, Community | Version 14.0.25431.01 |
 
 > [!NOTE]

docs/install/using-visual-studio-vm.md

@@ -34,7 +34,7 @@ To install these components using the manual installer, download and run the [Bu
 
 [!INCLUDE[workloads-components-header-2019_md](includes/workloads-components-header-2019_md.md)]
 
-To install these components using the manual installer, download and run the [Build Tools for Visual Studio](https://visualstudio.microsoft.com/downloads/#build-tools-for-visual-studio-2019).
+To install these components by using the manual installer, download and run the [Build Tools for Visual Studio](https://visualstudio.microsoft.com/downloads/#build-tools-for-visual-studio-2019).
 
 [!INCLUDE[Visual Studio Build Tools 2019](includes/vs-2019/workload-component-id-vs-build-tools.md)]
 

docs/install/workload-component-id-vs-build-tools.md

@@ -1,9 +1,9 @@
 ---
 title:  Manage Visual Studio Subscriptions
 author: evanwindom
-ms.author: jaunger
-manager: evelynp
-ms.date: 10/03/2017
+ms.author: lank
+manager: lank
+ms.date: 06/24/2019
 ms.topic: conceptual
 description: Learn how to get the most out of your Visual Studio subscriptions
 searchscope: VS Subscription
@@ -119,6 +119,12 @@ You can easily change the contact information and preferences in your profile.
    > [!div class="mx-imgBorder"]
    > ![Editing Profile Information](_img/manage-vs-subscriptions/edit-profile-resized.png)
 
+### Setting communications preferences
+If you would like to receive periodic updates about your subscription and benefits, including the monthly Visual Studio Subscriptions newsletter, [update your preferences](https://app.vsaex.visualstudio.com/me?workflowID=devprogram&tab=edit) by checking the box for Visual Studio Subscriptions in your Visual Studio profile. You can change these preferences and unsubscribe at any time. 
+
+   > [!div class="mx-imgBorder"]
+   > ![Setting Preferences](_img/manage-vs-subscriptions/change-prefs.png)
+   
 ### Linking my subscription to existing Azure DevOps Services or Azure subscriptions
 
 If you sign in to your subscription using a personal Microsoft account (MSA) and have a subscription that includes Azure DevOps Services or Microsoft Azure using a work or school account managed by Azure, you can link the two subscriptions. This is called an "alternate account" and allows you to keep using your MSA to sign in to your subscription while having access to existing Azure, Azure DevOps Services or IDE resources that are associated with your school or work accounts.