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/debugger/remote-debugging-azure-app-service.md
+10-9Lines changed: 10 additions & 9 deletions
Original file line number
Diff line number
Diff line change
@@ -25,7 +25,7 @@ This article describes how to attach the Visual Studio debugger to an ASP.NET Co
25
25
26
26
## Enable remote debugging
27
27
28
-
Before you can debug this issue with Visual Studio, you must enable the remote debugging feature on the App Service. This setting will allow the Visual Studio debugger to connect to the main App Service web hosting process.
28
+
Before you can debug this issue with Visual Studio, you must enable the remote debugging feature on the App Service. This setting allows the Visual Studio debugger to connect to the main App Service web hosting process.
29
29
30
30
1. Sign into your own [Azure portal](https://portal.azure.com/).
31
31
@@ -45,16 +45,14 @@ Your app service instance now supports remote debugging through Visual Studio.
45
45
46
46
## Configure debugging settings
47
47
48
-
Make sure you have completed the following steps in Visual Studio before debugging an app in Azure to ensure success.
49
-
50
-
1. First, make sure you have successfully built your project at least one time. A successful build ensures the source code and any necessary compiled files are ready to go. If your application is running locally, make sure to stop the app.
48
+
1. Build your app without errors. Stop your app if it's running locally.
51
49
52
50
> [!NOTE]
53
51
> Make sure the state of your local code matches what was deployed to Azure. This ensures that the local symbol files and source code line up with the deployed app.
54
52
55
53
1. Select **Debug > Options** from the top Visual Studio menu. Ensure that **Enable Just My code** is *unchecked* (as shown below), and then select **OK**.
56
54
57
-
Changing this setting allows Visual Studio to debug the optimized code that was deployed to Azure using the necessary symbol files from your local bin folder. Symbol files are used by the debugger as a bridge between compiled, executing code and the source code in Visual Studio, which is why it's important that your local source code matched the deploy app.
55
+
Changing this setting allows Visual Studio to debug the optimized code that was deployed to Azure using the necessary symbol files from your local bin folder. Symbol files are used by the debugger as a bridge between compiled, executing code and the source code in Visual Studio. Matching symbol files are required for remote debugging.
58
56
59
57
:::image type="content" source="../debugger/media/vs-2022/visual-studio-remote-debug-settings.png" alt-text="A screenshot of the Visual Studio debugging settings.":::
60
58
@@ -70,14 +68,17 @@ Make sure you have completed the following steps in Visual Studio before debuggi
70
68
71
69
1. Locate and select the App Service instance you created in the previous step, and then choose **OK**.
72
70
73
-
1. The `w3wp.exe` process should appear in the list of available processes to connect to, which is the main process of the Azure App Service that hosts the deployed application. Select that process and then choose **Attach** in the bottom right to connect the Visual Studio debugger.
71
+
1. The `w3wp.exe` process should appear in the list of available processes to connect to. `w3wp.exe` is the main process of the Azure App Service that hosts the deployed application. Select the `w3wp.exe`process and then choose **Attach** in the bottom right.
74
72
75
73
:::image type="content" source="../debugger/media/vs-2022/visual-studio-remote-debug-attach-to-process.png" alt-text="A screenshot of the attach to process features." lightbox="../debugger/media/vs-2022/visual-studio-remote-debug-attach-to-process.png":::
76
74
77
-
1. In a C# application file such as `Index.cshtml.cs`, set a breakpoint by clicking in the left margin. (Or, right-click and choose **Breakpoint** > **Insert breakpoint**.)
75
+
1. In a C# application file such as `Index.cshtml.cs`, set a breakpoint by clicking in the left margin. Alternatively, right-click and choose **Breakpoint** > **Insert breakpoint**.
78
76
79
-
1.Take action in the web appto hit the breakpoint. If you're attached to the process but can't hit the breakpoint, make sure your publish profile in Visual Studio is set to a Debug configuration instead of a Release configuration.
77
+
1.In the web app, navigate to the endpoint with the breakpoint. If you're attached to the process but can't hit the breakpoint, make sure your publish profile in Visual Studio is set to a Debug configuration instead of a Release configuration.
80
78
81
-
1.(Optional) you can also verify that Visual Studio has loaded the symbol files for your debugging session. Navigate to **Debug > Windows > Modules** to open the modules window. This window should indicate that the symbol files were successfully loaded after the **Just my code** configuration changes you made earlier.
79
+
1. Optional: To verify that Visual Studio has loaded the symbol files for your debugging session. Navigate to **Debug > Windows > Modules** to open the modules window. This window indicates that the symbol files were successfully loaded after the **Just my code** configuration changes you made earlier.
82
80
83
81
:::image type="content" source="../debugger/media/vs-2022/visual-studio-symbol-files.png" alt-text="A screenshot of the symbol files window.":::
82
+
83
+
> [!NOTE]
84
+
> For subsequent debugging of the app service, select the select **Debug** > **Reattach to w3wp.exe** or use the Shift+Alt+P hot keys.
- Sign *contoso.vsix* with a certificate stored in a secure USB drive specifying file digest algorithm (-fd), timestamp server (-t), and a custom output path (-o) for the signed VSIX.
Copy file name to clipboardExpand all lines: docs/ide/optimize-visual-studio-startup-time.md
+2-2Lines changed: 2 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -26,7 +26,7 @@ If Visual Studio detects slow startup, a pop-up message appears, alerting you to
26
26
27
27
The dialog box lists the extensions and tools windows that are affecting startup performance. You can change extension and tool window settings to improve startup performance.
28
28
29
-
## <aname="extensions" />To change extension settings to improve startup, solution load, and typing performance
29
+
## <aname="extensions"></a> To change extension settings to improve startup, solution load, and typing performance
30
30
31
31
1. Open the **Performance Manager** dialog box by choosing **Help** > **Visual Studio Performance Manager** from the menu bar.
32
32
@@ -38,7 +38,7 @@ The dialog box lists the extensions and tools windows that are affecting startup
38
38
39
39
You can always re-enable the extension for future sessions by using the **Extension Manager** or the **Visual Studio Performance Manager** dialog box.
40
40
41
-
## <aname="tool-windows" />To change tool window settings to improve startup time
41
+
## <aname="tool-windows"></a> To change tool window settings to improve startup time
42
42
43
43
1. Open the **Performance Manager** dialog box by choosing **Help** > **Visual Studio Performance Manager** from the menu bar.
Copy file name to clipboardExpand all lines: docs/modeling/analyze-and-model-your-architecture.md
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -72,7 +72,7 @@ Use domain-specific language to:
72
72
Learn more:
73
73
-[Modeling SDK for Visual Studio - Domain-Specific Languages](../modeling/modeling-sdk-for-visual-studio-domain-specific-languages.md)
74
74
75
-
## <aname="VersionSupport" />Edition support for architecture and modeling tools
75
+
## <aname="VersionSupport"></a> Edition support for architecture and modeling tools
76
76
77
77
Visual Studio is available in several editions. Not all of these provide support for the architecture and modeling tools. The following table shows the availability of each tool.
0 commit comments