/
Microsoft.CodeAnalysis.Analyzers.xml
164 lines (164 loc) · 11.8 KB
/
Microsoft.CodeAnalysis.Analyzers.xml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
<?xml version="1.0"?>
<doc>
<assembly>
<name>Microsoft.CodeAnalysis.Analyzers</name>
</assembly>
<members>
<member name="T:Microsoft.CodeAnalysis.Analyzers.CodeAnalysisDiagnosticsResources">
<summary>
A strongly-typed resource class, for looking up localized strings, etc.
</summary>
</member>
<member name="P:Microsoft.CodeAnalysis.Analyzers.CodeAnalysisDiagnosticsResources.ResourceManager">
<summary>
Returns the cached ResourceManager instance used by this class.
</summary>
</member>
<member name="P:Microsoft.CodeAnalysis.Analyzers.CodeAnalysisDiagnosticsResources.Culture">
<summary>
Overrides the current thread's CurrentUICulture property for all
resource lookups using this strongly typed resource class.
</summary>
</member>
<member name="P:Microsoft.CodeAnalysis.Analyzers.CodeAnalysisDiagnosticsResources.AddLanguageSupportToAnalyzerDescription">
<summary>
Looks up a localized string similar to Diagnostic analyzer is marked as supporting only one language, but the analyzer assembly doesn't seem to refer to any language specific CodeAnalysis assemblies, and so is likely to work for more than one language. Consider adding an additional language argument to DiagnosticAnalyzerAttribute..
</summary>
</member>
<member name="P:Microsoft.CodeAnalysis.Analyzers.CodeAnalysisDiagnosticsResources.AddLanguageSupportToAnalyzerMessage">
<summary>
Looks up a localized string similar to Diagnostic analyzer '{0}' may be able to support both C# and Visual Basic. Consider adding an argument to DiagnosticAnalyzerAttribute for '{1}' language support..
</summary>
</member>
<member name="P:Microsoft.CodeAnalysis.Analyzers.CodeAnalysisDiagnosticsResources.AddLanguageSupportToAnalyzerTitle">
<summary>
Looks up a localized string similar to Recommend adding language support to diagnostic analyzer..
</summary>
</member>
<member name="P:Microsoft.CodeAnalysis.Analyzers.CodeAnalysisDiagnosticsResources.ApplyDiagnosticAnalyzerAttribute_1">
<summary>
Looks up a localized string similar to Apply DiagnosticAnalyzer attribute for '{0}'..
</summary>
</member>
<member name="P:Microsoft.CodeAnalysis.Analyzers.CodeAnalysisDiagnosticsResources.ApplyDiagnosticAnalyzerAttribute_2">
<summary>
Looks up a localized string similar to Apply DiagnosticAnalyzer attribute for both '{0}' and '{1}'..
</summary>
</member>
<member name="P:Microsoft.CodeAnalysis.Analyzers.CodeAnalysisDiagnosticsResources.DoNotStorePerCompilationDataOntoFieldsDescription">
<summary>
Looks up a localized string similar to Instance of a diagnostic analyzer might outlive the lifetime of compilation. Hence, storing per-compilation data, such as symbols, into the fields of a diagnostic analyzer might cause stale compilations to stay alive and cause memory leaks. Instead, you should store this data on a separate type instantiatied in a compilation start action, registered using '{0}.{1}' API. An instance of this type will be created per-compilation and it won't outlive compilation's lifetime, hence avoiding memory leaks..
</summary>
</member>
<member name="P:Microsoft.CodeAnalysis.Analyzers.CodeAnalysisDiagnosticsResources.DoNotStorePerCompilationDataOntoFieldsMessage">
<summary>
Looks up a localized string similar to Avoid storing per-compilation data of type '{0}' into the fields of a diagnostic analyzer..
</summary>
</member>
<member name="P:Microsoft.CodeAnalysis.Analyzers.CodeAnalysisDiagnosticsResources.DoNotStorePerCompilationDataOntoFieldsTitle">
<summary>
Looks up a localized string similar to Avoid storing per-compilation data into the fields of a diagnostic analyzer..
</summary>
</member>
<member name="P:Microsoft.CodeAnalysis.Analyzers.CodeAnalysisDiagnosticsResources.InternalImplementationOnlyDescription">
<summary>
Looks up a localized string similar to The author of this interface did not intend to have third party implementations of this interface and reserves the right to change it. Implementing this interface could therefore result in a source or binary compatibility issue with a future version of this interface..
</summary>
</member>
<member name="P:Microsoft.CodeAnalysis.Analyzers.CodeAnalysisDiagnosticsResources.InternalImplementationOnlyMessage">
<summary>
Looks up a localized string similar to Type {0} cannot implement interface {1} because {1} is not available for public implementation..
</summary>
</member>
<member name="P:Microsoft.CodeAnalysis.Analyzers.CodeAnalysisDiagnosticsResources.InternalImplementationOnlyTitle">
<summary>
Looks up a localized string similar to "Only internal implementations of this interface are allowed.".
</summary>
</member>
<member name="P:Microsoft.CodeAnalysis.Analyzers.CodeAnalysisDiagnosticsResources.InvalidReportDiagnosticDescription">
<summary>
Looks up a localized string similar to ReportDiagnostic should only be invoked with supported DiagnosticDescriptors that are returned from DiagnosticAnalyzer.SupportedDiagnostics property. Otherwise, the reported diagnostic will be filtered out by the analysis engine..
</summary>
</member>
<member name="P:Microsoft.CodeAnalysis.Analyzers.CodeAnalysisDiagnosticsResources.InvalidReportDiagnosticMessage">
<summary>
Looks up a localized string similar to ReportDiagnostic invoked with an unsupported DiagnosticDescriptor '{0}'..
</summary>
</member>
<member name="P:Microsoft.CodeAnalysis.Analyzers.CodeAnalysisDiagnosticsResources.InvalidReportDiagnosticTitle">
<summary>
Looks up a localized string similar to ReportDiagnostic invoked with an unsupported DiagnosticDescriptor..
</summary>
</member>
<member name="P:Microsoft.CodeAnalysis.Analyzers.CodeAnalysisDiagnosticsResources.InvalidSyntaxKindTypeArgumentDescription">
<summary>
Looks up a localized string similar to DiagnosticAnalyzer's language-specific Register methods, such as RegisterSyntaxNodeAction, RegisterCodeBlockStartAction and RegisterCodeBlockEndAction, expect a language-specific 'SyntaxKind' type argument for it's '{0}' type parameter. Otherwise, the registered analyzer action can never be invoked during analysis..
</summary>
</member>
<member name="P:Microsoft.CodeAnalysis.Analyzers.CodeAnalysisDiagnosticsResources.InvalidSyntaxKindTypeArgumentMessage">
<summary>
Looks up a localized string similar to Type argument '{0}' for type parameter '{1}' of method '{2}' is not a SyntaxKind enum..
</summary>
</member>
<member name="P:Microsoft.CodeAnalysis.Analyzers.CodeAnalysisDiagnosticsResources.InvalidSyntaxKindTypeArgumentTitle">
<summary>
Looks up a localized string similar to Invalid type argument for DiagnosticAnalyzer's Register method..
</summary>
</member>
<member name="P:Microsoft.CodeAnalysis.Analyzers.CodeAnalysisDiagnosticsResources.MissingAttributeMessage">
<summary>
Looks up a localized string similar to Missing '{0}' attribute..
</summary>
</member>
<member name="P:Microsoft.CodeAnalysis.Analyzers.CodeAnalysisDiagnosticsResources.MissingDiagnosticAnalyzerAttributeDescription">
<summary>
Looks up a localized string similar to Non-abstract sub-types of DiagnosticAnalyzer should be marked with DiagnosticAnalyzerAttribute(s). The argument to this attribute(s), if any, determine the supported languages for the analyzer. Analyzer types without this attribute will be ignored by the analysis engine..
</summary>
</member>
<member name="P:Microsoft.CodeAnalysis.Analyzers.CodeAnalysisDiagnosticsResources.MissingDiagnosticAnalyzerAttributeTitle">
<summary>
Looks up a localized string similar to Missing diagnostic analyzer attribute..
</summary>
</member>
<member name="P:Microsoft.CodeAnalysis.Analyzers.CodeAnalysisDiagnosticsResources.MissingKindArgumentToRegisterActionDescription">
<summary>
Looks up a localized string similar to You must specify at least one syntax/symbol kinds of interest while registering a syntax/symbol analyzer action. Otherwise, the registered action will be dead code and will never be invoked during analysis..
</summary>
</member>
<member name="P:Microsoft.CodeAnalysis.Analyzers.CodeAnalysisDiagnosticsResources.MissingKindArgumentToRegisterActionMessage">
<summary>
Looks up a localized string similar to Specify at least one '{0}' of interest while registering a {1} analyzer action..
</summary>
</member>
<member name="P:Microsoft.CodeAnalysis.Analyzers.CodeAnalysisDiagnosticsResources.MissingKindArgumentToRegisterActionTitle">
<summary>
Looks up a localized string similar to Missing kind argument while registering an analyzer action..
</summary>
</member>
<member name="P:Microsoft.CodeAnalysis.Analyzers.CodeAnalysisDiagnosticsResources.UnsupportedSymbolKindArgumentToRegisterActionMessage">
<summary>
Looks up a localized string similar to SymbolKind '{0}' is not supported for symbol analyzer actions..
</summary>
</member>
<member name="P:Microsoft.CodeAnalysis.Analyzers.CodeAnalysisDiagnosticsResources.UnsupportedSymbolKindArgumentToRegisterActionTitle">
<summary>
Looks up a localized string similar to Unsupported SymbolKind argument while registering a symbol analyzer action..
</summary>
</member>
<member name="P:Microsoft.CodeAnalysis.Analyzers.CodeAnalysisDiagnosticsResources.UseLocalizableStringsInDescriptorDescription">
<summary>
Looks up a localized string similar to If your diagnostic analyzer and it's reported diagnostics need to be localizable, then the supported DiagnosticDescriptors used for constructing the diagnostics must also be localizable. If so, then localizable argument(s) must be provided for parameter 'title' (and optionally 'description') to the diagnostic descriptor constructor to ensure that the descriptor is localizable..
</summary>
</member>
<member name="P:Microsoft.CodeAnalysis.Analyzers.CodeAnalysisDiagnosticsResources.UseLocalizableStringsInDescriptorMessage">
<summary>
Looks up a localized string similar to Consider providing localizable arguments of type '{0}' to diagnostic descriptor constructor to ensure the descriptor is localizable..
</summary>
</member>
<member name="P:Microsoft.CodeAnalysis.Analyzers.CodeAnalysisDiagnosticsResources.UseLocalizableStringsInDescriptorTitle">
<summary>
Looks up a localized string similar to Provide localizable arguments to diagnostic descriptor constructor..
</summary>
</member>
</members>
</doc>