Merge remote-tracking branch 'MicrosoftDocs/master'

Author: timeyoutakeit

.openpublishing.redirection.json

@@ -97,6 +97,11 @@
             "redirect_url": "/visualstudio/code-quality/code-analysis-for-c-cpp-overview",
             "redirect_document_id": false
         },
+        {
+            "source_path": "docs/code-quality/code-analysis-rule-set-reference.md",
+            "redirect_url": "/visualstudio/code-quality/managed-minimun-rules-rule-set-for-managed-code",
+            "redirect_document_id": false
+        },
         {
             "source_path": "docs/code-quality/creating-and-using-code-analysis-check-in-policies.md",
             "redirect_url": "/visualstudio/code-quality/how-to-create-or-update-standard-code-analysis-check-in-policies",
@@ -652,6 +657,16 @@
             "redirect_url": "/visualstudio/debugger/graphics/walkthrough-using-graphics-diagnostics-to-debug-a-compute-shader",
             "redirect_document_id": false
         },
+        {
+            "source_path": "docs/debugger/first-look-at-the-debugger.md",
+            "redirect_url": "/visualstudio/debugger/getting-started-with-the-debugger",
+            "redirect_document_id": false
+        },
+        {
+            "source_path": "docs/debugger/debugger-basics.md",
+            "redirect_url": "/visualstudio/debugger/getting-started-with-the-debugger",
+            "redirect_document_id": false
+        },
         {
             "source_path": "docs/deployment/installshield-limited-edition.md",
             "redirect_url": "/visualstudio/deployment/deploying-applications-services-and-components",
@@ -1472,6 +1487,21 @@
             "redirect_url": "/visualstudio/profiling/profiling-feature-tour",
             "redirect_document_id": false
         },
+        {
+            "source_path": "docs/profiling/peopletrax-sample-profiling-tools.md",
+            "redirect_url": "/visualstudio/profiling/performance-explorer",
+            "redirect_document_id": false
+        },
+        {
+            "source_path": "docs/profiling/walkthrough-command-line-profiling-using-instrumentation.md",
+            "redirect_url": "/visualstudio/profiling/command-line-profiling-of-stand-alone-applications",
+            "redirect_document_id": false
+        },
+        {
+            "source_path": "docs/profiling/walkthrough-identifying-performance-problems.md",
+            "redirect_url": "/visualstudio/profiling/beginners-guide-to-cpu-sampling",
+            "redirect_document_id": false
+        },
         {
             "source_path": "docs/python/code-editing.md",
             "redirect_url": "/visualstudio/python/editing-python-code-in-visual-studio",
@@ -1807,6 +1837,11 @@
             "redirect_url": "/vsts/build-release/test/getting-started-with-continuous-testing",
             "redirect_document_id": false
         },
+        {
+            "source_path": "docs/test/create-and-run-unit-tests-for-a-store-app-in-visual-studio.md",
+            "redirect_url": "/visualstudio/test/unit-test-your-code",
+            "redirect_document_id": false
+        },
         {
             "source_path": "docs/test/index.md",
             "redirect_url": "/visualstudio/test/improve-code-quality",
@@ -1817,6 +1852,16 @@
             "redirect_url": "/visualstudio/test/lab-management/install-configure-test-agents",
             "redirect_document_id": false
         },
