You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/dev-spaces/how-dev-spaces-works.md
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -25,7 +25,7 @@ This article describes the processes that power Azure Dev Spaces and how those p
25
25
26
26
*[Java with CLI and Visual Studio Code](quickstart-java.md)
27
27
*[.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)
29
29
*[Node.js with CLI and Visual Studio Code](quickstart-nodejs.md)
30
30
31
31
## How Azure Dev Spaces works
@@ -62,7 +62,7 @@ While your application is running, the client-side tooling also:
62
62
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:
63
63
64
64
* 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).
66
66
67
67
Here's the basic flow for setting up and using Azure Dev Spaces:
68
68
1. Prepare your AKS cluster for Azure Dev Spaces
@@ -400,11 +400,11 @@ ingress:
400
400
401
401
## Debug your code
402
402
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.
404
404
405
405

406
406
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.
408
408
409
409
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`.
410
410
@@ -429,12 +429,12 @@ To get started using Azure Dev Spaces, see the following quickstarts:
429
429
430
430
* [Java with CLI and Visual Studio Code](quickstart-java.md)
431
431
* [.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)
433
433
* [Node.js with CLI and Visual Studio Code](quickstart-nodejs.md)
434
434
435
435
To get started with team development, see the following how-to articles:
436
436
437
437
* [Team Development - Java with CLI and Visual Studio Code](team-development-java.md)
438
438
* [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)
440
440
* [Team Development - Node.js with CLI and Visual Studio Code](team-development-nodejs.md)
Copy file name to clipboardExpand all lines: articles/event-grid/custom-event-to-hybrid-connection.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -74,7 +74,7 @@ Notice that an [expiration date](concepts.md#event-subscription-expiration) is s
74
74
75
75
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.
76
76
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.
Copy file name to clipboardExpand all lines: articles/event-grid/event-grid-event-hubs-integration.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -40,7 +40,7 @@ In this article, you take the following steps:
40
40
To complete this tutorial, you must have:
41
41
42
42
* 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.
44
44
* Download the [EventHubsCaptureEventGridDemo sample project](https://github.com/Azure/azure-event-hubs/tree/master/samples/e2e/EventHubsCaptureEventGridDemo) to your computer.
45
45
46
46
## Deploy the infrastructure
@@ -191,7 +191,7 @@ Create a table in your data warehouse by running the [CreateDataWarehouseTable.s
191
191
192
192
## Publish the Azure Functions app
193
193
194
-
1. Launch Visual Studio 2017.
194
+
1. Launch Visual Studio.
195
195
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.
196
196
3. In Solution Explorer, right-click **FunctionEGDWDumper**, and select **Publish**.
Copy file name to clipboardExpand all lines: articles/event-hubs/event-hubs-dotnet-framework-getstarted-send.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -26,7 +26,7 @@ This tutorial shows how to create .NET Framework console applications in C# to s
26
26
## Prerequisites
27
27
To complete this tutorial, you need the following prerequisites:
28
28
29
-
-[Microsoft Visual Studio 2017 or higher](https://visualstudio.com).
29
+
-[Microsoft Visual Studio 2019](https://visualstudio.com).
30
30
-**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.
Copy file name to clipboardExpand all lines: articles/event-hubs/event-hubs-dotnet-standard-getstarted-send.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -29,7 +29,7 @@ This tutorial shows how to create .NET Core applications in C# to send events to
29
29
30
30
## Prerequisites
31
31
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).
33
33
-[.NET Core Visual Studio 2015 or 2017 tools](https://www.microsoft.com/net/core).
34
34
-**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.
-[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
40
40
- Download the [Git sample](https://github.com/Azure/azure-event-hubs/tree/master/samples/e2e/EventHubsCaptureEventGridDemo). The sample solution contains the following components:
41
41
-*WindTurbineDataGenerator* – A simple publisher that sends sample wind turbine data to a Capture-enabled event hub
42
42
-*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);
103
103
104
104
## Publish code to the Functions App
105
105
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.
107
107
108
108
1. In Solution Explorer, right-click *FunctionEGDWDumper*, and select **Publish**.
Copy file name to clipboardExpand all lines: articles/hdinsight/hdinsight-hadoop-emulator-visual-studio.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -21,7 +21,7 @@ Using the Hortonworks Sandbox allows you to work with Hadoop locally on your dev
21
21
22
22
* 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.
23
23
24
-
* Visual Studio 2013, Visual Studio 2015, or Visual Studio 2017 (any edition).
24
+
* Visual Studio.
25
25
26
26
* The [Azure SDK for .NET](https://azure.microsoft.com/downloads/) 2.7.1 or later.
0 commit comments