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/general-debugging-options-dialog-box.md
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -112,7 +112,7 @@ Tells the debugger to verify that a source file matches the version of the sourc
112
112
Sends all debugger messages that would ordinarily appear in the **Output** window to the **Immediate** window instead.
113
113
114
114
**Show raw structure of objects in variables windows**:
115
-
Turns off all object structure view customizations. For more information about view customizations, see [Create custom views of .managed objects](../debugger/create-custom-views-of-dot-managed-objects.md).
115
+
Turns off all object structure view customizations. For more information about view customizations, see [Create custom views of managed objects](../debugger/create-custom-views-of-managed-objects.md).
116
116
117
117
**Suppress JIT optimization on module load (Managed only)**:
118
118
Disables the JIT optimization of managed code when a module is loaded and JIT is compiled while the debugger is attached. Disabling optimization may make it easier to debug some problems, although at the expense of performance. If you are using Just My Code, suppressing JIT optimization can cause non-user code to appear as user code ("My Code"). For more information, see [JIT optimization and debugging](../debugger/jit-optimization-and-debugging.md).
Copy file name to clipboardExpand all lines: docs/debugger/using-debuggertypeproxy-attribute.md
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -62,5 +62,5 @@ Visual Basic does not have open type syntax, so you cannot do the same thing in
62
62
## See Also
63
63
64
64
-[Using the DebuggerDisplay Attribute](../debugger/using-the-debuggerdisplay-attribute.md)
65
-
-[Create custom views of .managed objects](../debugger/create-custom-views-of-dot-managed-objects.md)
65
+
-[Create custom views of managed objects](../debugger/create-custom-views-of-managed-objects.md)
66
66
-[Enhancing Debugging with the Debugger Display Attributes](/dotnet/framework/debug-trace-profile/enhancing-debugging-with-the-debugger-display-attributes)
-[Create custom views of managed objects](../debugger/create-custom-views-of-dot-managed-objects.md)
179
+
-[Create custom views of managed objects](../debugger/create-custom-views-of-managed-objects.md)
180
180
-[Format specifiers in C#](../debugger/format-specifiers-in-csharp.md)
181
181
-[Enhancing Debugging with the Debugger Display Attributes](/dotnet/framework/debug-trace-profile/enhancing-debugging-with-the-debugger-display-attributes)
Copy file name to clipboardExpand all lines: docs/debugger/viewing-data-in-the-debugger.md
+2-2Lines changed: 2 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -26,7 +26,7 @@ The [!INCLUDE[vsprvs](../code-quality/includes/vsprvs_md.md)] debugger provides
26
26
27
27
## Create custom views of data in variable windows and DataTips
28
28
29
-
Many of the [debugger windows](../debugger/debugger-windows.md), such as the **Autos** and **Watch** windows, allow you to inspect variables. You can customize how C++ types, managed objects, and your own types are shown in the debugger variable windows and in [DataTips](../debugger/view-data-values-in-data-tips-in-the-code-editor.md). For more information, see [Create custom views of C++ objects](../debugger/create-custom-views-of-native-objects.md) and [Create custom views of objects](../debugger/create-custom-views-of-dot-managed-objects.md).
29
+
Many of the [debugger windows](../debugger/debugger-windows.md), such as the **Autos** and **Watch** windows, allow you to inspect variables. You can customize how C++ types, managed objects, and your own types are shown in the debugger variable windows and in [DataTips](../debugger/view-data-values-in-data-tips-in-the-code-editor.md). For more information, see [Create custom views of C++ objects](../debugger/create-custom-views-of-native-objects.md) and [Create custom views of managed objects](../debugger/create-custom-views-of-managed-objects.md).
30
30
31
31
## Create custom visualizers
32
32
@@ -36,4 +36,4 @@ The [!INCLUDE[vsprvs](../code-quality/includes/vsprvs_md.md)] debugger provides
36
36
37
37
-[First look at the debugger](../debugger/debugger-feature-tour.md)
Copy file name to clipboardExpand all lines: docs/vs-2015/debugger/general-debugging-options-dialog-box.md
+4-4Lines changed: 4 additions & 4 deletions
Original file line number
Diff line number
Diff line change
@@ -52,7 +52,7 @@ The**Tools / Options / Debugging / General** page lets you set the following opt
52
52
Automatically shows the **Disassembly** window when you try to debug code for which source is unavailable.
53
53
54
54
**Enable breakpoint filters**
55
-
Enables you to set filters on breakpoints so that they will affect only specific processes, threads, or computers.
55
+
Enables you to set filters on breakpoints so that they affect only specific processes, threads, or computers.
56
56
57
57
**Enable the exception assistant**
58
58
For managed code only. Managed exceptions open the exception assistant dialog box. See [Exception Assistant](https://msdn.microsoft.com/library/992892ac-9d52-44cc-bf09-b44bfc5befeb).
@@ -103,7 +103,7 @@ The**Tools / Options / Debugging / General** page lets you set the following opt
103
103
Sends all debugger messages that would ordinarily appear in the **Output** window to the **Immediate** window instead.
104
104
105
105
**Show raw structure of objects in variables windows**
106
-
Turns off all object structure view customizations. For more information about view customizations, see [Create custom views of managed objects](../debugger/create-custom-views-of-dot-managed-objects.md).
106
+
Turns off all object structure view customizations. For more information about view customizations, see [Create custom views of managed objects](../debugger/create-custom-views-of-managed-objects.md).
107
107
108
108
**Suppress JIT optimization on module load (managed only)**
109
109
Disables the JIT optimization of managed code when a module is loaded and JIT is compiled while the debugger is attached. Disabling optimization may make it easier to debug some problems, although at the expense of performance. If you are using Just My Code, suppressing JIT optimization can cause non-user code to appear as user code ("My Code").
@@ -117,7 +117,7 @@ The**Tools / Options / Debugging / General** page lets you set the following opt
117
117
**Load dll exports**
118
118
Loads dll export tables. Symbol information from dll export tables can be useful if you are working with Windows messages, Windows procedures (WindowProcs), COM objects, or marshaling, or any dll for which you do not have symbols. Reading dll export information involves some overhead. Therefore, this capability is turned off by default.
119
119
120
-
To see what symbols are available in the export table of a dll, use `dumpbin /exports`. Symbols are available for any 32-bit system dll. By reading the `dumpbin /exports` output, you can see the exact function name, including non-alphanumeric characters. This is useful for setting a breakpoint on a function. Function names from dll export tables might appear truncated elsewhere in the debugger. The calls are listed in the calling order, with the current function (the most deeply nested) at the top. For more information, see [dumpbin /exports](https://msdn.microsoft.com/library/2971ab7e-4ee6-478b-9c85-cda42a4ce1bf).
120
+
To see what symbols are available in the export table of a dll, use `dumpbin /exports`. Symbols are available for any 32-bit system dll. By reading the `dumpbin /exports` output, you can see the exact function name, including non-alphanumeric characters. This is useful for setting a breakpoint on a function. Function names from dll export tables might appear truncated elsewhere in the debugger. The calls are listed in the calling order, with the current function (the most deeply nested) at the top. For more information, see [dump bin /exports](https://msdn.microsoft.com/library/2971ab7e-4ee6-478b-9c85-cda42a4ce1bf).
121
121
122
122
**Show parallel stacks diagram bottom-up**
123
123
Controls the direction in which stacks are displayed in the **Parallel Stacks** window.
@@ -137,7 +137,7 @@ The**Tools / Options / Debugging / General** page lets you set the following opt
137
137
**Use Native Compatibility Mode**
138
138
When this option is selected, the debugger uses the Visual Studio 2010 native debugger instead of the new native debugger.
139
139
140
-
You should use this option when you are debugging .NET C++ code, because the new debugging engine does not support evaluating .NET C++ expressions. However, enabling Native Compatibility Mode disables many features that depend on the current debugger implementation to operate. For example, the legacy engine lacks many visualizers for built-in types like `std::string` in Visual Studio 2015 projects. Please use Visual Studio 2013 projects for the optimal debugging experience in these cases.
140
+
You should use this option when you are debugging .NET C++ code, because the new debugging engine does not support evaluating .NET C++ expressions. However, enabling Native Compatibility Mode disables many features that depend on the current debugger implementation to operate. For example, the legacy engine lacks many visualizers for built-in types like `std::string` in Visual Studio 2015 projects. Use Visual Studio 2013 projects for the optimal debugging experience in these cases.
141
141
142
142
**Use the legacy C# and VB expression evaluators**
143
143
The debugger will use the Visual Studio 2013 C#/VB expression evaluators instead of the Visual Studio 2015 Roslyn-based expression evaluators.
With the [!INCLUDE[vsprvs](../includes/vsprvs-md.md)] debugger, you can debug a Web application transparently on the local computer or a remote server. This means that the debugger functions the same way and allows you to use the same features on either computer. For remote debugging to work correctly, however, there are some prerequisites.
0 commit comments