Skip to content

Commit 53f412d

Browse files
authored
Merge pull request #7044 from MicrosoftDocs/repo_sync_working_branch
Confirm merge from repo_sync_working_branch to master to sync with https://github.com/MicrosoftDocs/visualstudio-docs (branch master)
2 parents ca6c221 + 0779655 commit 53f412d

File tree

41 files changed

+169
-164
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

41 files changed

+169
-164
lines changed

docs/ai/installation.md

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -28,10 +28,9 @@ You can download the tools from the [Visual Studio Marketplace](https://marketpl
2828
2. In the **Extensions and Updates** dialog box, select **Online** on the left-hand side.
2929
3. In the search box in the upper right-hand corner, type or enter "tools for ai".
3030
4. Select **Visual Studio Tools for AI** from the results.
31-
5. Click **Download**.
31+
5. Select **Download**.
3232

3333
## Prepare your local machine
34-
3534
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.
3635

3736
> [!NOTE]

docs/azure/vs-azure-tools-configure-roles-for-cloud-service.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -30,7 +30,7 @@ You can configure an Azure cloud service from Solution Explorer in Visual Studio
3030

3131
1. Create or open an Azure cloud service project in Visual Studio.
3232

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**.
3434

3535
![Solution Explorer project context menu](./media/vs-azure-tools-configure-roles-for-cloud-service/solution-explorer-project-context-menu.png)
3636

@@ -50,7 +50,7 @@ To improve the performance of your cloud service, you can change the number of i
5050

5151
1. Create or open an Azure cloud service project in Visual Studio.
5252

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**.
5454

5555
![Solution Explorer Azure role context menu](./media/vs-azure-tools-configure-roles-for-cloud-service/solution-explorer-azure-role-context-menu.png)
5656

@@ -80,7 +80,7 @@ By using a different value for each service configuration, you do not have to us
8080

8181
1. Create or open an Azure cloud service project in Visual Studio.
8282

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**.
8484

8585
![Solution Explorer Azure role context menu](./media/vs-azure-tools-configure-roles-for-cloud-service/solution-explorer-azure-role-context-menu.png)
8686

@@ -142,7 +142,7 @@ By using a different value for each service configuration, you do not have to us
142142

143143
1. Create or open an Azure cloud service project in Visual Studio.
144144

145-
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**.
145+
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**.
146146

147147
![Solution Explorer Azure role context menu](./media/vs-azure-tools-configure-roles-for-cloud-service/solution-explorer-azure-role-context-menu.png)
148148

@@ -193,7 +193,7 @@ You can add local file system storage for each instance of a role. The data stor
193193

194194
1. Create or open an Azure cloud service project in Visual Studio.
195195

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 and hold) the role you want to update, and, from the context menu, select **Properties**.
197197

198198
![Solution Explorer Azure role context menu](./media/vs-azure-tools-configure-roles-for-cloud-service/solution-explorer-azure-role-context-menu.png)
199199

@@ -248,7 +248,7 @@ using (FileStream writeStream = File.Create(filePath))
248248

249249
To view the file created by the code in the previous section, follow these steps:
250250

251-
1. In the Windows notification area, right-click the Azure icon, and, from the context menu, select **Show Compute Emulator UI**.
251+
1. In the Windows notification area, right-click (or select and hold) the Azure icon, and, from the context menu, select **Show Compute Emulator UI**.
252252

253253
![Show Azure compute emulator](./media/vs-azure-tools-configure-roles-for-cloud-service/show-compute-emulator.png)
254254

docs/azure/vs-azure-tools-connected-services-storage.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -39,7 +39,7 @@ The connected service functionality adds all the needed references and connectio
3939

4040
1. Open your project in Visual Studio.
4141

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**.
4343

4444
![Add Azure connected service](./media/vs-azure-tools-connected-services-storage/add-connected-service.png)
4545

docs/azure/vs-azure-tools-debug-cloud-services-virtual-machines.md

Lines changed: 10 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -23,15 +23,15 @@ The emulator simulates the Azure Compute service and runs in your local environm
2323

2424
### To debug your cloud service on your local computer
2525

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.
2727

2828
![Azure emulator in the system tray](./media/vs-azure-tools-debug-cloud-services-virtual-machines/IC783828.png)
2929

3030
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**.
3131

3232
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.
3333

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.
3535

3636
> [!NOTE]
3737
> 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
7373

7474
![Select code type dialog box](./media/vs-azure-tools-debug-cloud-services-virtual-machines/IC718346.png)
7575

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**.
7777

