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/ide/managing-application-settings-dotnet.md
+2-2Lines changed: 2 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -78,9 +78,9 @@ If any user-scoped settings are changed during run time, for example in testing
78
78
79
79
We strongly recommend that you use the `My.Settings` object and the default *.settings* file to access settings. This is because you can use the **Settings Designer** to assign properties to settings, and, additionally, user settings are automatically saved before application shutdown. However, your Visual Basic application can access settings directly. In that case you have to access the `MySettings` class and use a custom *.settings* file in the root of the project. You must save the user settings before ending the application, as you would do for a C# application; this is described in the following section.
80
80
81
-
<!-- markdownlint-disable MD003 -->
81
+
<!-- markdownlint-disable MD003 MD020 -->
82
82
## Access or change application settings at run time in C#
83
-
<!-- markdownlint-enable MD003 -->
83
+
<!-- markdownlint-enable MD003 MD020 -->
84
84
85
85
In languages other than Visual Basic, such as C#, you must access the `Settings` class directly, as shown in the following [!INCLUDE[csprcs](../data-tools/includes/csprcs_md.md)] example.
The Visual Studio integrated development environment (IDE) is a collection of development tools exposed through a common user interface. Some of the tools are shared with other [!INCLUDE[vsprvs](../includes/vsprvs-md.md)] languages, and some, such as the C# compiler, are unique to Visual C#. This topic provides links to the most important Visual C# tools.
@@ -43,6 +44,7 @@ The Visual Studio integrated development environment (IDE) is a collection of de
43
44
|[Managing Application Resources (.NET)](../ide/managing-application-resources-dotnet.md)|Shows how to add or edit resources for your project, such as strings, images, icons, audio, and files.|
Debugging F# is similar to debugging any managed language, with a few exceptions:
25
-
26
-
- The **Autos** window does not display F# variables.
27
-
28
-
- Edit and Continue is not supported for F#. Editing F# code during a debugging session is possible but should be avoided. Because code changes are not applied during the debugging session, editing F# code during debugging will cause a mismatch between the source code and the code being debugged.
29
-
30
-
- The debugger does not recognize F# expressions. To enter an expression in a debugger window or a dialog box during F# debugging, you must translate the expression into C# syntax. When you translate an F# expression into C#, make sure to remember that C# uses == as the comparison operator for equality and that F# uses a single =.
Debugging F# is similar to debugging any managed language, with a few exceptions:
26
+
27
+
- The **Autos** window does not display F# variables.
28
+
29
+
- Edit and Continue is not supported for F#. Editing F# code during a debugging session is possible but should be avoided. Because code changes are not applied during the debugging session, editing F# code during debugging will cause a mismatch between the source code and the code being debugged.
30
+
31
+
- The debugger does not recognize F# expressions. To enter an expression in a debugger window or a dialog box during F# debugging, you must translate the expression into C# syntax. When you translate an F# expression into C#, make sure to remember that C# uses == as the comparison operator for equality and that F# uses a single =.
You can change the format in which a value is displayed in the **Watch** window using format specifiers. You can also use format specifiers in the **Immediate** window, the **Command** window, and even in source windows. If you pause on an expression in those windows, the result will appear in a DataTip. DataTips will reflect the format specifier in the DataTip display.
35
-
36
-
To use a format specifier, type the expression followed by a comma. After the comma, add the appropriate specifier.
37
-
38
-
## Using Format Specifiers
39
-
If you have the following code:
40
-
41
-
```
42
-
{
43
-
int my_var1 = 0x0065;
44
-
int my_var2 = 0x0066;
45
-
int my_var3 = 0x0067;
46
-
}
47
-
```
48
-
49
-
Add the `my_var1` variable to the Watch window (while debugging, **Debug / Windows / Watch / Watch 1**) and set the display to hexadecimal (in the **Watch** window, right-click the variable and select **Hexadecimal Display**). Now the **Watch** window shows that it contains the value 0x0065. To see this value expressed as a decimal integer instead of a hexadecimal integer, in the Name column, after the variable name, add the decimal format specifier: **, d**. The Value column now displays the decimal value 101
|ac|Force evaluation of an expression. This can be useful when implicit evaluation of properties and implicit function calls is turned off. See [Side Effects and Expressions](http://msdn.microsoft.com/library/e1f8a6ea-9e19-481d-b6bd-df120ad3bf4e).|Message “Implicit function evaluation is turned off by the user”|\<value>|
59
-
|d|decimal integer|0x0065|101|
60
-
|dynamic|Displays the specified object using a Dynamic View|Displays all the members of the object, including the Dynamic View|Displays only the Dynamic View|
61
-
|h|hexadecimal integer|61541|0x0000F065|
62
-
|nq|string with no quotes|"My String"|My String|
63
-
|hidden|Displays all public and non-public members|Displays public members|Displays all members|
64
-
|raw|Displays item as it appears in the raw item node. Valid on proxy objects only.|Dictionary\<T>|Raw View of Dictionary\<T>|
65
-
|results|Used with a variable of a type that implements IEnumerable or IEnumerable\<T>, usually the result of a query expression. Displays only the members that contain the query result.|Displays all the members.|Displays the members the meet the conditions of the query.|
66
-
67
-
## See Also
68
-
[Watch and QuickWatch Windows](../debugger/watch-and-quickwatch-windows.md)
You can change the format in which a value is displayed in the **Watch** window using format specifiers. You can also use format specifiers in the **Immediate** window, the **Command** window, and even in source windows. If you pause on an expression in those windows, the result will appear in a DataTip. DataTips will reflect the format specifier in the DataTip display.
36
+
37
+
To use a format specifier, type the expression followed by a comma. After the comma, add the appropriate specifier.
38
+
39
+
## Using Format Specifiers
40
+
41
+
If you have the following code:
42
+
43
+
```csharp
44
+
{
45
+
intmy_var1=0x0065;
46
+
intmy_var2=0x0066;
47
+
intmy_var3=0x0067;
48
+
}
49
+
```
50
+
51
+
Add the `my_var1` variable to the Watch window (while debugging, **Debug / Windows / Watch / Watch 1**) and set the display to hexadecimal (in the **Watch** window, right-click the variable and select **Hexadecimal Display**). Now the **Watch** window shows that it contains the value 0x0065. To see this value expressed as a decimal integer instead of a hexadecimal integer, in the Name column, after the variable name, add the decimal format specifier: **, d**. The Value column now displays the decimal value 101
|ac|Force evaluation of an expression. This can be useful when implicit evaluation of properties and implicit function calls is turned off. See [Side Effects and Expressions](http://msdn.microsoft.com/library/e1f8a6ea-9e19-481d-b6bd-df120ad3bf4e).|Message “Implicit function evaluation is turned off by the user”|\<value>|
62
+
|d|decimal integer|0x0065|101|
63
+
|dynamic|Displays the specified object using a Dynamic View|Displays all the members of the object, including the Dynamic View|Displays only the Dynamic View|
64
+
|h|hexadecimal integer|61541|0x0000F065|
65
+
|nq|string with no quotes|"My String"|My String|
66
+
|hidden|Displays all public and non-public members|Displays public members|Displays all members|
67
+
|raw|Displays item as it appears in the raw item node. Valid on proxy objects only.|Dictionary\<T>|Raw View of Dictionary\<T>|
68
+
|results|Used with a variable of a type that implements IEnumerable or IEnumerable\<T>, usually the result of a query expression. Displays only the members that contain the query result.|Displays all the members.|Displays the members the meet the conditions of the query.|
69
+
70
+
## See Also
71
+
72
+
-[Watch and QuickWatch Windows](../debugger/watch-and-quickwatch-windows.md)
0 commit comments