+        {
+            "source_path": "docs/test/lab-management/upgrade-scvmm-2008-r2-scvmm-2012.md",
+            "redirect_url": "/visualstudio/test/lab-management/using-a-lab-environment-for-your-application-lifecycle",
+            "redirect_document_id": false
+        },
+        {
+            "source_path": "docs/test/run-unit-tests-for-store-apps-in-visual-studio.md",
+            "redirect_url": "/visualstudio/test/run-unit-tests-with-test-explorer",
+            "redirect_document_id": false
+        },
         {
             "source_path": "docs/test/testing-store-apps-with-visual-studio.md",
             "redirect_url": "/visualstudio/test/create-and-run-unit-tests-for-a-store-app-in-visual-studio/",
@@ -1848,8 +1893,8 @@
             "redirect_document_id": false
         },
         {
-            "source_path": "docs/test/lab-management/upgrade-scvmm-2008-r2-scvmm-2012.md",
-            "redirect_url": "/visualstudio/test/lab-management/using-a-lab-environment-for-your-application-lifecycle",
+            "source_path": "docs/test/upgrading-coded-ui-tests-from-visual-studio-2010.md",
+            "redirect_url": "/visualstudio/test/use-ui-automation-to-test-your-code",
             "redirect_document_id": false
         },
         {
@@ -2137,6 +2182,36 @@
           "source_path": "docs/ide/quickstart-visual-basic-winforms.md",
           "redirect_url": "/visualstudio/ide/create-a-visual-basic-winform-in-visual-studio",
           "redirect_document_id": false
+        },
+        {
+          "source_path": "subscriptions/buy-vs-subscriptions.md",
+          "redirect_url": "http://www.visualstudio.com/vs/pricing/",
+          "redirect_document_id": false
+        },
+        {
+          "source_path": "subscriptions/compare-subscriptions.md",
+          "redirect_url": "http://www.visualstudio.com/vs/pricing/",
+          "redirect_document_id": false
+        },
+        {
+          "source_path": "subscriptions/vscloud-first-purchase.md",
+          "redirect_url": "/visualstudio/subscriptions/vscloud-overview",
+          "redirect_document_id": false
+        },
+        {
+          "source_path": "subscriptions/vscloud-renewals.md",
+          "redirect_url": "/visualstudio/subscriptions/vscloud-overview",
+          "redirect_document_id": false
+        },
+        {
+          "source_path": "subscriptions/vscloud-buy-more.md",
+          "redirect_url": "/visualstudio/subscriptions/vscloud-overview",
+          "redirect_document_id": false
+        },
+        {
+          "source_path": "subscriptions/vscloud-cancel.md",
+          "redirect_url": "/visualstudio/subscriptions/vscloud-overview",
+          "redirect_document_id": false
         }
     ]
 }

connected-environment/TOC.md

@@ -30,6 +30,7 @@
 
 # How to
 ##[Share a development environment](how-to/share-dev-environment.md)
+##[Use a custom NuGet feed](how-to/use-a-custom-nuget-feed.md)
 ##[Use kubectl with Visual Studio Connected Environment](how-to/use-kubectl-with-vsce.md)
 
 # [Troubleshoot](troubleshooting.md)

connected-environment/get-started-netcore-01.md

@@ -1,5 +1,5 @@
 ---
-title: "Visual Studio Connected Environment | Microsoft Docs"
+title: "Create a .NET Core development environment with containers using Kubernetes in the cloud - Step 1 - Install tools | Microsoft Docs"
 author: "johnsta"
 ms.author: "johnsta"
 ms.date: "02/20/2018"

connected-environment/get-started-netcore-02.md

@@ -1,5 +1,5 @@
 ---
-title: "Visual Studio Connected Environment | Microsoft Docs"
+title: "Create a .NET Core development environment with containers using Kubernetes in the cloud - Step 2 - Create a Kubernetes environment in Azure | Microsoft Docs"
 author: "johnsta"
 ms.author: "johnsta"
 ms.date: "02/20/2018"

connected-environment/get-started-netcore-03.md

@@ -1,5 +1,5 @@
 ---
-title: "Visual Studio Connected Environment | Microsoft Docs"
+title: "Create a .NET Core development environment with containers using Kubernetes in the cloud - Step 3 - Create an ASP.NET Core web app | Microsoft Docs"
 author: "johnsta"
 ms.author: "johnsta"
 ms.date: "02/20/2018"

connected-environment/get-started-netcore-04.md

@@ -1,5 +1,5 @@
 ---
-title: "Visual Studio Connected Environment | Microsoft Docs"
+title: "Create a .NET Core development environment with containers using Kubernetes in the cloud - Step 4 - Debug a container in Kubernetes  | Microsoft Docs"
 author: "johnsta"
 ms.author: "johnsta"
 ms.date: "02/20/2018"

connected-environment/get-started-netcore-05.md

@@ -1,5 +1,5 @@
 ---
-title: "Visual Studio Connected Environment | Microsoft Docs"
+title: "Create a .NET Core development environment with containers using Kubernetes in the cloud - Step 5 - Call another container | Microsoft Docs"
 author: "johnsta"
 ms.author: "johnsta"
 ms.date: "02/20/2018"

