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/watch-and-quickwatch-windows.md
+6-6Lines changed: 6 additions & 6 deletions
Original file line number
Diff line number
Diff line change
@@ -67,7 +67,7 @@ Add the values of the three variables to the **Watch** window as follows:
67
67
68
68
You should see the variable values changing as you iterate through the `for` loop.
69
69
70
-
If you're programming in native code, you may sometimes need to qualify the context of a variable name or an expression that has a variable name. The context is the function, source file, and module where a variable is located. If you have to qualify the context, you can use the context operator syntax. For more information, see [Context Operator (C++)](../debugger/context-operator-cpp.md).
70
+
If you're programming in native code, you may sometimes need to qualify the context of a variable name or an expression that has a variable name. The context is the function, source file, and module where a variable is located. If you have to qualify the context, you can use the context operator syntax. For more information, see [Context operator (C++)](../debugger/context-operator-cpp.md).
71
71
72
72
## Observe expressions with the Watch window
73
73
@@ -105,7 +105,7 @@ A tooltip provides information about why the expression wasn't evaluated if you
105
105
106
106
- An error occurred as the expression was being evaluated. For example, a time-out might have occurred, or a variable might have been out of scope.
107
107
108
-
- The expression has a function call, which could trigger a side effect in the application (see [Side effects and expressions](#bkmk_sideEffects)).
108
+
- The expression has a function call, which could trigger a side effect in the application (see the [Side effects and expressions](#bkmk_sideEffects) section).
109
109
110
110
- You've turned off automatic evaluation of properties and implicit function calls by the debugger (by choosing **Tools** > **Options** > **Debugging** > **General**, then clearing **Enable property evaluation and other implicit function calls**). The expression can't be automatically evaluated then.
111
111
@@ -127,7 +127,7 @@ An expression known to have side effects is evaluated only once, when you first
Evaluatingthemembersofa**DynamicView**canhavesideeffects. Foranexplanationofwhatsideeffectsare, seethe [Sideeffectsandexpressions](#bkmk_sideEffects) section. ForC#, thedebuggerdoesn't automatically reevaluate the values shown in the **Dynamic View** when you step to a new line of code. For Visual Basic, expressions added through the **Dynamic View** are automatically refreshed.
0 commit comments