7878
![Debug Processes](./media/vs-azure-tools-debug-cloud-services-virtual-machines/IC690787.gif)
7979

@@ -114,15 +114,15 @@ You can debug programs that run on Azure virtual machines by using Server Explor
114114

115115
3. After the remote debugging extension finishes installing, open the virtual machine's context menu and select **Attach Debugger...**
116116

117-
Azure gets a list of the processes on the virtual machine and shows them in the Attach to Process dialog box.
117+
Azure gets a list of the processes on the virtual machine and shows them in the **Attach to Process** dialog box.
118118

119119
![Attach debugger command](./media/vs-azure-tools-debug-cloud-services-virtual-machines/IC746722.png)
120120

121121
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.
122122

123123
![Select code type dialog box](./media/vs-azure-tools-debug-cloud-services-virtual-machines/IC718346.png)
124124

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.
126126

127127
## Create a web project and a virtual machine for debugging
128128

@@ -134,7 +134,7 @@ Visual Studio ASP.NET projects offer an option to create a handy virtual machine
134134

135135
1. In Visual Studio, create a new ASP.NET Web Application.
136136

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.
138138

139139
The **Create virtual machine on Azure** dialog box appears.
140140

@@ -143,13 +143,13 @@ Visual Studio ASP.NET projects offer an option to create a handy virtual machine
143143
> [!NOTE]
144144
> You'll be asked to sign in to your Azure account if you're not already signed in.
145145
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.
147147

148148
The name you enter for DNS name will be the name of the virtual machine.
149149

150150
![Create virtual machine on Azure dialog box](./media/vs-azure-tools-debug-cloud-services-virtual-machines/IC746724.png)
151151

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.
153153

154154
4. After the virtual machine is fully configured, select the virtual machine’s node in Server Explorer.
155155

@@ -169,15 +169,15 @@ Visual Studio ASP.NET projects offer an option to create a handy virtual machine
169169

170170
8. After the project publishes, on the virtual machine's context menu in Server Explorer, select **Attach Debugger...**
171171

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.
173173

174174
![Attach debugger command](./media/vs-azure-tools-debug-cloud-services-virtual-machines/IC746722.png)
175175

176176
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.
177177

178178
![Select code type dialog box](./media/vs-azure-tools-debug-cloud-services-virtual-machines/IC718346.png)
179179

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.
181181

182182
## Next steps
183183

docs/azure/vs-azure-tools-emulator-express-debug-run.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ When you create an Azure project in Azure SDK 2.3 or later, Emulator Express is
1717

1818
1. Create or open an Azure cloud service project in Visual Studio.
1919

20-
1. In **Solution Explorer**, right-click the project, and, from the context menu, select **Properties**.
20+
1. In Solution Explorer, right-click (or select and hold) the project, and, from the context menu, select **Properties**.
2121

2222
1. In the projects properties pages, select the **Web** tab.
2323

docs/azure/vs-azure-tools-resources-managing-with-cloud-explorer.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -28,7 +28,7 @@ Like the [Azure portal](https://portal.azure.com), Cloud Explorer is built on th
2828

2929
To view the resources associated with an Azure account, you must first add the account to **Cloud Explorer**.
3030

31-
1. In **Cloud Explorer**, choose the **Account Management** button.
31+
1. In **Cloud Explorer**, select the **Account Management** button.
3232

3333
![Cloud Explorer Azure account settings icon](./media/vs-azure-tools-resources-managing-with-cloud-explorer/azure-account-settings.png)
3434

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

4343
![Cloud Explorer: select Azure subscriptions to display](./media/vs-azure-tools-resources-managing-with-cloud-explorer/select-subscriptions.png)
4444

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**.
4646

4747
![Cloud Explorer resource listing for an Azure account](./media/vs-azure-tools-resources-managing-with-cloud-explorer/resources-listed.png)
4848

@@ -81,7 +81,7 @@ To view your Azure resources, you can choose either **Resource Types** or **Reso
8181

8282
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.
8383

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.
8585

8686
* **Properties** tab - Shows the properties of the resource, such as its type, locale, and resource group with which it is associated.
8787

@@ -95,7 +95,7 @@ Additional actions and property values may also appear based on the Azure resour
9595

9696
## Find resources in Cloud Explorer
9797

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**.
9999

100100
![Finding resources in Cloud Explorer](./media/vs-azure-tools-resources-managing-with-cloud-explorer/search-for-resources.png)
101101

0 commit comments

Comments
 (0)