connected-environment/get-started-netcore-06.md

@@ -1,5 +1,5 @@
 ---
-title: "Visual Studio Connected Environment | Microsoft Docs"
+title: "Create a .NET Core development environment with containers using Kubernetes in the cloud - Step 6 - Learn about team development | Microsoft Docs"
 author: "johnsta"
 ms.author: "johnsta"
 ms.date: "02/20/2018"

connected-environment/get-started-netcore-07.md

@@ -1,5 +1,5 @@
 ---
-title: "Visual Studio Connected Environment | Microsoft Docs"
+title: "Create a .NET Core development environment with containers using Kubernetes in the cloud - Step 7 - Summary | Microsoft Docs"
 author: "johnsta"
 ms.author: "johnsta"
 ms.date: "02/20/2018"

connected-environment/get-started-netcore-visualstudio-01.md

@@ -1,5 +1,5 @@
 ---
-title: "Visual Studio Connected Environment | Microsoft Docs"
+title: "Create a .NET Core development environment with containers using Kubernetes in the cloud with Visual Studio - Step 1 - Install tools | Microsoft Docs"
 author: "johnsta"
 ms.author: "johnsta"
 ms.date: "02/20/2018"

connected-environment/get-started-netcore-visualstudio-02.md

@@ -1,5 +1,5 @@
 ---
-title: "Visual Studio Connected Environment | Microsoft Docs"
+title: "Create a .NET Core development environment with containers using Kubernetes in the cloud with Visual Studio - Step 2 - Create an ASP.NET web app | Microsoft Docs"
 author: "johnsta"
 ms.author: "johnsta"
 ms.date: "02/20/2018"

connected-environment/get-started-netcore-visualstudio-03.md

@@ -1,5 +1,5 @@
 ---
-title: "Visual Studio Connected Environment | Microsoft Docs"
+title: "Create a .NET Core development environment with containers using Kubernetes in the cloud with Visual Studio - Step 3 - Create a Kubernetes development environment | Microsoft Docs"
 author: "johnsta"
 ms.author: "johnsta"
 ms.date: "02/20/2018"

connected-environment/get-started-netcore-visualstudio-04.md

@@ -1,5 +1,5 @@
 ---
-title: "Visual Studio Connected Environment | Microsoft Docs"
+title: "Create a .NET Core development environment with containers using Kubernetes in the cloud with Visual Studio - Step 4 - Debug a container in Kubernetes | Microsoft Docs"
 author: "johnsta"
 ms.author: "johnsta"
 ms.date: "02/20/2018"

connected-environment/get-started-netcore-visualstudio-05.md

@@ -1,5 +1,5 @@
 ---
-title: "Visual Studio Connected Environment | Microsoft Docs"
+title: "Create a .NET Core development environment with containers using Kubernetes in the cloud with Visual Studio - Step 5 - Call another container | Microsoft Docs"
 author: "johnsta"
 ms.author: "johnsta"
 ms.date: "02/20/2018"
@@ -55,7 +55,7 @@ Let's now write code in `webfrontend` that makes a request to `mywebapi`. Switch
 
 Note how Kubernetes' DNS service discovery is employed to refer to the service as `http://mywebapi`. **Code in our development environment is running the same way it will run in production**.
 
-The code example above also makes use of a `HeaderPropagatingHttpClient` class. This helper class is the file `HeaderPropagation.cs` that was added to your project when you configured it to use Connected Environment. `HeaderPropagatingHttpClient` is dervied from the well-known `HttpClient` class, and it adds functionality to propagate specific headers from an existing ASP .NET HttpRequest object into an outgoing HttpRequestMessage object. We'll see later how this facilitates a more productive development experience in team scenarios.
+The code example above also makes use of a `HeaderPropagatingHttpClient` class. This helper class is the file `HeaderPropagation.cs` that was added to your project when you configured it to use Connected Environment. `HeaderPropagatingHttpClient` is derived from the well-known `HttpClient` class, and it adds functionality to propagate specific headers from an existing ASP .NET HttpRequest object into an outgoing HttpRequestMessage object. We'll see later how this facilitates a more productive development experience in team scenarios.
 
 ## Debug across multiple services
 1. At this point, `mywebapi` should still be running with the debugger attached. If it is not, hit F5 in the `mywebapi` project.

