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/how-to-debug-from-a-dll-project.md
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -59,7 +59,7 @@ Native and managed DLL projects have different settings to specify calling apps.
59
59
60
60
- Or, select **Start browser with URL** and fill in the URL of a local ASP.NET app.
61
61
62
-
- For .NET Core DLLs, select**Executable** from the **Launch** dropdown, and then add the fully qualified path and name of the calling app in the **Executable** field.
62
+
- For .NET Core DLLs, the **Debug** Properties page is different. Select**Executable** from the **Launch** dropdown, and then add the fully qualified path and name of the calling app in the **Executable** field.
63
63
64
64
1. Add any necessary command-line arguments in the **Command line arguments** or **Application arguments** field.
Copy file name to clipboardExpand all lines: docs/debugger/how-to-debug-in-mixed-mode.md
+4-4Lines changed: 4 additions & 4 deletions
Original file line number
Diff line number
Diff line change
@@ -23,11 +23,11 @@ ms.workload:
23
23
# How to: Debug in mixed mode
24
24
The following procedures describe how to enable debugging for managed and native code together, also known as mixed-mode debugging. There are two mixed-mode debugging scenarios:
25
25
26
-
- The app that calls the DLL is written in native code, and the DLL is managed.
26
+
- The app that calls a DLL is written in native code, and the DLL is managed.
27
27
28
-
- The app that calls the DLL is written in managed code, and the DLL is in native code. For a tutorial that walks you through this scenario in more detail, see [Debug managed and native code](../debugger/how-to-debug-managed-and-native-code.md).
28
+
- The app that calls a DLL is written in managed code, and the DLL is in native code. For a tutorial that walks you through this scenario in more detail, see [Debug managed and native code](../debugger/how-to-debug-managed-and-native-code.md).
29
29
30
-
You can enable both managed and native debuggers in the calling app's project **Property** pages. The settings differ between native and managed apps.
30
+
You can enable both managed and native debuggers in the calling app project's**Property** pages. The settings differ between native and managed apps.
31
31
32
32
If you don't have access to a calling app's project, you can debug the DLL from the DLL project. You don't need mixed mode to debug just the DLL project. For more information, see [How to: Debug from a DLL project](../debugger/how-to-debug-from-a-dll-project.md).
33
33
@@ -48,7 +48,7 @@ If you don't have access to a calling app's project, you can debug the DLL from
48
48
49
49
## Enable mixed-mode debugging for a managed calling app
50
50
51
-
1. Select the C# or VB project in **Solution Explorer** and select the **Properties** icon, press **Alt**+**Enter**, or right-click and choose **Properties**.
51
+
1. Select the C# or Visual Basic project in **Solution Explorer** and select the **Properties** icon, press **Alt**+**Enter**, or right-click and choose **Properties**.
52
52
53
53
1. Select the **Debug** tab, and then select **Enable native code debugging**.
0 commit comments