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: docs/ai/installation.md
+1-2Lines changed: 1 addition & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -28,10 +28,9 @@ You can download the tools from the [Visual Studio Marketplace](https://marketpl
28
28
2. In the **Extensions and Updates** dialog box, select **Online** on the left-hand side.
29
29
3. In the search box in the upper right-hand corner, type or enter "tools for ai".
30
30
4. Select **Visual Studio Tools for AI** from the results.
31
-
5.Click**Download**.
31
+
5.Select**Download**.
32
32
33
33
## Prepare your local machine
34
-
35
34
Before training deep learning models on your local computer, make sure you have the applicable prerequisites installed. This includes making sure you have the latest drivers and libraries for your NVIDIA GPU (if you have one). Also ensure you've installed Python and Python libraries such as NumPy, SciPy, and appropriate deep learning frameworks such as Microsoft Cognitive Toolkit (CNTK), TensorFlow, Caffe2, MXNet, Keras, Theano, PyTorch, and Chainer, that you plan to use in your project.
Copy file name to clipboardExpand all lines: docs/azure/vs-azure-tools-configure-roles-for-cloud-service.md
+6-6Lines changed: 6 additions & 6 deletions
Original file line number
Diff line number
Diff line change
@@ -30,7 +30,7 @@ You can configure an Azure cloud service from Solution Explorer in Visual Studio
30
30
31
31
1. Create or open an Azure cloud service project in Visual Studio.
32
32
33
-
1. In **Solution Explorer**, right-click the project, and, from the context menu, select **Properties**.
33
+
1. In **Solution Explorer**, right-click (or select and hold) the project, and, from the context menu, select **Properties**.
34
34
35
35

36
36
@@ -50,7 +50,7 @@ To improve the performance of your cloud service, you can change the number of i
50
50
51
51
1. Create or open an Azure cloud service project in Visual Studio.
52
52
53
-
1. In **Solution Explorer**, expand the project node. Under the **Roles** node, right-click the role you want to update, and, from the context menu, select **Properties**.
53
+
1. In **Solution Explorer**, expand the project node. Under the **Roles** node, right-click (or select and hold) the role you want to update, and, from the context menu, select **Properties**.
54
54
55
55

56
56
@@ -80,7 +80,7 @@ By using a different value for each service configuration, you do not have to us
80
80
81
81
1. Create or open an Azure cloud service project in Visual Studio.
82
82
83
-
1. In **Solution Explorer**, expand the project node. Under the **Roles** node, right-click the role you want to update, and, from the context menu, select **Properties**.
83
+
1. In **Solution Explorer**, expand the project node. Under the **Roles** node, right-click (or select and hold) the role you want to update, and, from the context menu, select **Properties**.
84
84
85
85

86
86
@@ -142,7 +142,7 @@ By using a different value for each service configuration, you do not have to us
@@ -193,7 +193,7 @@ You can add local file system storage for each instance of a role. The data stor
193
193
194
194
1. Create or open an Azure cloud service project in Visual Studio.
195
195
196
-
1. In **Solution Explorer**, expand the project node. Under the **Roles** node, right-click the role you want to update, and, from the context menu, select **Properties**.
196
+
1. In **Solution Explorer**, expand the project node. Under the **Roles** node, right-click (or select andhold) theroleyouwanttoupdate, and, fromthecontextmenu, select**Properties**.
Copy file name to clipboardExpand all lines: docs/azure/vs-azure-tools-connected-services-storage.md
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -39,7 +39,7 @@ The connected service functionality adds all the needed references and connectio
39
39
40
40
1. Open your project in Visual Studio.
41
41
42
-
1. In **Solution Explorer**, right-click the **Connected Services** node, and, from the context menu, select **Add Connected Service**.
42
+
1. In **Solution Explorer**, right-click (or select and hold) the **Connected Services** node, and, from the context menu, and select **Add Connected Service**.
Copy file name to clipboardExpand all lines: docs/azure/vs-azure-tools-debug-cloud-services-virtual-machines.md
+10-10Lines changed: 10 additions & 10 deletions
Original file line number
Diff line number
Diff line change
@@ -23,15 +23,15 @@ The emulator simulates the Azure Compute service and runs in your local environm
23
23
24
24
### To debug your cloud service on your local computer
25
25
26
-
1. On the menu bar, choose**Debug**, **Start Debugging** to run your Azure cloud service project. As an alternative, you can press F5. You’ll see a message that the Compute Emulator is starting. When the emulator starts, the system tray icon confirms it.
26
+
1. On the menu bar, select**Debug** > **Start Debugging** to run your Azure cloud service project. As an alternative, you can select F5. You’ll see a message that the Compute Emulator is starting. When the emulator starts, the system tray icon confirms it.
27
27
28
28

29
29
30
30
2. Display the user interface for the compute emulator by opening the shortcut menu for the Azure icon in the notification area, and then select **Show Compute Emulator UI**.
31
31
32
32
The left pane of the UI shows the services that are currently deployed to the compute emulator and the role instances that each service is running. You can choose the service or roles to display lifecycle, logging, and diagnostic information in the right pane. If you put the focus in the top margin of an included window, it expands to fill the right pane.
33
33
34
-
3. Step through the application by selecting commands on the **Debug** menu and setting breakpoints in your code. As you step through the application in the debugger, the panes are updated with the current status of the application. When you stop debugging, the application deployment is deleted. If your application includes a web role and you've set the Startup action property to start the web browser, Visual Studio starts your web application in the browser. If you change the number of instances of a role in the service configuration, you must stop your cloud service and then restart debugging so that you can debug these new instances of the role.
34
+
3. Step through the application by choosing commands on the **Debug** menu and setting breakpoints in your code. As you step through the application in the debugger, the panes are updated with the current status of the application. When you stop debugging, the application deployment is deleted. If your application includes a web role and you've set the Startup action property to start the web browser, Visual Studio starts your web application in the browser. If you change the number of instances of a role in the service configuration, you must stop your cloud service and then restart debugging so that you can debug these new instances of the role.
35
35
36
36
> [!NOTE]
37
37
> When you stop running or debugging your service, the local compute emulator and storage emulator aren't stopped. You must stop them explicitly from the notification area.
@@ -73,7 +73,7 @@ If you enable remote debugging for a cloud service, it doesn't exhibit degraded
73
73
74
74

75
75
76
-
4. To identify the processes to which the debugger is attached, open the Processes dialog box by, on the menu bar, choosing Debug, Windows, Processes. (Keyboard: Ctrl+Alt+Z) To detach a specific process, open its shortcut menu, and then select **Detach Process**. Or, locate the instance node in Server Explorer, find the process, open its shortcut menu, and then select **Detach Process**.
76
+
4. To identify the processes to which the debugger is attached, on the menu bar, select **Debug** > **Windows** > **Processes**, and open the **Processes** dialog box. (Keyboard: Ctrl+Alt+Z) To detach a specific process, open its shortcut menu, and then select **Detach Process**. Or, locate the instance node in Server Explorer, find the process, open its shortcut menu, and then select **Detach Process**.
4. In the **Attach to Process** dialog box, select **Select** to limit the results list to show only the types of code you want to debug. You can debug 32-bit or 64-bit managed code, native code, or both.
122
122
123
123

124
124
125
-
5.Select the processes you want to debug on the virtual machine and then select **Attach**. For example, you might choose the w3wp.exe process if you wanted to debug a web app on the virtual machine. See [Debug One or More Processes in Visual Studio](https://msdn.microsoft.com/library/jj919165.aspx) and [Azure Role Architecture](https://blogs.msdn.microsoft.com/kwill/2011/05/05/windows-azure-role-architecture/) for more information.
125
+
5.Choose the processes you want to debug on the virtual machine and then select **Attach**. For example, you might choose the w3wp.exe process if you wanted to debug a web app on the virtual machine. See [Debug One or More Processes in Visual Studio](https://msdn.microsoft.com/library/jj919165.aspx) and [Azure Role Architecture](https://blogs.msdn.microsoft.com/kwill/2011/05/05/windows-azure-role-architecture/) for more information.
126
126
127
127
## Create a web project and a virtual machine for debugging
128
128
@@ -134,7 +134,7 @@ Visual Studio ASP.NET projects offer an option to create a handy virtual machine
134
134
135
135
1. In Visual Studio, create a new ASP.NET Web Application.
136
136
137
-
2. In the New ASP.NET Project dialog, in the Azure section, choose**Virtual Machine** in the dropdown list box. Leave the **Create remote resources** check box selected. Select **OK** to proceed.
137
+
2. In the New ASP.NET Project dialog, in the Azure section, select**Virtual Machine** in the dropdown list box. Leave the **Create remote resources** check box selected. Select **OK** to proceed.
138
138
139
139
The **Create virtual machine on Azure** dialog box appears.
140
140
@@ -143,13 +143,13 @@ Visual Studio ASP.NET projects offer an option to create a handy virtual machine
143
143
> [!NOTE]
144
144
> You'll be asked to sign in to your Azure account if you're not already signed in.
145
145
146
-
3.Select the various settings for the virtual machine and then select **OK**. See [Virtual Machines](/azure/virtual-machines/) for more information.
146
+
3.Choose the various settings for the virtual machine and then select **OK**. See [Virtual Machines](/azure/virtual-machines/) for more information.
147
147
148
148
The name you enter for DNS name will be the name of the virtual machine.
149
149
150
150

151
151
152
-
Azure creates the virtual machine and then provisions and configures the endpoints, such as Remote Desktop and Web Deploy
152
+
Azure creates the virtual machine and then provisions and configures the endpoints, such as Remote Desktop and Web Deploy.
153
153
154
154
4. After the virtual machine is fully configured, select the virtual machine’s node in Server Explorer.
155
155
@@ -169,15 +169,15 @@ Visual Studio ASP.NET projects offer an option to create a handy virtual machine
169
169
170
170
8. After the project publishes, on the virtual machine's context menu in Server Explorer, select **Attach Debugger...**
171
171
172
-
Azure gets a list of the processes on the virtual machine and shows them in the Attach to Process dialog box.
172
+
Azure gets a list of the processes on the virtual machine and shows them in the **Attach to Process** dialog box.
9. In the **Attach to Process** dialog box, select **Select** to limit the results list to show only the types of code you want to debug. You can debug 32-bit or 64-bit managed code, native code, or both.
177
177
178
178

179
179
180
-
10.Select the processes you want to debug on the virtual machine and then select **Attach**. For example, you might choose the w3wp.exe process if you wanted to debug a web app on the virtual machine. See [Debug One or More Processes in Visual Studio](https://msdn.microsoft.com/library/jj919165.aspx) for more information.
180
+
10.Choose the processes you want to debug on the virtual machine and then select **Attach**. For example, you might choose the w3wp.exe process if you wanted to debug a web app on the virtual machine. See [Debug One or More Processes in Visual Studio](https://msdn.microsoft.com/library/jj919165.aspx) for more information.
Copy file name to clipboardExpand all lines: docs/azure/vs-azure-tools-resources-managing-with-cloud-explorer.md
+4-4Lines changed: 4 additions & 4 deletions
Original file line number
Diff line number
Diff line change
@@ -28,7 +28,7 @@ Like the [Azure portal](https://portal.azure.com), Cloud Explorer is built on th
28
28
29
29
To view the resources associated with an Azure account, you must first add the account to **Cloud Explorer**.
30
30
31
-
1. In **Cloud Explorer**, choose the **Account Management** button.
31
+
1. In **Cloud Explorer**, select the **Account Management** button.
32
32
33
33

34
34
@@ -42,7 +42,7 @@ To view the resources associated with an Azure account, you must first add the a
42
42
43
43

44
44
45
-
1. After selecting the subscriptions whose resources you want to browse, those subscriptions and resources display in the Cloud Explorer.
45
+
1. After selecting the subscriptions whose resources you want to browse, those subscriptions and resources display in the **Cloud Explorer**.
46
46
47
47

48
48
@@ -81,7 +81,7 @@ To view your Azure resources, you can choose either **Resource Types** or **Reso
81
81
82
82
To navigate to an Azure resource and view its information in Cloud Explorer, expand the item's type or associated resource group and then select the resource. When you select a resource, information appears in the two tabs - **Actions** and **Properties** - at the bottom of Cloud Explorer.
83
83
84
-
***Actions** tab - Lists the actions you can take in Cloud Explorer for the selected resource. You can also view these options by right-clicking the resource to view its context menu.
84
+
***Actions** tab - Lists the actions you can take in Cloud Explorer for the selected resource. You can also view these options by right-clicking (or selecting and holding) the resource to view its context menu.
85
85
86
86
***Properties** tab - Shows the properties of the resource, such as its type, locale, and resource group with which it is associated.
87
87
@@ -95,7 +95,7 @@ Additional actions and property values may also appear based on the Azure resour
95
95
96
96
## Find resources in Cloud Explorer
97
97
98
-
To locate resources with a specific name in your Azure account subscriptions, enter the name in the **Search** box in Cloud Explorer.
98
+
To locate resources with a specific name in your Azure account subscriptions, enter the name in the **Search** box in **Cloud Explorer**.
99
99
100
100

0 commit comments