connected-environment/get-started-netcore-visualstudio-06.md

@@ -1,5 +1,5 @@
 ---
-title: "Visual Studio Connected Environment | Microsoft Docs"
+title: "Create a .NET Core development environment with containers using Kubernetes in the cloud with Visual Studio - Step 6 - Learn about team development | Microsoft Docs"
 author: "johnsta"
 ms.author: "johnsta"
 ms.date: "02/20/2018"
@@ -44,7 +44,7 @@ Do the following to make sure both our `webfrontend` and `mywebapi` services are
 3. Switch to the Visual Studio window with the `webfrontend` project and press Ctrl+F5 to run it as well.
 
 > [!Note]
-It is sometimes necessarry to refresh your browser after it the web page is initially displayed following a Ctrl+F5.
+It is sometimes necessary to refresh your browser after it the web page is initially displayed following a Ctrl+F5.
 
 Anyone who opens the public URL and navigates to the web app will invoke the code path we have written which runs through both services using the default `mainline` space. Now suppose we want to continue developing `mywebapi` - how can we do this and not interrupt other developers who are using the development environment? To do that, we'll set up our own space.
 

connected-environment/get-started-netcore-visualstudio-07.md

@@ -1,5 +1,5 @@
 ---
-title: "Visual Studio Connected Environment | Microsoft Docs"
+title: "Create a .NET Core development environment with containers using Kubernetes in the cloud with Visual Studio - Step 7 - Summary | Microsoft Docs"
 author: "johnsta"
 ms.author: "johnsta"
 ms.date: "02/20/2018"

connected-environment/get-started-nodejs-01.md

@@ -1,5 +1,5 @@
 ---
-title: "Visual Studio Connected Environment | Microsoft Docs"
+title: "Create a Node.js development environment with containers using Kubernetes in the cloud - Step 1 - Install tools | Microsoft Docs"
 author: "johnsta"
 ms.author: "johnsta"
 ms.date: "02/20/2018"

connected-environment/get-started-nodejs-02.md

@@ -1,5 +1,5 @@
 ---
-title: "Visual Studio Connected Environment | Microsoft Docs"
+title: "Create a Node.js development environment with containers using Kubernetes in the cloud - Step 2 - Create a Kubernetes development environment | Microsoft Docs"
 author: "johnsta"
 ms.author: "johnsta"
 ms.date: "02/20/2018"

connected-environment/get-started-nodejs-03.md

@@ -1,5 +1,5 @@
 ---
-title: "Visual Studio Connected Environment | Microsoft Docs"
+title: "Create a Node.js development environment with containers using Kubernetes in the cloud - Step 3 - Create an ASP.NET web app | Microsoft Docs"
 author: "johnsta"
 ms.author: "johnsta"
 ms.date: "02/20/2018"

connected-environment/get-started-nodejs-04.md

@@ -1,5 +1,5 @@
 ---
-title: "Visual Studio Connected Environment | Microsoft Docs"
+title: "Create a Node.js development environment with containers using Kubernetes in the cloud - Step 4 - Debug a container in Kubernetes | Microsoft Docs"
 author: "johnsta"
 ms.author: "johnsta"
 ms.date: "02/20/2018"

connected-environment/get-started-nodejs-05.md

@@ -1,5 +1,5 @@
 ---
-title: "Visual Studio Connected Environment | Microsoft Docs"
+title: "Create a Node.js development environment with containers using Kubernetes in the cloud - Step 5 - Call another container | Microsoft Docs"
 author: "johnsta"
 ms.author: "johnsta"
 ms.date: "02/20/2018"

connected-environment/get-started-nodejs-06.md

@@ -1,5 +1,5 @@
 ---
-title: "Visual Studio Connected Environment | Microsoft Docs"
+title: "Create a Node.js development environment with containers using Kubernetes in the cloud - Step 6 - Learn about team development | Microsoft Docs"
 author: "johnsta"
 ms.author: "johnsta"
 ms.date: "02/20/2018"

connected-environment/get-started-nodejs-07.md

@@ -1,5 +1,5 @@
 ---
