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/ai/installation.md
+38-38Lines changed: 38 additions & 38 deletions
Original file line number
Diff line number
Diff line change
@@ -82,27 +82,27 @@ Then, we need to verify whether Python 3.5 is installed correctly, and upgrade p
82
82
83
83
-**Windows**
84
84
85
-
```cmd
86
-
C:\Users\test>python -V
87
-
Python 3.5.4
85
+
```cmd
86
+
C:\Users\test>python -V
87
+
Python 3.5.4
88
88
89
-
C:\Users\test>pip3.5 -V
90
-
pip 9.0.1 from c:\users\test\appdata\local\programs\python\python35\lib\site-packages (python 3.5)
89
+
C:\Users\test>pip3.5 -V
90
+
pip 9.0.1 from c:\users\test\appdata\local\programs\python\python35\lib\site-packages (python 3.5)
91
91
92
-
C:\Users\test>python -m pip install -U pip
93
-
```
92
+
C:\Users\test>python -m pip install -U pip
93
+
```
94
94
95
95
-**macOS**
96
96
97
-
```bash
98
-
MyMac:~ test$ python3.5 -V
99
-
Python 3.5.4
97
+
```bash
98
+
MyMac:~ test$ python3.5 -V
99
+
Python 3.5.4
100
100
101
-
MyMac:~ test$ pip3.5 -V
102
-
pip 9.0.1 from /Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5/site-packages (python 3.5)
101
+
MyMac:~ test$ pip3.5 -V
102
+
pip 9.0.1 from /Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5/site-packages (python 3.5)
103
103
104
-
MyMac:~ test$ python3.5 -m pip install -U pip
105
-
```
104
+
MyMac:~ test$ python3.5 -m pip install -U pip
105
+
```
106
106
107
107
### Python on Visual Studio
108
108
@@ -156,15 +156,15 @@ To install MXNet, run the following command in a terminal:
156
156
157
157
- With GPU
158
158
159
-
```bash
160
-
pip3.5 install mxnet-cu80==0.12.0
161
-
```
159
+
```bash
160
+
pip3.5 install mxnet-cu80==0.12.0
161
+
```
162
162
163
163
- Without GPU
164
164
165
-
```bash
166
-
pip3.5 install mxnet==0.12.0
167
-
```
165
+
```bash
166
+
pip3.5 install mxnet==0.12.0
167
+
```
168
168
169
169
### Keras
170
170
@@ -197,33 +197,33 @@ To install PyTorch, run the following command in a terminal:
197
197
198
198
-**Windows**
199
199
200
-
There's no official wheel package yet. You can download a third-party package from [Anaconda](https://anaconda.org/pytorch/repo?type=all) or [University of California](https://www.lfd.uci.edu/~gohlke/pythonlibs/#pytorch).
200
+
There's no official wheel package yet. You can download a third-party package from [Anaconda](https://anaconda.org/pytorch/repo?type=all) or [University of California](https://www.lfd.uci.edu/~gohlke/pythonlibs/#pytorch).
201
201
202
-
- Decompress it to your home directory, for example, *C:\Users\test\pytorch*.
203
-
- Add *C:\Users\test\pytorch\Lib\site-packages* to the %PYTHONPATH% environment variable.
202
+
- Decompress it to your home directory, for example, *C:\Users\test\pytorch*.
203
+
- Add *C:\Users\test\pytorch\Lib\site-packages* to the %PYTHONPATH% environment variable.
Copy file name to clipboardExpand all lines: docs/code-quality/ca1507.md
+3-3Lines changed: 3 additions & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -35,9 +35,9 @@ Rule CA1507 flags the use of a `string` literal as an argument to a method or co
35
35
36
36
- The constant value of the `string` literal matches either of the following:
37
37
38
-
- The name of a parameter of the method, lambda, or local function within which the method or constructor is being invoked.
38
+
- The name of a parameter of the method, lambda, or local function within which the method or constructor is being invoked.
39
39
40
-
- The name of a property of the type within which the method or constructor is being invoked.
40
+
- The name of a property of the type within which the method or constructor is being invoked.
41
41
42
42
- The argument corresponds to a `string`-typed parameter of the method or the constructor that's being invoked (that is, there is no conversion involved at the call site).
43
43
@@ -81,4 +81,4 @@ It's safe to suppress a violation of this rule if you're not concerned about the
Copy file name to clipboardExpand all lines: docs/code-quality/in-source-suppression-overview.md
+7-7Lines changed: 7 additions & 7 deletions
Original file line number
Diff line number
Diff line change
@@ -61,17 +61,17 @@ The properties of the attribute include:
61
61
62
62
- **Scope** - The target on which the warning is being suppressed. If the target is not specified, it is set to the target of the attribute. Supported [scopes](xref:System.Diagnostics.CodeAnalysis.SuppressMessageAttribute.Scope) include the following:
63
63
64
-
- `module`
64
+
- `module`
65
65
66
-
- `resource`
66
+
- `resource`
67
67
68
-
- `type`
68
+
- `type`
69
69
70
-
- `member`
70
+
- `member`
71
71
72
-
- `namespace` - This scope suppresses warnings against the namespace itself. It does not suppress warnings against types within the namespace.
72
+
- `namespace` - This scope suppresses warnings against the namespace itself. It does not suppress warnings against types within the namespace.
73
73
74
-
- `namespaceanddescendants` - (New for Visual Studio 2019) This scope suppresses warnings in a namespace and all its descendant symbols. The `namespaceanddescendants` value is only valid for Roslyn analyzers, and is ignored by binary, FxCop-based static analysis.
74
+
- `namespaceanddescendants` - (New for Visual Studio 2019) This scope suppresses warnings in a namespace and all its descendant symbols. The `namespaceanddescendants` value is only valid for Roslyn analyzers, and is ignored by binary, FxCop-based static analysis.
75
75
76
76
- **Target** - An identifier that is used to specify the target on which the warning is being suppressed. It must contain a fully qualified item name.
77
77
@@ -165,4 +165,4 @@ The global suppression file maintains suppressions that are either global-level
Copy file name to clipboardExpand all lines: docs/code-quality/use-roslyn-analyzers.md
+16-16Lines changed: 16 additions & 16 deletions
Original file line number
Diff line number
Diff line change
@@ -104,40 +104,40 @@ There are multiple ways to suppress rule violations:
104
104
105
105
- From the **Analyze** menu
106
106
107
-
Select **Analyze** > **Run Code Analysis and Suppress Active Issues** on the menu bar to suppress all current violations. This is sometimes referred to as "baselining".
107
+
Select **Analyze** > **Run Code Analysis and Suppress Active Issues** on the menu bar to suppress all current violations. This is sometimes referred to as "baselining".
108
108
109
109
- From **Solution Explorer**
110
110
111
-
To suppress a violation in **Solution Explorer**, set the rule's severity to **None**.
111
+
To suppress a violation in **Solution Explorer**, set the rule's severity to **None**.
112
112
113
113
- From the **rule set editor**
114
114
115
-
To suppress a violation from the rule set editor, uncheck the box next to its name or set **Action** to **None**.
115
+
To suppress a violation from the rule set editor, uncheck the box next to its name or set **Action** to **None**.
116
116
117
117
- From the **code editor**
118
118
119
-
To suppress a violation from the code editor, place the cursor in the line of code with the violation and press **Ctrl**+**.** to open the **Quick Actions** menu. Select **Suppress CAXXXX** > **in Source/in Suppression File**.
119
+
To suppress a violation from the code editor, place the cursor in the line of code with the violation and press **Ctrl**+**.** to open the **Quick Actions** menu. Select **Suppress CAXXXX** > **in Source/in Suppression File**.
120
120
121
-
121
+
122
122
123
123
- From the **Error List**
124
124
125
-
You can suppress one or many diagnostics from the **Error List** by selecting the ones you want to suppress, and then right-clicking and selecting **Suppress** > **In Source/In Suppression File**.
125
+
You can suppress one or many diagnostics from the **Error List** by selecting the ones you want to suppress, and then right-clicking and selecting **Suppress** > **In Source/In Suppression File**.
126
126
127
-
- If you suppress **In Source**, the **Preview Changes** dialog opens and shows a preview of the C# [#pragma warning](/dotnet/csharp/language-reference/preprocessor-directives/preprocessor-pragma-warning) or Visual Basic [#Disable warning](/dotnet/visual-basic/language-reference/directives/directives) directive that's added to the source code.
127
+
- If you suppress **In Source**, the **Preview Changes** dialog opens and shows a preview of the C# [#pragma warning](/dotnet/csharp/language-reference/preprocessor-directives/preprocessor-pragma-warning) or Visual Basic [#Disable warning](/dotnet/visual-basic/language-reference/directives/directives) directive that's added to the source code.
128
128
129
-
129
+
130
130
131
-
- If you select **In Suppression File**, the **Preview Changes** dialog opens and shows a preview of the <xref:System.Diagnostics.CodeAnalysis.SuppressMessageAttribute> attribute that's added to the global suppressions file.
131
+
- If you select **In Suppression File**, the **Preview Changes** dialog opens and shows a preview of the <xref:System.Diagnostics.CodeAnalysis.SuppressMessageAttribute> attribute that's added to the global suppressions file.
132
132
133
-
133
+
134
134
135
-
In the **Preview Changes** dialog, select **Apply**.
135
+
In the **Preview Changes** dialog, select **Apply**.
136
136
137
-
> [!NOTE]
138
-
> If you don't see the **Suppress** menu option in **Solution Explorer**, the violation is likely coming from build and not live analysis. The **Error List** displays diagnostics, or rule violations, from both live code analysis and build. Since the build diagnostics can be stale, for example, if you've edited the code to fix the violation but haven't rebuilt, you cannot suppress these diagnostics from the **Error List**. Diagnostics from live analysis, or IntelliSense, are always up-to-date with current sources and can be suppressed from the **Error List**. To exclude *build* diagnostics from your selection, switch the **Error List** source filter from **Build + IntelliSense** to **Intellisense Only**. Then, select the diagnostics you want to suppress and proceed as described previously.
139
-
>
140
-
> 
137
+
> [!NOTE]
138
+
> If you don't see the **Suppress** menu option in **Solution Explorer**, the violation is likely coming from build and not live analysis. The **Error List** displays diagnostics, or rule violations, from both live code analysis and build. Since the build diagnostics can be stale, for example, if you've edited the code to fix the violation but haven't rebuilt, you cannot suppress these diagnostics from the **Error List**. Diagnostics from live analysis, or IntelliSense, are always up-to-date with current sources and can be suppressed from the **Error List**. To exclude *build* diagnostics from your selection, switch the **Error List** source filter from **Build + IntelliSense** to **Intellisense Only**. Then, select the diagnostics you want to suppress and proceed as described previously.
139
+
>
140
+
> 
141
141
142
142
## Command-line usage
143
143
@@ -177,4 +177,4 @@ In a .NET Core project, if you add a reference to a project that has NuGet analy
177
177
-[Overview of Roslyn analyzers in Visual Studio](../code-quality/roslyn-analyzers-overview.md)
178
178
-[Submit a Roslyn analyzer bug](https://github.com/dotnet/roslyn-analyzers/issues)
0 commit comments