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/code-quality/ca1720-identifiers-should-not-contain-type-names.md
+2-2Lines changed: 2 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -132,7 +132,7 @@ In addition, the names of a parameter are also checked against the following lan
132
132
Replace the language-specific data type identifier in the name of the member with a term that better describes its meaning, a language-independent equivalent, or a more generic term, such as 'value'.
133
133
134
134
## When to suppress warnings
135
-
Occasional use of type-based parameter and member names might be appropriate. However, for new development, no known scenarios occur where you should suppress a warning from this rule. For libraries that have previous shipped, you might have to suppress a warning from this rule.
135
+
Occasional use of type-based parameter and member names might be appropriate. However, for new development, no known scenarios occur where you should suppress a warning from this rule. For libraries that have previously shipped, you might have to suppress a warning from this rule.
136
136
137
137
## Related rules
138
138
[CA1709: Identifiers should be cased correctly](../code-quality/ca1709-identifiers-should-be-cased-correctly.md)
@@ -141,4 +141,4 @@ In addition, the names of a parameter are also checked against the following lan
141
141
142
142
[CA1707: Identifiers should not contain underscores](../code-quality/ca1707-identifiers-should-not-contain-underscores.md)
143
143
144
-
[CA1719: Parameter names should not match member names](../code-quality/ca1719-parameter-names-should-not-match-member-names.md)
144
+
[CA1719: Parameter names should not match member names](../code-quality/ca1719-parameter-names-should-not-match-member-names.md)
Copy file name to clipboardExpand all lines: docs/code-quality/cpp-core-guidelines-warnings.md
+2-2Lines changed: 2 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -122,10 +122,10 @@ These macros correspond to the rule sets and expand into a space-separated lists
122
122
The Microsoft Visual C++ compiler has a limited support for the GSL suppress attribute. It can be used to suppress warnings on expression and block statements inside of a function.
123
123
124
124
```cpp
125
-
//Supress only warnings from the 'r.11' rule in expression.
125
+
//Suppress only warnings from the 'r.11' rule in expression.
126
126
[[gsl::suppress(r.11)]] newint;
127
127
128
-
//Supress all warnings from the 'r' rule group (resource management) in block.
128
+
//Suppress all warnings from the 'r' rule group (resource management) in block.
Copy file name to clipboardExpand all lines: docs/code-quality/how-to-enable-and-disable-automatic-code-analysis-for-managed-code.md
+8-3Lines changed: 8 additions & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
---
2
-
title: "How to: Enable and Disable Automatic Code Analysis for Managed Code"
3
-
ms.date: 09/28/2018
2
+
title: Enable or disable code analysis
3
+
ms.date: 10/25/2018
4
4
ms.prod: visual-studio-dev15
5
5
ms.technology: vs-ide-code-analysis
6
6
ms.topic: conceptual
@@ -12,14 +12,19 @@ ms.workload:
12
12
---
13
13
# How to: Enable and disable automatic code analysis for managed code
14
14
15
-
You can configure code analysis to run after each build of a managed code project. You can set different code analysis properties for each build configuration, for example, debug and release.
15
+
You can configure (static) code analysis to run after each build of a managed code project. You can set different code analysis properties for each build configuration, for example, debug and release.
16
+
17
+
This article applies only to static code analysis and not live code analysis using [Roslyn code analyzers](roslyn-analyzers-overview.md).
16
18
17
19
## To enable or disable automatic code analysis
18
20
19
21
1. In **Solution Explorer**, right-click the project, and then choose **Properties**.
20
22
21
23
1. In the properties dialog box for the project, choose the **Code Analysis** tab.
22
24
25
+
> [!TIP]
26
+
> Newer project types such as .NET Core and .NET Standard applications don't have a **Code Analysis** tab. Static code analysis is not available for these project types, but you can still get live code analysis using [Roslyn code analyzers](roslyn-analyzers-overview.md). To suppress warnings from Roslyn code analyzers, see the note at the end of this article.
27
+
23
28
1. Specify the build type in **Configuration** and the target platform in **Platform**.
24
29
25
30
1. To enable or disable automatic code analysis, select or clear the **Enable Code Analysis on Build** check box.
Copy file name to clipboardExpand all lines: docs/code-quality/using-the-cpp-core-guidelines-checkers.md
+2-2Lines changed: 2 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -129,10 +129,10 @@ These macros correspond to the rule sets and expand into a space-separated list
129
129
The Microsoft Visual C++ compiler has a limited support for the GSL suppress attribute. It can be used to suppress warnings on expression and block statements inside of a function.
130
130
131
131
```cpp
132
-
//Supress only warnings from the 'r.11' rule in expression.
132
+
//Suppress only warnings from the 'r.11' rule in expression.
133
133
[[gsl::suppress(r.11)]] newint;
134
134
135
-
//Supress all warnings from the 'r' rule group (resource management) in block.
135
+
//Suppress all warnings from the 'r' rule group (resource management) in block.
Use this page of the Options dialog box to specify whether or not files are automatically backed up. This page also allows you to specify whether or not modified files are restored when the integrated development environment (IDE) shuts down unexpectedly. You can access this dialog box by selecting the **Tools** menu and choosing **Options**, and then selecting the **Environment** folder and choosing the **AutoRecover** page. If this page does not appear in the list, select **Show all setting** in the **Options** dialog box.
23
+
# AutoRecover, Environment, Options dialog box
24
+
25
+
Use this page in the **Options** dialog box to specify whether to automatically back up files or not. This page also lets you specify if you want to restore modified files if Visual Studio shuts down unexpectedly.
26
+
27
+
Access this dialog box by selecting the **Tools** menu, selecting **Options**, and then selecting **Environment** > **AutoRecover**. If this page doesn't appear in the list, select **Show all setting** in the **Options** dialog box.
26
28
27
29
> [!NOTE]
28
-
> The dialog boxes and menu commands you see might differ from those described in Help depending on your active settings or edition. To change your settings, choose Import and Export Settings on the Tools menu. For more information, see [Personalize the Visual Studio IDE](../../ide/personalizing-the-visual-studio-ide.md).
30
+
> The dialog boxes and menu commands you see might differ from those described in Help depending on your active settings or edition. To change your settings, choose **Import and Export Settings** on the **Tools** menu. For more information, see [Personalize the Visual Studio IDE](../../ide/personalizing-the-visual-studio-ide.md).
31
+
32
+
**Save AutoRecover information every [n] minutes**
33
+
34
+
Use this option to customize how often a file is automatically saved in the editor. For previously saved files, a copy of the file is saved in *%USERPROFILE%\Documents\Visual Studio \<version>\Backup Files\\<projectname>*. If the file is new and you haven't saved it yet, the file is autosaved using a randomly generated file name.
29
35
30
-
**Save AutoRecover information every \<n> minutes**
31
-
Use this option to customize how often a file is automatically saved in the editor. For previously saved files, a copy of the file is saved in \\...\My Documents\Visual Studio \<*version*>\Backup Files\\<*projectname*>. If the file is new and has not been manually saved, the file is auto-saved using a randomly generated file name.
36
+
**Keep AutoRecover information for [n] days**
32
37
33
-
**Keep AutoRecover information for \<n> days**
34
-
Use this option to specify how long Visual Studio keeps files created for autorecovery.
38
+
Use this option to specify how long Visual Studio keeps files created for autorecovery.
Copy file name to clipboardExpand all lines: docs/ide/reference/documents-environment-options-dialog-box.md
+33-24Lines changed: 33 additions & 24 deletions
Original file line number
Diff line number
Diff line change
@@ -7,7 +7,6 @@ ms.topic: reference
7
7
f1_keywords:
8
8
- "VS.Environment.Documents"
9
9
- "VS.ToolsOptionsPages.Environment.Documents"
10
-
- "VS.ToolsOptionsPag.Environment.Documents"
11
10
helpviewer_keywords:
12
11
- "Documents Environment Options dialog box"
13
12
- "defaults, directories"
@@ -36,50 +35,60 @@ ms.workload:
36
35
- "multiple"
37
36
---
38
37
# Documents, Environment, Options Dialog Box
38
+
39
39
Use this page of the **Options** dialog box to control the display of documents in the integrated development environment (IDE) and manage external changes to documents and files. You can access this dialog box by clicking **Options** on the **Tools** menu and then selecting **Documents** in the **Environment** node. If **Documents** does not appear in the list, select **Show all settings** in the **Options** dialog box.
40
40
41
41
> [!NOTE]
42
42
> The options available in dialog boxes, and the names and locations of menu commands you see, might differ from what is described in Help depending on your active settings or edition. To change your settings, choose **Import and Export Settings** on the **Tools** menu. For more information, see [Personalize the Visual Studio IDE](../../ide/personalizing-the-visual-studio-ide.md).
43
43
44
+
**Reuse current document window, if saved**
45
+
46
+
When selected, closes your current document if it has been saved, and opens a new document in the same window. If your current document has not been saved, it remains open and the new document is opened in a separate window. When this option is cleared, new documents always open in separate windows.
47
+
48
+
If you perform multi-document cut and paste operations infrequently and want to minimize the number of open documents and windows in your working space, try this option.
49
+
50
+
**Detect when file is changed outside the environment**
51
+
52
+
When this option is selected, a message immediately notifies you of changes to an open file that have been made by an editor outside the IDE. The message lets you reload the file from storage.
44
53
45
-
**Reuse current document window, if saved**
46
-
When selected, closes your current document if it has been saved, and opens a new document in the same window. If your current document has not been saved, it remains open and the new document is opened in a separate window. When this option is cleared, new documents always open in separate windows.
54
+
**Auto-load changes, if saved**
47
55
48
-
If you perform multi-document cut and paste operations infrequently and want to minimize the number of open documents and windows in your working space, try this option.
56
+
When you have **Detect when file is changed outside the environment** selected and an open file in the IDE changes outside the IDE, a warning message is generated by default. If this option is enabled, no warning appears and the document is reloaded in the IDE to pick up the external changes.
49
57
50
-
**Detect when file is changed outside the environment**
51
-
When this option is selected, a message immediately notifies you of changes to an open file that have been made by an editor outside the IDE. The message lets you reload the file from storage.
58
+
**Allow editing of read-only files; warn when attempt to save**
52
59
53
-
**Auto-load changes, if saved**
54
-
When you have **Detect when file is changed outside the environment** selected and an open file in the IDE changes outside the IDE, a warning message is generated by default. If this option is enabled, no warning appears and the document is reloaded in the IDE to pick up the external changes.
60
+
When this option is enabled, you can open and edit a read-only file. When you are finished, you must use the **Save As** command to save the file by a new name if you want to save a record of your changes.
55
61
56
-
**Allow editing of read-only files; warn when attempt to save**
57
-
When this option is enabled you can open and edit a read-only file. When you are finished, you must use the **Save As**command to save the file by a new name if you want to save a record of your changes.
62
+
**Open file using directory of currently active document**
58
63
59
-
**Open file using directory of currently active document**
60
-
When selected, this option specifies that the **Open File** dialog box displays the directory of the active document. When this option is cleared, the **Open File** dialog box displays the directory last used to open a file.
64
+
When selected, this option specifies that the **Open File** dialog box displays the directory of the active document. When this option is cleared, the **Open File** dialog box displays the directory last used to open a file.
61
65
62
-
**Check for consistent line endings on load**
63
-
Select this option to have the editor scan the line endings in a file and display a message box if inconsistencies are detected in how line endings are formatted.
66
+
**Check for consistent line endings on load**
64
67
65
-
**Display warning when global undo will modify edited files**
66
-
Select this option to display a message box when the **Global Undo** command will roll back refactoring changes made in files that also were changed after the refactoring operation. Returning a file to its pre-refactoring state might discard subsequent changes made in the file.
68
+
Select this option to have the editor scan the line endings in a file and display a message box if inconsistencies are detected in how line endings are formatted.
67
69
68
-
**Show Miscellaneous files in Solution Explorer**
69
-
Select this option to display the **Miscellaneous Files** node in **Solution Explorer**. Miscellaneous files are files that are not associated with a project or solution but can appear in **Solution Explorer** for your convenience.
70
+
**Display warning when global undo will modify edited files**
71
+
72
+
Select this option to display a message box when the **Global Undo** command will roll back refactoring changes made in files that also were changed after the refactoring operation. Returning a file to its pre-refactoring state might discard subsequent changes made in the file.
73
+
74
+
**Show Miscellaneous files in Solution Explorer**
75
+
76
+
Select this option to display the **Miscellaneous Files** node in **Solution Explorer**. Miscellaneous files are files that are not associated with a project or solution but can appear in **Solution Explorer** for your convenience.
70
77
71
78
> [!NOTE]
72
79
> Select this option to enable the **View in Browser** command on the **File** menu for web documents not included in the active web application.
73
80
74
-
**\<***n***> items saved in the Miscellaneous files project**
75
-
Specifies the number of files to persist in the **MiscellaneousFiles** folder of **Solution Explorer**. These files are listed even if they are no longer open in an editor. You can specify any whole number from 0 to 256. The default number is 0.
81
+
**\<***n***> items saved in the Miscellaneous files project**
82
+
83
+
Specifies the number of files to persist in the **MiscellaneousFiles** folder of **Solution Explorer**. These files are listed even if they are no longer open in an editor. You can specify any whole number from 0 to 256. The default number is 0.
84
+
85
+
For example, if you set this option to 5 and have 10 miscellaneous files open, when you close all 10 files, the first 5 will still be shown in the **Miscellaneous Files** folder.
76
86
77
-
For example, if you set this option to 5 and have 10 miscellaneous files open, when you close all 10 files, the first 5 will still be shown in the **Miscellaneous Files** folder.
87
+
**Save documents as Unicode when data cannot be saved in codepage**
78
88
79
-
**Save documents as Unicode when data cannot be saved in codepage**
80
-
Select this option to cause files containing information incompatible with the selected codepage to be saved as Unicode by default.
89
+
Select this option to cause files containing information incompatible with the selected codepage to be saved as Unicode by default.
# International Settings, Environment, Options Dialog Box
24
+
25
25
The International Settings page allows you to change the default language when you have more than one language version of the integrated development environment (IDE) installed on your machine. You can access this dialog box by selecting **Options** from the **Tools** menu and then choosing **International Settings** from the **Environment** folder. If this page does not appear in the list, select **Show all settings** in the **Options** dialog box.
26
26
27
27
> [!NOTE]
28
28
> The options available in dialog boxes, and the names and locations of menu commands you see, might differ from what is described in Help depending on your active settings or edition. To change your settings, choose **Import and Export Settings** on the **Tools** menu. For more information, see [Personalize the Visual Studio IDE](../../ide/personalizing-the-visual-studio-ide.md).
29
29
30
-
31
30
**Language**
32
31
Lists the available languages for the installed product language versions. This option is unavailable unless you have more than one language version installed on your machine. If multiple languages of products or a mixed language installation of products share the environment, the language selection is changed to **Same as Microsoft Windows**.
33
32
34
33
> [!CAUTION]
35
34
> In a system with multiple languages installed, the Visual C++ build tools (cl.exe, link.exe, nmake.exe, bscmake.exe and related files) are not affected by this setting. These tools use the version for the last language installed. The build tools for the previously installed language are overwritten, because the Visual C++ build tools do not use the satellite DLL model.
36
35
37
-
38
36
## See Also
39
37
40
38
-[Install language packs](../../install/install-visual-studio.md#step-6---install-language-packs-optional)
0 commit comments