-title: "Visual Studio Connected Environment | Microsoft Docs"
+title: "Create a Node.js development environment with containers using Kubernetes in the cloud - Step 7 - Summary | Microsoft Docs"
 author: "johnsta"
 ms.author: "johnsta"
 ms.date: "02/20/2018"

connected-environment/get-started.md

@@ -1,5 +1,5 @@
 ---
-title: "Visual Studio Connected Environment | Microsoft Docs"
+title: "Create a development environment with containers using Kubernetes in the cloud | Microsoft Docs"
 author: "johnsta"
 ms.author: "johnsta"
 ms.date: "02/20/2018"

connected-environment/how-to/use-a-custom-nuget-feed.md

@@ -0,0 +1,58 @@
+---
+title: "How to use a custom NuGet feed in a connected environment| Microsoft Docs"
+author: "johnsta"
+ms.author: "johnsta"
+ms.date: "03/27/2018"
+ms.topic: "article"
+description: "Use a custom NuGet feed to access and use NuGet packages in a connected environment."
+keywords: "Docker, Kubernetes, Azure, AKS, Azure Container Service, containers"
+manager: "ghogen"
+---
+#  Use a custom NuGet feed in a connected environment
+
+A NuGet feed provides a convenient way to include package sources in a project. Connected Environment will need to be able to access this feed in order for dependencies to be properly installed in the Docker container.
+
+To set up a NuGet feed:
+1. Add a [package reference](https://docs.microsoft.com/en-us/nuget/consume-packages/package-references-in-project-files) in the `*.csproj` file under the `PackageReference` node.
+
+   ```xml
+   <ItemGroup>
+       <!-- ... -->
+       <PackageReference Include="Contoso.Utility.UsefulStuff" Version="3.6.0" />
+       <!-- ... -->
+   </ItemGroup>
+   ```
+
+2. Create a [NuGet.Config](https://docs.microsoft.com/en-us/nuget/reference/nuget-config-file) file in the project folder.
+     * Use the `packageSources` section to reference your NuGet feed location. Important: The NuGet feed must be publicly accessible.
+     * Use the `packageSourceCredentials` section to configure username and password credentials. 
+
+   ```xml
+   <packageSources>
+       <add key="Contoso" value="https://contoso.com/packages/" />
+   </packageSources>
+
+   <packageSourceCredentials>
+       <Contoso>
+           <add key="Username" value="[email protected]" />
+           <add key="ClearTextPassword" value="33f!!lloppa" />
+       </Contoso>
+   </packageSourceCredentials>
+   ```
+
+3. If you're using source code control:
+    - Reference `NuGet.Config` in your `.gitignore` file so you don't accidentally commit credentials to your source repository.
+    - Open the `vsce.yaml` file in your project, and locate the `build` section, and insert the following snippet to ensure that the `NuGet.Config` file will be synced to Azure so that it used during the container image build process. (By default, Connected Environment does not synchronize files that match `.gitignore` and `.dockerignore` rules.)
+
+        ```yaml
+        build:
+        useGitIgnore: true
+        ignore:
+        - “!NuGet.Config”
+        ```
+
+
+## Next steps
+
+Once you have completed the above steps, the next time you run `vsce up` (or hit `F5` in VSCode or Visual Studio), Connected Environment will synchronize the `NuGet.Config` file to Azure, which is then utilized by `dotnet restore` to install package dependencies in the container.
+

connected-environment/troubleshooting.md

@@ -1,5 +1,5 @@
 ---
-title: "Visual Studio Connected Environment | Microsoft Docs"
+title: "Troubleshooting | Microsoft Docs"
 author: "johnsta"
 ms.author: "johnsta"
 ms.date: "02/20/2018"

connected-environment/visual-studio-connected-environment.md

@@ -9,7 +9,7 @@ description: "Rapid Kubernetes development with containers and microservices on
 keywords: "Docker, Kubernetes, Azure, AKS, Azure Container Service, containers"
 manager: "ghogen"
 ---
-# VS Connected Environment for AKS (Preview)
+# VS Connected Environment for Azure Container Service (AKS) (Preview)
 VS Connected Environment helps you develop with speed on Kubernetes. You create a Kubernetes-based environment that is fully managed in Azure and optimized for development, and then iteratively develop containers in the cloud using familiar tools like VS Code, Visual Studio, or the command line.
 
 This approach carries several benefits: