Skip to content

Commit 5deae15

Browse files
authored
Merge pull request #75641 from DennisLee-DennisLee/v-dele-1515469-6
1514063/1515469: VS2019 updates in Azure (part 6)
2 parents ef92f65 + 1941ebb commit 5deae15

10 files changed

+18
-18
lines changed

articles/dev-spaces/how-dev-spaces-works.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -25,7 +25,7 @@ This article describes the processes that power Azure Dev Spaces and how those p
2525

2626
* [Java with CLI and Visual Studio Code](quickstart-java.md)
2727
* [.NET Core with CLI and Visual Studio Code](quickstart-netcore.md)
28-
* [.NET Core with Visual Studio 2017](quickstart-netcore-visualstudio.md)
28+
* [.NET Core with Visual Studio](quickstart-netcore-visualstudio.md)
2929
* [Node.js with CLI and Visual Studio Code](quickstart-nodejs.md)
3030

3131
## How Azure Dev Spaces works
@@ -62,7 +62,7 @@ While your application is running, the client-side tooling also:
6262
You can use the client-side tooling from the command line as part of the `azds` command. You can also use the client-side tooling with:
6363

6464
* Visual Studio Code using the [Azure Dev Spaces extension](https://marketplace.visualstudio.com/items?itemName=azuredevspaces.azds).
65-
* Visual Studio 2017 with [Visual Studio Tools for Kubernetes](https://aka.ms/get-vsk8stools).
65+
* Visual Studio with [Visual Studio Tools for Kubernetes](https://aka.ms/get-vsk8stools).
6666

6767
Here's the basic flow for setting up and using Azure Dev Spaces:
6868
1. Prepare your AKS cluster for Azure Dev Spaces
@@ -400,11 +400,11 @@ ingress:
400400

401401
## Debug your code
402402

403-
For Java, .NET and Node.js applications, you can debug your application running directly in your dev space using Visual Studio Code or Visual Studio 2017. Visual Studio Code and Visual Studio 2017 provide tooling to connect to your dev space, launch your application, and attach a debugger. After running `azds prep`, you can open your project in Visual Studio Code or Visual Studio 2017. Visual Studio Code or Visual Studio 2017 will generate their own configuration files for connecting which is separate from running `azds prep`. From within Visual Studio Code or Visual Studio 2017, you can set breakpoints and launch your application to your dev space.
403+
For Java, .NET and Node.js applications, you can debug your application running directly in your dev space using Visual Studio Code or Visual Studio. Visual Studio Code and Visual Studio provide tooling to connect to your dev space, launch your application, and attach a debugger. After running `azds prep`, you can open your project in Visual Studio Code or Visual Studio. Visual Studio Code or Visual Studio will generate their own configuration files for connecting which is separate from running `azds prep`. From within Visual Studio Code or Visual Studio, you can set breakpoints and launch your application to your dev space.
404404

405405
![Debugging your code](media/get-started-node/debug-configuration-nodejs2.png)
406406

407-
When you launch your application using Visual Studio Code or Visual Studio 2017 for debugging, they handle launching and connecting to your dev space in the same way as running `azds up`. The client-side tooling in Visual Studio Code and Visual Studio 2017 also provide an additional parameter with specific information for debugging. The parameter contains the name of debugger image, the location of the debugger within in the debugger's image, and the destination location within the application's container to mount the debugger folder.
407+
When you launch your application using Visual Studio Code or Visual Studio for debugging, they handle launching and connecting to your dev space in the same way as running `azds up`. The client-side tooling in Visual Studio Code and Visual Studio also provide an additional parameter with specific information for debugging. The parameter contains the name of debugger image, the location of the debugger within in the debugger's image, and the destination location within the application's container to mount the debugger folder.
408408

409409
The debugger image is automatically determined by the client-side tooling. It uses a method similar to the one used during Dockerfile and Helm chart generate when running `azds prep`. After the debugger is mounted in the application's image, it is run using `azds exec`.
410410

@@ -429,12 +429,12 @@ To get started using Azure Dev Spaces, see the following quickstarts:
429429

430430
* [Java with CLI and Visual Studio Code](quickstart-java.md)
431431
* [.NET Core with CLI and Visual Studio Code](quickstart-netcore.md)
432-
* [.NET Core with Visual Studio 2017](quickstart-netcore-visualstudio.md)
432+
* [.NET Core with Visual Studio](quickstart-netcore-visualstudio.md)
433433
* [Node.js with CLI and Visual Studio Code](quickstart-nodejs.md)
434434

435435
To get started with team development, see the following how-to articles:
436436

437437
* [Team Development - Java with CLI and Visual Studio Code](team-development-java.md)
438438
* [Team Development - .NET Core with CLI and Visual Studio Code](team-development-netcore.md)
439-
* [Team Development - .NET Core with Visual Studio 2017](team-development-netcore-visualstudio.md)
439+
* [Team Development - .NET Core with Visual Studio](team-development-netcore-visualstudio.md)
440440
* [Team Development - Node.js with CLI and Visual Studio Code](team-development-nodejs.md)

articles/event-grid/custom-event-to-hybrid-connection.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -74,7 +74,7 @@ Notice that an [expiration date](concepts.md#event-subscription-expiration) is s
7474

7575
You need an application that can retrieve events from the hybrid connection. The [Microsoft Azure Event Grid Hybrid Connection Consumer sample for C#](https://github.com/Azure-Samples/event-grid-dotnet-hybridconnection-destination) performs that operation. You've already finished the prerequisite steps.
7676

77-
1. Make sure you have Visual Studio 2017 Version 15.5 or later.
77+
1. Make sure you have Visual Studio 2019 or later.
7878

7979
1. Clone the repository to your local machine.
8080

articles/event-grid/event-grid-event-hubs-integration.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -40,7 +40,7 @@ In this article, you take the following steps:
4040
To complete this tutorial, you must have:
4141

4242
* An Azure subscription. If you don't have an Azure subscription, create a [free account](https://azure.microsoft.com/free/) before you begin.
43-
* [Visual studio 2017 Version 15.3.2 or greater](https://www.visualstudio.com/vs/) with workloads for: .NET desktop development, Azure development, ASP.NET and web development, Node.js development, and Python development.
43+
* [Visual studio 2019](https://www.visualstudio.com/vs/) with workloads for: .NET desktop development, Azure development, ASP.NET and web development, Node.js development, and Python development.
4444
* Download the [EventHubsCaptureEventGridDemo sample project](https://github.com/Azure/azure-event-hubs/tree/master/samples/e2e/EventHubsCaptureEventGridDemo) to your computer.
4545

4646
## Deploy the infrastructure
@@ -191,7 +191,7 @@ Create a table in your data warehouse by running the [CreateDataWarehouseTable.s
191191
192192
## Publish the Azure Functions app
193193
194-
1. Launch Visual Studio 2017.
194+
1. Launch Visual Studio.
195195
2. Open the **EventHubsCaptureEventGridDemo.sln** solution that you downloaded from the [GitHub](https://github.com/Azure/azure-event-hubs/tree/master/samples/e2e/EventHubsCaptureEventGridDemo) as part of the prerequisites.
196196
3. In Solution Explorer, right-click **FunctionEGDWDumper**, and select **Publish**.
197197

articles/event-hubs/event-hubs-create.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -25,7 +25,7 @@ In this quickstart, you create an event hub using the [Azure portal](https://por
2525
To complete this quickstart, make sure that you have:
2626

2727
- Azure subscription. If you don't have one, [create a free account](https://azure.microsoft.com/free/) before you begin.
28-
- [Visual Studio 2017 Update 3 (version 15.3, 26730.01)](https://www.visualstudio.com/vs) or later.
28+
- [Visual Studio 2019)](https://www.visualstudio.com/vs) or later.
2929
- [.NET Standard SDK](https://www.microsoft.com/net/download/windows), version 2.0 or later.
3030

3131
## Create a resource group

articles/event-hubs/event-hubs-dotnet-framework-getstarted-send.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -26,7 +26,7 @@ This tutorial shows how to create .NET Framework console applications in C# to s
2626
## Prerequisites
2727
To complete this tutorial, you need the following prerequisites:
2828

29-
- [Microsoft Visual Studio 2017 or higher](https://visualstudio.com).
29+
- [Microsoft Visual Studio 2019](https://visualstudio.com).
3030
- **Create an Event Hubs namespace and an event hub**. The first step is to use the [Azure portal](https://portal.azure.com) to create a namespace of type Event Hubs, and obtain the management credentials your application needs to communicate with the event hub. To create a namespace and an event hub, follow the procedure in [this article](event-hubs-create.md). Then, get the **connection string for the event hub namespace** by following instructions from the article: [Get connection string](event-hubs-get-connection-string.md#get-connection-string-from-the-portal). You use the connection string later in this tutorial.
3131

3232
## Send events

articles/event-hubs/event-hubs-dotnet-standard-getstarted-send.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -29,7 +29,7 @@ This tutorial shows how to create .NET Core applications in C# to send events to
2929
3030
## Prerequisites
3131

32-
- [Microsoft Visual Studio 2015 or 2017](https://www.visualstudio.com). The examples in this tutorial use Visual Studio 2017, but Visual Studio 2015 is also supported.
32+
- [Microsoft Visual Studio 2019](https://www.visualstudio.com).
3333
- [.NET Core Visual Studio 2015 or 2017 tools](https://www.microsoft.com/net/core).
3434
- **Create an Event Hubs namespace and an event hub**. The first step is to use the [Azure portal](https://portal.azure.com) to create a namespace of type Event Hubs, and obtain the management credentials your application needs to communicate with the event hub. To create a namespace and an event hub, follow the procedure in [this article](event-hubs-create.md). Then, get the **connection string for the event hub namespace** by following instructions from the article: [Get connection string](event-hubs-get-connection-string.md#get-connection-string-from-the-portal). You use the connection string later in this tutorial.
3535

articles/event-hubs/event-hubs-quickstart-powershell.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -29,7 +29,7 @@ In this quickstart, you create an event hub using Azure PowerShell.
2929
To complete this tutorial, make sure you have:
3030

3131
- Azure subscription. If you don't have one, [create a free account][] before you begin.
32-
- [Visual Studio 2017 Update 3 (version 15.3, 26730.01)](https://www.visualstudio.com/vs) or later.
32+
- [Visual Studio 2019](https://www.visualstudio.com/vs).
3333
- [.NET Standard SDK](https://www.microsoft.com/net/download/windows), version 2.0 or later.
3434

3535
[!INCLUDE [cloud-shell-try-it.md](../../includes/cloud-shell-try-it.md)]

articles/event-hubs/store-captured-data-data-warehouse.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -36,7 +36,7 @@ In this tutorial, you do the following actions:
3636

3737
[!INCLUDE [updated-for-az](../../includes/updated-for-az.md)]
3838

39-
- [Visual studio 2017 Version 15.3.2 or greater](https://www.visualstudio.com/vs/). While installing, ensure that you install the following workloads: .NET desktop development, Azure development, ASP.NET and web development, Node.js development, Python development
39+
- [Visual studio 2019](https://www.visualstudio.com/vs/). While installing, ensure that you install the following workloads: .NET desktop development, Azure development, ASP.NET and web development, Node.js development, Python development
4040
- Download the [Git sample](https://github.com/Azure/azure-event-hubs/tree/master/samples/e2e/EventHubsCaptureEventGridDemo). The sample solution contains the following components:
4141
- *WindTurbineDataGenerator* – A simple publisher that sends sample wind turbine data to a Capture-enabled event hub
4242
- *FunctionDWDumper* – An Azure Function that receives an Event Grid notification when an Avro file is captured to the Azure Storage blob. It receives the blob’s URI path, reads its contents, and pushes this data to a SQL Data Warehouse.
@@ -103,7 +103,7 @@ WITH (CLUSTERED COLUMNSTORE INDEX, DISTRIBUTION = ROUND_ROBIN);
103103

104104
## Publish code to the Functions App
105105

106-
1. Open the solution *EventHubsCaptureEventGridDemo.sln* in Visual Studio 2017 (15.3.2 or greater).
106+
1. Open the solution *EventHubsCaptureEventGridDemo.sln* in Visual Studio 2019.
107107

108108
1. In Solution Explorer, right-click *FunctionEGDWDumper*, and select **Publish**.
109109

articles/hdinsight/hdinsight-hadoop-create-linux-clusters-dotnet-sdk.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -27,11 +27,11 @@ Learn how to create an [Apache Hadoop](https://hadoop.apache.org/) cluster in Az
2727

2828
* **An Azure subscription**. See [Get Azure free trial](https://azure.microsoft.com/documentation/videos/get-azure-free-trial-for-testing-hadoop-in-hdinsight/).
2929
* **An Azure storage account**. See [Create a storage account](../storage/common/storage-quickstart-create-account.md).
30-
* **Visual Studio 2013, Visual Studio 2015 or Visual Studio 2017**.
30+
* **Visual Studio**.
3131

3232
## Create clusters
3333

34-
1. Open Visual Studio 2017.
34+
1. Open Visual Studio.
3535
2. Create a new Visual C# console application.
3636
3. From the **Tools** menu, click **NuGet Package Manager**, and then click **Package Manager Console**.
3737
4. Run the following command in the console to install the packages:

articles/hdinsight/hdinsight-hadoop-emulator-visual-studio.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -21,7 +21,7 @@ Using the Hortonworks Sandbox allows you to work with Hadoop locally on your dev
2121

2222
* The Hortonworks Sandbox, running in a virtual machine on your development environment. This document was written and tested with the sandbox running in Oracle VirtualBox. For information on setting up the sandbox, see the [Get started with the Hortonworks sandbox.](hadoop/apache-hadoop-emulator-get-started.md) document.
2323

24-
* Visual Studio 2013, Visual Studio 2015, or Visual Studio 2017 (any edition).
24+
* Visual Studio.
2525

2626
* The [Azure SDK for .NET](https://azure.microsoft.com/downloads/) 2.7.1 or later.
2727

0 commit comments

Comments
 (0)