12
2021/06/04 14:57:46.270
2021/06/04 14:57:46.258
2022/01/11 09:25:10.250
2021/06/04 14:57:46.270
2021/06/04 14:57:46.270
-2040176723
2021/06/04 14:57:46.270
0
2021/06/04 14:57:46.270
0
2021/06/04 14:57:46.270
0
2021/06/04 14:57:46.270
0
2021/06/04 14:57:46.270
0
2021/06/04 14:57:46.270
0
The file has no header, the header Xml is invalid, or the header is not located at the top of the file.
1
False
All using directives must be placed inside of the namespace.
1
False
The interface must have a documentation header.
5
False
The method must have a documentation header.
7
False
2021/06/04 14:57:46.270
2021/06/04 14:57:46.258
2022/01/11 09:25:10.244
2021/06/04 14:57:46.270
2021/06/04 14:57:46.270
-2040176723
2021/06/04 14:57:46.270
0
2021/06/04 14:57:46.270
0
2021/06/04 14:57:46.270
0
2021/06/04 14:57:46.270
0
2021/06/04 14:57:46.270
0
2021/06/04 14:57:46.270
0
The file has no header, the header Xml is invalid, or the header is not located at the top of the file.
1
False
All using directives must be placed inside of the namespace.
1
False
All using directives must be placed inside of the namespace.
2
False
All using directives must be placed inside of the namespace.
3
False
The interface must have a documentation header.
7
False
The method must have a documentation header.
9
False
The method must have a documentation header.
10
False
Adjacent elements must be separated by a blank line.
10
False
The variable name 'dbAias' begins with a prefix that looks like Hungarian notation. Remove the prefix or add it to the list of allowed prefixes.
10
False
2021/06/04 14:57:46.270
2021/06/04 14:57:46.258
2022/01/11 09:25:10.252
2021/06/04 14:57:46.270
2021/06/04 14:57:46.270
-2040176723
2021/06/04 14:57:46.270
0
2021/06/04 14:57:46.270
0
2021/06/04 14:57:46.270
0
2021/06/04 14:57:46.270
0
2021/06/04 14:57:46.270
0
2021/06/04 14:57:46.270
0
The file has no header, the header Xml is invalid, or the header is not located at the top of the file.
1
False
The comment is empty. Add text to the comment or remove it.
216
8415
8416
216
17
216
18
False
All using directives must be placed inside of the namespace.
1
False
All using directives must be placed inside of the namespace.
2
False
System using directives must be placed before all other using directives.
2
False
All using directives must be placed inside of the namespace.
3
False
All using directives must be placed inside of the namespace.
4
False
All using directives must be placed inside of the namespace.
5
False
All using directives must be placed inside of the namespace.
6
False
All using directives must be placed inside of the namespace.
7
False
All using directives must be placed inside of the namespace.
8
False
The documentation header must not contain blank lines. Use the 'para' tag to insert line breaks within documentation text.
13
False
The summary section in the documentation header must not be empty.
15
False
A single-line comment must be preceded by a blank line or another single-line comment, or must be the first item in its scope. To ignore this error when commenting out a line of code, begin the comment with '////' rather than '//'.
20
False
The code must not contain multiple blank lines in a row.
307
False
The comment must start with a single space. To ignore this error when commenting out a line of code, begin the comment with '////' rather than '//'.
29
872
882
29
9
29
19
False
The field must have a documentation header.
17
False
Field names must not start with an underscore.
17
False
The field must have a documentation header.
19
False
The method must have a documentation header.
21
False
All private methods must be placed after all public methods.
47
False
All private methods must be placed after all public methods.
71
False
All methods must be placed after all fields.
81
False
All private methods must be placed after all public methods.
89
False
All private methods must be placed after all public methods.
115
False
All private methods must be placed after all public methods.
140
False
All private methods must be placed after all public methods.
151
False
All private methods must be placed after all public methods.
161
False
All private methods must be placed after all public methods.
313
False
All private methods must be placed after all public methods.
341
False
The method must have a documentation header.
30
False
Statements or elements wrapped in curly brackets must be followed by a blank line.
39
False
method names begin with an upper-case letter: getCpu.
30
False
The documentation text within the summary tag does not contain any whitespace between words, indicating that it most likely does not follow a proper grammatical structure required for documentation text.
47
False
The documentation text within the summary tag contains incorrectly spelled words: '得到客户序列号'
47
False
The returns section in the documentation header must not be empty.
47
False
Statements or elements wrapped in curly brackets must be followed by a blank line.
55
False
Statements or elements wrapped in curly brackets must be followed by a blank line.
59
False
Statements or elements wrapped in curly brackets must be followed by a blank line.
63
False
Variable names and private field names must start with a lower-case letter: LastKey.
49
False
Variable names and private field names must start with a lower-case letter: TempKey.
50
False
A comment may not be placed within the bracketed statement.
52
False
A comment may not be placed within the bracketed statement.
56
False
A comment may not be placed within the bracketed statement.
60
False
The comment is empty. Add text to the comment or remove it.
51
1667
1668
51
55
51
56
False
Use string.Empty rather than "".
49
False
Invalid spacing around the semicolon.
50
1600
1600
50
38
50
38
False
The comment must start with a single space. To ignore this error when commenting out a line of code, begin the comment with '////' rather than '//'.
50
1601
1610
50
39
50
48
False
Invalid spacing around the semicolon.
51
1666
1666
51
54
51
54
False
Invalid spacing around the closing parenthesis.
52
1723
1731
52
53
52
61
False
The comment must start with a single space. To ignore this error when commenting out a line of code, begin the comment with '////' rather than '//'.
52
1723
1731
52
53
52
61
False
Invalid spacing around the closing parenthesis.
56
1894
1902
56
58
56
66
False
The comment must start with a single space. To ignore this error when commenting out a line of code, begin the comment with '////' rather than '//'.
56
1894
1902
56
58
56
66
False
Invalid spacing around the closing parenthesis.
60
2079
2103
60
51
60
75
False
The comment must start with a single space. To ignore this error when commenting out a line of code, begin the comment with '////' rather than '//'.
60
2079
2103
60
51
60
75
False
The documentation text within the summary tag does not contain any whitespace between words, indicating that it most likely does not follow a proper grammatical structure required for documentation text.
71
False
The documentation text within the summary tag contains incorrectly spelled words: '得到客户序列号'
71
False
The documentation header must contain param tags matching the element's parameter list.
71
False
The returns section in the documentation header must not be empty.
71
False
The variable name 'wLicenseInfo' begins with a prefix that looks like Hungarian notation. Remove the prefix or add it to the list of allowed prefixes.
73
False
Variable names and private field names must start with a lower-case letter: ProID.
71
False
Use string.Empty rather than "".
73
False
The field must have a documentation header.
81
False
Variable names and private field names must start with a lower-case letter: Keys.
81
False
The documentation text within the summary tag does not contain any whitespace between words, indicating that it most likely does not follow a proper grammatical structure required for documentation text.
89
False
The documentation text within the summary tag contains incorrectly spelled words: '加密字符串'
89
False
The documentation text within the param tag does not contain any whitespace between words, indicating that it most likely does not follow a proper grammatical structure required for documentation text.
89
False
The documentation text within the param tag contains incorrectly spelled words: '待加密的字符串'
89
False
The documentation text within the param tag contains incorrectly spelled words: '加密密钥'
89
False
The documentation text within the return tag does not contain any whitespace between words, indicating that it most likely does not follow a proper grammatical structure required for documentation text.
89
False
The documentation text within the return tag contains incorrectly spelled words: '成功返回加密后的字符串', '失敗返回源串'
89
False
The variable name 'dCSP' begins with a prefix that looks like Hungarian notation. Remove the prefix or add it to the list of allowed prefixes.
96
False
The variable name 'mStream' begins with a prefix that looks like Hungarian notation. Remove the prefix or add it to the list of allowed prefixes.
97
False
The variable name 'cStream' begins with a prefix that looks like Hungarian notation. Remove the prefix or add it to the list of allowed prefixes.
98
False
The documentation text within the summary tag does not contain any whitespace between words, indicating that it most likely does not follow a proper grammatical structure required for documentation text.
115
False
The documentation text within the summary tag contains incorrectly spelled words: '解密字符串'
115
False
The documentation text within the param tag does not contain any whitespace between words, indicating that it most likely does not follow a proper grammatical structure required for documentation text.
115
False
The documentation text within the param tag contains incorrectly spelled words: '待解密的字符串'
115
False
The documentation text within the param tag contains incorrectly spelled words: '解密密鑰'
115
False
The documentation text within the return tag does not contain any whitespace between words, indicating that it most likely does not follow a proper grammatical structure required for documentation text.
115
False
The documentation text within the return tag contains incorrectly spelled words: '成功返回解密后的字符串', '失敗返回源串'
115
False
Variable names and private field names must start with a lower-case letter: DCSP.
122
False
The variable name 'mStream' begins with a prefix that looks like Hungarian notation. Remove the prefix or add it to the list of allowed prefixes.
123
False
The variable name 'cStream' begins with a prefix that looks like Hungarian notation. Remove the prefix or add it to the list of allowed prefixes.
124
False
The documentation header must not contain blank lines. Use the 'para' tag to insert line breaks within documentation text.
136
False
The summary section in the documentation header must not be empty.
140
False
The documentation text within the param tag for the '<param name="strLicense" />' parameter must not be empty.
140
False
The returns section in the documentation header must not be empty.
140
False
Use string.Empty rather than "".
142
False
Use string.Empty rather than "".
143
False
The documentation header must not contain blank lines. Use the 'para' tag to insert line breaks within documentation text.
147
False
The summary section in the documentation header must not be empty.
151
False
The documentation header must contain param tags matching the element's parameter list.
151
False
The documentation text within the param tag for the '<param name="strLicense" />' parameter must not be empty.
151
False
The returns section in the documentation header must not be empty.
151
False
Use string.Empty rather than "".
153
False
The documentation header must not contain blank lines. Use the 'para' tag to insert line breaks within documentation text.
156
False
The summary section in the documentation header must not be empty.
161
False
The documentation header must contain param tags matching the element's parameter list.
161
False
The documentation text within the param tag for the '<param name="strLicense" />' parameter must not be empty.
161
False
The documentation text within the param tag for the '<param name="strMAC" />' parameter must not be empty.
161
False
The returns section in the documentation header must not be empty.
161
False
Adjacent elements must be separated by a blank line.
161
False
The body of the if statement must be wrapped in opening and closing curly brackets.
189
False
The body of the else statement must be wrapped in opening and closing curly brackets.
191
False
A documentation header must be preceded by a blank line or must be the first item in its scope.
155
False
Statements or elements wrapped in curly brackets must be followed by a blank line.
166
False
An opening curly bracket must not be followed by a blank line.
173
False
Statements or elements wrapped in curly brackets must be followed by a blank line.
185
False
Statements or elements wrapped in curly brackets must be followed by a blank line.
196
False
Statements or elements wrapped in curly brackets must be followed by a blank line.
204
False
Statements or elements wrapped in curly brackets must be followed by a blank line.
224
False
Statements or elements wrapped in curly brackets must be followed by a blank line.
233
False
Statements or elements wrapped in curly brackets must be followed by a blank line.
241
False
A single-line comment must be preceded by a blank line or another single-line comment, or must be the first item in its scope. To ignore this error when commenting out a line of code, begin the comment with '////' rather than '//'.
250
False
Statements or elements wrapped in curly brackets must be followed by a blank line.
256
False
Variable names and private field names must start with a lower-case letter: LastString.
167
False
The variable name 'wCustomerName' begins with a prefix that looks like Hungarian notation. Remove the prefix or add it to the list of allowed prefixes.
161
False
The variable name 'iLen' begins with a prefix that looks like Hungarian notation. Remove the prefix or add it to the list of allowed prefixes.
177
False
Use string.Empty rather than "".
165
False
Use string.Empty rather than "".
167
False
Use string.Empty rather than "".
175
False
Use string.Empty rather than "".
178
False
Use string.Empty rather than "".
197
False
Use string.Empty rather than "".
206
False
Use string.Empty rather than "".
217
False
Use string.Empty rather than "".
226
False
Use string.Empty rather than "".
240
False
Use string.Empty rather than "".
242
False
Use string.Empty rather than "".
255
False
The comment must start with a single space. To ignore this error when commenting out a line of code, begin the comment with '////' rather than '//'.
215
8263
8396
215
17
215
150
False
The comment must start with a single space. To ignore this error when commenting out a line of code, begin the comment with '////' rather than '//'.
250
9943
9974
250
17
250
48
False
The comment must start with a single space. To ignore this error when commenting out a line of code, begin the comment with '////' rather than '//'.
251
9993
10040
251
17
251
64
False
The method must have a documentation header.
260
False
Statements or elements wrapped in curly brackets must be followed by a blank line.
267
False
Statements or elements wrapped in curly brackets must be followed by a blank line.
271
False
Statements or elements wrapped in curly brackets must be followed by a blank line.
275
False
Statements or elements wrapped in curly brackets must be followed by a blank line.
279
False
Statements or elements wrapped in curly brackets must be followed by a blank line.
283
False
Statements or elements wrapped in curly brackets must be followed by a blank line.
287
False
Statements or elements wrapped in curly brackets must be followed by a blank line.
291
False
Statements or elements wrapped in curly brackets must be followed by a blank line.
295
False
Statements or elements wrapped in curly brackets must be followed by a blank line.
299
False
Statements or elements wrapped in curly brackets must be followed by a blank line.
303
False
The variable name 'iKey' begins with a prefix that looks like Hungarian notation. Remove the prefix or add it to the list of allowed prefixes.
262
False
Field names must not start with an underscore.
263
False
Variable names and private field names must start with a lower-case letter: _Seed.
263
False
The documentation header must not contain blank lines. Use the 'para' tag to insert line breaks within documentation text.
309
False
The summary section in the documentation header must not be empty.
313
False
The documentation text within the param tag for the '<param name="wMacID" />' parameter must not be empty.
313
False
The returns section in the documentation header must not be empty.
313
False
The body of the if statement must be wrapped in opening and closing curly brackets.
317
False
Statements or elements wrapped in curly brackets must be followed by a blank line.
332
False
The variable name 'mMacID' begins with a prefix that looks like Hungarian notation. Remove the prefix or add it to the list of allowed prefixes.
318
False
The variable name 'wMacID' begins with a prefix that looks like Hungarian notation. Remove the prefix or add it to the list of allowed prefixes.
313
False
The variable name 'wLicenseInfo' begins with a prefix that looks like Hungarian notation. Remove the prefix or add it to the list of allowed prefixes.
325
False
Use string.Empty rather than "".
318
False
The documentation header must not contain blank lines. Use the 'para' tag to insert line breaks within documentation text.
336
False
The summary section in the documentation header must not be empty.
341
False
The param tags in the documentation header must match the element's parameter list.
341
False
The documentation text within the param tag for the '<param name="wLicenseInfo" />' parameter must not be empty.
341
False
The documentation text within the param tag for the '<param name="ProID" />' parameter must not be empty.
341
False
The documentation text within the param tag does not contain any whitespace between words, indicating that it most likely does not follow a proper grammatical structure required for documentation text.
341
False
The documentation text within the param tag contains incorrectly spelled words: '没有加密的客户识别码'
341
False
Adjacent elements must be separated by a blank line.
341
False
A documentation header must be preceded by a blank line or must be the first item in its scope.
335
False
The variable name 'wLicenseInfo' begins with a prefix that looks like Hungarian notation. Remove the prefix or add it to the list of allowed prefixes.
341
False
The variable name 'wMacID' begins with a prefix that looks like Hungarian notation. Remove the prefix or add it to the list of allowed prefixes.
341
False
The variable name 'wCustomerName' begins with a prefix that looks like Hungarian notation. Remove the prefix or add it to the list of allowed prefixes.
341
False
The documentation header must not contain blank lines. Use the 'para' tag to insert line breaks within documentation text.
350
False
The summary section in the documentation header must not be empty.
352
False
A C# document may only contain a single class at the root level unless all of the classes are partial and are of the same type.
352
False
The documentation text within the summary tag does not contain any whitespace between words, indicating that it most likely does not follow a proper grammatical structure required for documentation text.
360
False
The documentation text within the summary tag contains incorrectly spelled words: '得到版本号'
360
False
The documentation text within the param tag does not contain any whitespace between words, indicating that it most likely does not follow a proper grammatical structure required for documentation text.
360
False
The documentation text within the param tag contains incorrectly spelled words: '主版本号'
360
False
The documentation text within the param tag contains incorrectly spelled words: '次版本号'
360
False
The returns section in the documentation header must not be empty.
360
False
Variable names and private field names must start with a lower-case letter: Ver1.
360
False
Variable names and private field names must start with a lower-case letter: Ver2.
360
False
Use string.Empty rather than "".
364
False
The documentation text within the summary tag does not contain any whitespace between words, indicating that it most likely does not follow a proper grammatical structure required for documentation text.
378
False
The documentation text within the summary tag contains incorrectly spelled words: '得到使用期限'
378
False
The documentation text within the param tag for the '<param name="wKey" />' parameter must not be empty.
378
False
The documentation text within the param tag for the '<param name="wPDate" />' parameter must not be empty.
378
False
The returns section in the documentation header must not be empty.
378
False
Statements or elements wrapped in curly brackets must be followed by a blank line.
401
False
The variable name 'wToday' begins with a prefix that looks like Hungarian notation. Remove the prefix or add it to the list of allowed prefixes.
380
False
The variable name 'wKey' begins with a prefix that looks like Hungarian notation. Remove the prefix or add it to the list of allowed prefixes.
378
False
The variable name 'wPDate' begins with a prefix that looks like Hungarian notation. Remove the prefix or add it to the list of allowed prefixes.
378
False
The comment must start with a single space. To ignore this error when commenting out a line of code, begin the comment with '////' rather than '//'.
398
14868
14879
398
21
398
32
False
The method must have a documentation header.
405
False
Statements or elements wrapped in curly brackets must be followed by a blank line.
449
False
Variable names and private field names must start with a lower-case letter: _Seed.
407
False
Field names must not start with an underscore.
407
False
All private methods must be placed after all public methods.
467
False
The method must have a documentation header.
453
False
The documentation text within the summary tag does not contain any whitespace between words, indicating that it most likely does not follow a proper grammatical structure required for documentation text.
467
False
The documentation text within the summary tag contains incorrectly spelled words: '产生注册码'
467
False
The documentation header must contain param tags matching the element's parameter list.
467
False
The documentation text within the param tag does not contain any whitespace between words, indicating that it most likely does not follow a proper grammatical structure required for documentation text.
467
False
The documentation text within the param tag contains incorrectly spelled words: '使用限限'
467
False
The documentation text within the param tag contains incorrectly spelled words: '机器码'
467
False
The returns section in the documentation header must not be empty.
467
False
Statements or elements wrapped in curly brackets must be followed by a blank line.
481
False
Statements or elements wrapped in curly brackets must be followed by a blank line.
487
False
Statements or elements wrapped in curly brackets must be followed by a blank line.
494
False
Statements or elements wrapped in curly brackets must be followed by a blank line.
500
False
Statements or elements wrapped in curly brackets must be followed by a blank line.
506
False
Statements or elements wrapped in curly brackets must be followed by a blank line.
513
False
Variable names and private field names must start with a lower-case letter: ProID.
469
False
Variable names and private field names must start with a lower-case letter: Ver.
470
False
Variable names and private field names must start with a lower-case letter: ProductKey.
472
False
The variable name 'iLen' begins with a prefix that looks like Hungarian notation. Remove the prefix or add it to the list of allowed prefixes.
475
False
The variable name 'wToDay' begins with a prefix that looks like Hungarian notation. Remove the prefix or add it to the list of allowed prefixes.
488
False
Variable names and private field names must start with a lower-case letter: Days.
467
False
Variable names and private field names must start with a lower-case letter: MacKey.
467
False
Variable names and private field names must start with a lower-case letter: MaxUsers.
467
False
Use string.Empty rather than "".
471
False
Invalid spacing around the comma.
470
17124
17124
470
50
470
50
False
The comment must start with a single space. To ignore this error when commenting out a line of code, begin the comment with '////' rather than '//'.
471
17183
17189
471
54
471
60
False
The comment must start with a single space. To ignore this error when commenting out a line of code, begin the comment with '////' rather than '//'.
475
17397
17401
475
43
475
47
False
The documentation header must not contain blank lines. Use the 'para' tag to insert line breaks within documentation text.
519
False
The summary section in the documentation header must not be empty.
521
False
An opening curly bracket must not be followed by a blank line.
522
False
The documentation text within the summary tag contains incorrectly spelled words: '文件路径'
527
False
The property's documentation summary text must begin with: Gets
527
False
property names begin with an upper-case letter: tXMLPath.
527
False
All properties must be placed after all constructors.
527
False
The documentation header must not contain blank lines. Use the 'para' tag to insert line breaks within documentation text.
536
False
The summary section in the documentation header must not be empty.
538
False
The documentation text within the constructor's summary tag must begin with the text: Initializes a new instance of the <see cref="ManagerLicenseInfo" /> class.
538
False
The call to Init must begin with the 'this.', 'base.', 'object.' or 'ManagerLicenseInfo.' or 'XmlDocument.' prefix to indicate the intended method call.
540
19449
19452
540
13
540
16
False
The method must have a documentation header.
543
False
Statements or elements wrapped in curly brackets must be followed by a blank line.
562
False
Variable names and private field names must start with a lower-case letter: FileNameAll.
543
False
All private methods must be placed after all public methods.
572
False
All private methods must be placed after all public methods.
583
False
All private methods must be placed after all public methods.
662
False
The comment must start with a single space. To ignore this error when commenting out a line of code, begin the comment with '////' rather than '//'.
547
19617
19630
547
17
547
30
False
The documentation text within the summary tag does not contain any whitespace between words, indicating that it most likely does not follow a proper grammatical structure required for documentation text.
572
False
The documentation text within the summary tag contains incorrectly spelled words: '写入'
572
False
The param tags in the documentation header must match the element's parameter list.
572
False
The documentation text within the param tag for the '<param name="wLicenseInfo" />' parameter must not be empty.
572
False
The documentation text within the param tag for the '<param name="ProID" />' parameter must not be empty.
572
False
The documentation text within the param tag for the '<param name="wMacID" />' parameter must not be empty.
572
False
The variable name 'wLicenseInfo' begins with a prefix that looks like Hungarian notation. Remove the prefix or add it to the list of allowed prefixes.
572
False
The variable name 'wMacID' begins with a prefix that looks like Hungarian notation. Remove the prefix or add it to the list of allowed prefixes.
572
False
The variable name 'wCustomerName' begins with a prefix that looks like Hungarian notation. Remove the prefix or add it to the list of allowed prefixes.
572
False
The call to WriteMacID must begin with the 'this.', 'base.', 'object.' or 'ManagerLicenseInfo.' or 'XmlDocument.' prefix to indicate the intended method call.
574
20796
20805
574
13
574
22
False
The call to WriteLicense must begin with the 'this.', 'base.', 'object.' or 'ManagerLicenseInfo.' or 'XmlDocument.' prefix to indicate the intended method call.
575
20829
20840
575
13
575
24
False
The call to tXMLPath must begin with the 'this.', 'base.', 'object.' or 'ManagerLicenseInfo.' or 'XmlDocument.' prefix to indicate the intended method call.
576
20895
20902
576
23
576
30
False
The documentation header must not contain blank lines. Use the 'para' tag to insert line breaks within documentation text.
580
False
The summary section in the documentation header must not be empty.
583
False
The returns section in the documentation header must not be empty.
583
False
Statements or elements wrapped in curly brackets must be followed by a blank line.
598
False
Statements or elements wrapped in curly brackets must be followed by a blank line.
603
False
The variable name 'mSub' begins with a prefix that looks like Hungarian notation. Remove the prefix or add it to the list of allowed prefixes.
599
False
Use string.Empty rather than "".
594
False
The method must have a documentation header.
607
False
The variable name 'wMacID' begins with a prefix that looks like Hungarian notation. Remove the prefix or add it to the list of allowed prefixes.
607
False
Variable names and private field names must start with a lower-case letter: Root.
612
False
The call to FindNode must begin with the 'this.', 'base.', 'object.' or 'ManagerLicenseInfo.' or 'XmlDocument.' prefix to indicate the intended method call.
612
22217
22224
612
32
612
39
False
The method must have a documentation header.
621
False
Statements or elements wrapped in curly brackets must be followed by a blank line.
630
False
Variable names and private field names must start with a lower-case letter: ProID.
623
False
The variable name 'wLicenseInfo' begins with a prefix that looks like Hungarian notation. Remove the prefix or add it to the list of allowed prefixes.
621
False
The variable name 'wCustomerName' begins with a prefix that looks like Hungarian notation. Remove the prefix or add it to the list of allowed prefixes.
621
False
Variable names and private field names must start with a lower-case letter: Root.
628
False
Variable names and private field names must start with a lower-case letter: Root.
634
False
The call to FindNode must begin with the 'this.', 'base.', 'object.' or 'ManagerLicenseInfo.' or 'XmlDocument.' prefix to indicate the intended method call.
628
22713
22720
628
32
628
39
False
The call to FindNode must begin with the 'this.', 'base.', 'object.' or 'ManagerLicenseInfo.' or 'XmlDocument.' prefix to indicate the intended method call.
634
22988
22995
634
32
634
39
False
Use string.Empty rather than "".
629
False
The documentation text within the summary tag does not contain any whitespace between words, indicating that it most likely does not follow a proper grammatical structure required for documentation text.
662
False
The documentation text within the summary tag contains incorrectly spelled words: '得到机器码'
662
False
The returns section in the documentation header must not be empty.
662
False
Use string.Empty rather than "".
667
False
The method must have a documentation header.
675
False
Variable names and private field names must start with a lower-case letter: ParaNode.
675
False
Variable names and private field names must start with a lower-case letter: Name.
675
False
Variable names and private field names must start with a lower-case letter: Value.
675
False
The method must have a documentation header.
683
False
The documentation text within the summary tag does not contain any whitespace between words, indicating that it most likely does not follow a proper grammatical structure required for documentation text.
693
False
The documentation text within the summary tag contains incorrectly spelled words: '用于保存'
693
False
class names begin with an upper-case letter: tagLicenseString.
693
False
The property must have a documentation header.
695
False
The property must have a documentation header.
696
False
Adjacent elements must be separated by a blank line.
696
False
The class must have a documentation header.
699
False
The constructor must have a documentation header.
701
False
The property must have a documentation header.
705
False
The property must have a documentation header.
706
False
Adjacent elements must be separated by a blank line.
706
False
The property must have a documentation header.
707
False
Adjacent elements must be separated by a blank line.
707
False
Statements or elements wrapped in curly brackets must be followed by a blank line.
716
False
The body of the if statement must be wrapped in opening and closing curly brackets.
712
False
The body of the else statement must be wrapped in opening and closing curly brackets.
714
False
The call to SerialNumber must begin with the 'this.' prefix to indicate that the item is a member of the class.
711
25293
25304
711
42
711
53
False
The property must have a documentation header.
717
False
Adjacent elements must be separated by a blank line.
717
False
The documentation text within the summary tag does not contain any whitespace between words, indicating that it most likely does not follow a proper grammatical structure required for documentation text.
721
False
The documentation text within the summary tag contains incorrectly spelled words: '软件期限'
721
False
The property's documentation summary text must begin with: Gets
721
False
Adjacent elements must be separated by a blank line.
721
False
A documentation header must be preceded by a blank line or must be the first item in its scope.
718
False
Statements or elements wrapped in curly brackets must be followed by a blank line.
734
False
The call to SerialDate must begin with the 'this.' prefix to indicate that the item is a member of the class.
725
25642
25651
725
21
725
30
False
The call to LicenseDays must begin with the 'this.' prefix to indicate that the item is a member of the class.
725
25670
25680
725
49
725
59
False
The call to LicenseDays must begin with the 'this.' prefix to indicate that the item is a member of the class.
731
25826
25836
731
28
731
38
False
The property must have a documentation header.
735
False
Adjacent elements must be separated by a blank line.
735
False
The property must have a documentation header.
736
False
Adjacent elements must be separated by a blank line.
736
False
The property must have a documentation header.
737
False
Adjacent elements must be separated by a blank line.
737
False
2021/06/04 14:57:46.270
2021/06/04 14:57:46.258
2022/01/11 09:25:10.254
2021/06/04 14:57:46.270
2021/06/04 14:57:46.270
-2040176723
2021/06/04 14:57:46.270
0
2021/06/04 14:57:46.270
0
2021/06/04 14:57:46.270
0
2021/06/04 14:57:46.270
0
2021/06/04 14:57:46.270
0
2021/06/04 14:57:46.270
0
The file has no header, the header Xml is invalid, or the header is not located at the top of the file.
1
False
All using directives must be placed inside of the namespace.
1
False
All using directives must be placed inside of the namespace.
2
False
The class must have a documentation header.
6
False
The comment must start with a single space. To ignore this error when commenting out a line of code, begin the comment with '////' rather than '//'.
8
149
166
8
9
8
26
False
The field must have a documentation header.
9
False
The field must have an access modifier.
9
False
The documentation header must not contain blank lines. Use the 'para' tag to insert line breaks within documentation text.
11
False
The summary section in the documentation header must not be empty.
15
False
The documentation header must contain param tags matching the element's parameter list.
15
False
The documentation text within the param tag for the '<param name="source" />' parameter must not be empty.
15
False
The returns section in the documentation header must not be empty.
15
False
Adjacent elements must be separated by a blank line.
15
False
A documentation header must be preceded by a blank line or must be the first item in its scope.
10
False
Statements or elements wrapped in curly brackets must be followed by a blank line.
25
False
The variable name 'hStrText' begins with a prefix that looks like Hungarian notation. Remove the prefix or add it to the list of allowed prefixes.
15
False
Invalid spacing around the semicolon.
24
878
878
24
70
24
70
False
The comment must start with a single space. To ignore this error when commenting out a line of code, begin the comment with '////' rather than '//'.
24
879
916
24
71
24
108
False
2021/06/04 14:57:46.270
2021/06/04 14:57:46.258
2022/01/11 09:25:10.249
2021/06/04 14:57:46.270
2021/06/04 14:57:46.270
-2040176723
2021/06/04 14:57:46.270
0
2021/06/04 14:57:46.270
0
2021/06/04 14:57:46.270
0
2021/06/04 14:57:46.270
0
2021/06/04 14:57:46.270
0
2021/06/04 14:57:46.270
0
The file has no header, the header Xml is invalid, or the header is not located at the top of the file.
1
False
All using directives must be placed inside of the namespace.
1
False
All using directives must be placed inside of the namespace.
2
False
All using directives must be placed inside of the namespace.
3
False
All using directives must be placed inside of the namespace.
4
False
All using directives must be placed inside of the namespace.
5
False
All using directives must be placed inside of the namespace.
6
False
System using directives must be placed before all other using directives.
6
False
All using directives must be placed inside of the namespace.
7
False
All using directives must be placed inside of the namespace.
8
False
All using directives must be placed inside of the namespace.
9
False
All using directives must be placed inside of the namespace.
10
False
The class must have a documentation header.
14
False
The field must have a documentation header.
16
False
Field names must not start with an underscore.
16
False
The field must have a documentation header.
17
False
Field names must not start with an underscore.
17
False
The constructor must have a documentation header.
19
False
The call to _userService must begin with the 'this.' prefix to indicate that the item is a member of the class.
21
680
691
21
13
21
24
False
The call to _tokenManagement must begin with the 'this.' prefix to indicate that the item is a member of the class.
22
721
736
22
13
22
28
False
The method must have a documentation header.
25
False
The body of the if statement must be wrapped in opening and closing curly brackets.
29
False
All static public methods must be placed before all non-static public methods.
44
False
The call to _userService must begin with the 'this.' prefix to indicate that the item is a member of the class.
28
917
928
28
18
28
29
False
The call to _tokenManagement must begin with the 'this.' prefix to indicate that the item is a member of the class.
35
1303
1318
35
71
35
86
False
The call to _tokenManagement must begin with the 'this.' prefix to indicate that the item is a member of the class.
37
1470
1485
37
49
37
64
False
The call to _tokenManagement must begin with the 'this.' prefix to indicate that the item is a member of the class.
37
1495
1510
37
74
37
89
False
The call to _tokenManagement must begin with the 'this.' prefix to indicate that the item is a member of the class.
37
1563
1578
37
142
37
157
False
Invalid spacing around the comma.
32
1068
1068
32
42
32
42
False
Invalid spacing around the comma.
33
1132
1132
33
46
33
46
False
The spacing around the symbol '+' is invalid.
33
1152
1152
33
66
33
66
False
The spacing around the symbol '+' is invalid.
33
False
The spacing around the symbol '+' is invalid.
33
1191
1191
33
105
33
105
False
The method must have a documentation header.
44
False
Variable names and private field names must start with a lower-case letter: Token.
44
False
2021/06/04 14:57:46.270
2021/06/04 14:57:46.258
2022/01/11 09:25:10.246
2021/06/04 14:57:46.270
2021/06/04 14:57:46.270
-2040176723
2021/06/04 14:57:46.270
0
2021/06/04 14:57:46.270
0
2021/06/04 14:57:46.270
0
2021/06/04 14:57:46.270
0
2021/06/04 14:57:46.270
0
2021/06/04 14:57:46.270
0
A syntax error has been discovered in file D:\ouruan\SourceCode\OPSOFT_O3(ODK6.0)\01 Source\APP.O3\WebApi\Authentication\UserService.cs on line 84.
84
False
2021/06/04 14:57:46.270
2021/06/04 14:57:46.258
2022/01/11 09:25:10.107
2021/06/04 14:57:46.270
2021/06/04 14:57:46.270
-2040176723
2021/06/04 14:57:46.270
0
2021/06/04 14:57:46.270
0
2021/06/04 14:57:46.270
0
2021/06/04 14:57:46.270
0
2021/06/04 14:57:46.270
0
2021/06/04 14:57:46.270
0
The file has no header, the header Xml is invalid, or the header is not located at the top of the file.
1
False
All using directives must be placed inside of the namespace.
1
False
Using directives must be sorted alphabetically by the namespaces.
1
False
All using directives must be placed inside of the namespace.
2
False
Using directives must be sorted alphabetically by the namespaces.
2
False
All using directives must be placed inside of the namespace.
3
False
All using directives must be placed inside of the namespace.
4
False
All using directives must be placed inside of the namespace.
5
False
All using directives must be placed inside of the namespace.
6
False
Using directives must be sorted alphabetically by the namespaces.
6
False
All using directives must be placed inside of the namespace.
7
False
All using directives must be placed inside of the namespace.
8
False
All using directives must be placed inside of the namespace.
9
False
System using directives must be placed before all other using directives.
9
False
The class must have a documentation header.
14
False
The code must not contain multiple blank lines in a row.
23
False
The code must not contain multiple blank lines in a row.
38
False
The code must not contain multiple blank lines in a row.
53
False
The field must have a documentation header.
16
False
The constructor must have a documentation header.
17
False
Adjacent elements must be separated by a blank line.
17
False
The call to service must begin with the 'this.', 'base.', 'object.' or 'AssetInventoryController.' or 'BaseApiController<AssetInventoryController>.' prefix to indicate the intended method call.
20
812
818
20
13
20
19
False
The documentation text within the summary tag does not contain any whitespace between words, indicating that it most likely does not follow a proper grammatical structure required for documentation text.
30
False
The documentation text within the summary tag contains incorrectly spelled words: '获取盘点方案信息及暂存信息'
30
False
The param tags in the documentation header must match the element's parameter list.
30
False
The documentation text within the param tag for the '<param name="data" />' parameter must not be empty.
30
False
The returns section in the documentation header must not be empty.
30
False
Variable names and private field names must start with a lower-case letter: SData.
30
False
If the method parameters are on separate lines, the first parameter must begin on the line beneath the name of the method.
32
False
The parameter must begin on the line after the previous parameter.
35
False
The call to TryProcess must begin with the 'this.', 'base.', 'object.' or 'AssetInventoryController.' or 'BaseApiController<AssetInventoryController>.' prefix to indicate the intended method call.
32
1160
1169
32
26
32
35
False
The documentation text within the summary tag does not contain any whitespace between words, indicating that it most likely does not follow a proper grammatical structure required for documentation text.
45
False
The documentation text within the summary tag contains incorrectly spelled words: '获取资产信息'
45
False
The param tags in the documentation header must match the element's parameter list.
45
False
The documentation text within the param tag for the '<param name="data" />' parameter must not be empty.
45
False
The returns section in the documentation header must not be empty.
45
False
Variable names and private field names must start with a lower-case letter: SData.
45
False
If the method parameters are on separate lines, the first parameter must begin on the line beneath the name of the method.
47
False
The parameter must begin on the line after the previous parameter.
50
False
The call to TryProcess must begin with the 'this.', 'base.', 'object.' or 'AssetInventoryController.' or 'BaseApiController<AssetInventoryController>.' prefix to indicate the intended method call.
47
1586
1595
47
26
47
35
False
The documentation text within the summary tag does not contain any whitespace between words, indicating that it most likely does not follow a proper grammatical structure required for documentation text.
60
False
The documentation text within the summary tag contains incorrectly spelled words: '资产盘点暂存'
60
False
The param tags in the documentation header must match the element's parameter list.
60
False
The documentation text within the param tag for the '<param name="data" />' parameter must not be empty.
60
False
The returns section in the documentation header must not be empty.
60
False
Variable names and private field names must start with a lower-case letter: SData.
60
False
If the method parameters are on separate lines, the first parameter must begin on the line beneath the name of the method.
62
False
The parameter must begin on the line after the previous parameter.
65
False
The call to TryProcess must begin with the 'this.', 'base.', 'object.' or 'AssetInventoryController.' or 'BaseApiController<AssetInventoryController>.' prefix to indicate the intended method call.
62
2014
2023
62
26
62
35
False
2021/06/04 14:57:46.270
2021/06/04 14:57:46.258
2022/01/11 09:25:10.091
2021/06/04 14:57:46.270
2021/06/04 14:57:46.270
-2040176723
2021/06/04 14:57:46.270
0
2021/06/04 14:57:46.270
0
2021/06/04 14:57:46.270
0
2021/06/04 14:57:46.270
0
2021/06/04 14:57:46.270
0
2021/06/04 14:57:46.270
0
The file has no header, the header Xml is invalid, or the header is not located at the top of the file.
1
False
The code must not contain multiple blank lines in a row.
10
False
All using directives must be placed inside of the namespace.
1
False
All using directives must be placed inside of the namespace.
2
False
All using directives must be placed inside of the namespace.
3
False
All using directives must be placed inside of the namespace.
4
False
All using directives must be placed inside of the namespace.
5
False
All using directives must be placed inside of the namespace.
6
False
All using directives must be placed inside of the namespace.
7
False
System using directives must be placed before all other using directives.
7
False
All using directives must be placed inside of the namespace.
8
False
The class must have a documentation header.
14
False
The field must have a documentation header.
16
False
Field names must not start with an underscore.
16
False
The constructor must have a documentation header.
17
False
Adjacent elements must be separated by a blank line.
17
False
Statements or elements wrapped in curly brackets must be followed by a blank line.
21
False
Variable names and private field names must start with a lower-case letter: Service.
17
False
The call to _service must begin with the 'this.', 'base.', 'object.' or 'AssetinventoryController.' or 'BaseApiController<AssetinventoryController>.' prefix to indicate the intended method call.
20
780
787
20
13
20
20
False
The method must have a documentation header.
23
False
An opening curly bracket must not be followed by a blank line.
24
False
If the method parameters are on separate lines, the first parameter must begin on the line beneath the name of the method.
27
False
The parameter must begin on the line after the previous parameter.
30
False
The call to TryProcess must begin with the 'this.', 'base.', 'object.' or 'AssetinventoryController.' or 'BaseApiController<AssetinventoryController>.' prefix to indicate the intended method call.
27
1066
1075
27
26
27
35
False
2021/06/04 14:57:46.270
2021/06/04 14:57:46.258
2022/01/11 09:25:10.087
2021/06/04 14:57:46.270
2021/06/04 14:57:46.270
-2040176723
2021/06/04 14:57:46.270
0
2021/06/04 14:57:46.270
0
2021/06/04 14:57:46.270
0
2021/06/04 14:57:46.270
0
2021/06/04 14:57:46.270
0
2021/06/04 14:57:46.270
0
The file has no header, the header Xml is invalid, or the header is not located at the top of the file.
1
False
All using directives must be placed inside of the namespace.
1
False
All using directives must be placed inside of the namespace.
2
False
All using directives must be placed inside of the namespace.
3
False
All using directives must be placed inside of the namespace.
4
False
All using directives must be placed inside of the namespace.
5
False
All using directives must be placed inside of the namespace.
6
False
All using directives must be placed inside of the namespace.
7
False
All using directives must be placed inside of the namespace.
8
False
All using directives must be placed inside of the namespace.
9
False
All using directives must be placed inside of the namespace.
10
False
All using directives must be placed inside of the namespace.
11
False
System using directives must be placed before all other using directives.
11
False
All using directives must be placed inside of the namespace.
12
False
All using directives must be placed inside of the namespace.
13
False
The documentation text within the summary tag does not contain any whitespace between words, indicating that it most likely does not follow a proper grammatical structure required for documentation text.
21
False
The documentation text within the summary tag contains incorrectly spelled words: '系统配置数据'
21
False
The code must not contain multiple blank lines in a row.
150
False
The field must have a documentation header.
23
False
Field names must not start with an underscore.
23
False
The constructor must have a documentation header.
24
False
Adjacent elements must be separated by a blank line.
24
False
Variable names and private field names must start with a lower-case letter: Service.
24
False
The call to _service must begin with the 'this.', 'base.', 'object.' or 'SysConfigDataController.' or 'BaseApiController<SysConfigDataController>.' prefix to indicate the intended method call.
27
1015
1022
27
13
27
20
False
The documentation text within the summary tag does not contain any whitespace between words, indicating that it most likely does not follow a proper grammatical structure required for documentation text.
36
False
The documentation text within the summary tag contains incorrectly spelled words: '获取', '版本'
36
False
The param tags in the documentation header must match the element's parameter list.
36
False
The documentation text within the param tag for the '<param name="request" />' parameter must not be empty.
36
False
The returns section in the documentation header must not be empty.
36
False
If the method parameters are on separate lines, the first parameter must begin on the line beneath the name of the method.
38
False
The parameter must begin on the line after the previous parameter.
41
False
The call to TryProcess must begin with the 'this.', 'base.', 'object.' or 'SysConfigDataController.' or 'BaseApiController<SysConfigDataController>.' prefix to indicate the intended method call.
38
1335
1344
38
26
38
35
False
The call to LoginInfo must begin with the 'this.', 'base.', 'object.' or 'SysConfigDataController.' or 'BaseApiController<SysConfigDataController>.' prefix to indicate the intended method call.
41
1458
1466
41
16
41
24
False
The documentation text within the summary tag does not contain any whitespace between words, indicating that it most likely does not follow a proper grammatical structure required for documentation text.
48
False
The documentation text within the summary tag contains incorrectly spelled words: '获取轮播图信息'
48
False
The returns section in the documentation header must not be empty.
48
False
If the method parameters are on separate lines, the first parameter must begin on the line beneath the name of the method.
50
False
The parameter must begin on the line after the previous parameter.
53
False
The call to TryProcess must begin with the 'this.', 'base.', 'object.' or 'SysConfigDataController.' or 'BaseApiController<SysConfigDataController>.' prefix to indicate the intended method call.
50
1703
1712
50
26
50
35
False
The call to LoginInfo must begin with the 'this.', 'base.', 'object.' or 'SysConfigDataController.' or 'BaseApiController<SysConfigDataController>.' prefix to indicate the intended method call.
53
1822
1830
53
16
53
24
False
The documentation text within the summary tag does not contain any whitespace between words, indicating that it most likely does not follow a proper grammatical structure required for documentation text.
62
False
The documentation text within the summary tag contains incorrectly spelled words: '获取仓库信息'
62
False
The documentation text within the param tag for the '<param name="paramaters" />' parameter must not be empty.
62
False
The returns section in the documentation header must not be empty.
62
False
If the method parameters are on separate lines, the first parameter must begin on the line beneath the name of the method.
64
False
The parameter must begin on the line after the previous parameter.
67
False
The call to TryProcess must begin with the 'this.', 'base.', 'object.' or 'SysConfigDataController.' or 'BaseApiController<SysConfigDataController>.' prefix to indicate the intended method call.
64
2167
2176
64
26
64
35
False
The documentation text within the summary tag does not contain any whitespace between words, indicating that it most likely does not follow a proper grammatical structure required for documentation text.
75
False
The documentation text within the summary tag contains incorrectly spelled words: '获取仓位信息'
75
False
The documentation text within the param tag for the '<param name="paramaters" />' parameter must not be empty.
75
False
The returns section in the documentation header must not be empty.
75
False
Adjacent elements must be separated by a blank line.
75
False
A documentation header must be preceded by a blank line or must be the first item in its scope.
69
False
If the method parameters are on separate lines, the first parameter must begin on the line beneath the name of the method.
77
False
The parameter must begin on the line after the previous parameter.
80
False
The call to TryProcess must begin with the 'this.', 'base.', 'object.' or 'SysConfigDataController.' or 'BaseApiController<SysConfigDataController>.' prefix to indicate the intended method call.
77
2640
2649
77
26
77
35
False
The documentation text within the summary tag does not contain any whitespace between words, indicating that it most likely does not follow a proper grammatical structure required for documentation text.
88
False
The documentation text within the summary tag contains incorrectly spelled words: '查询个人日志信息'
88
False
The documentation header must contain param tags matching the element's parameter list.
88
False
The returns section in the documentation header must not be empty.
88
False
If the method parameters are on separate lines, the first parameter must begin on the line beneath the name of the method.
90
False
The parameter must begin on the line after the previous parameter.
93
False
The call to TryProcess must begin with the 'this.', 'base.', 'object.' or 'SysConfigDataController.' or 'BaseApiController<SysConfigDataController>.' prefix to indicate the intended method call.
90
3072
3081
90
26
90
35
False
The documentation text within the summary tag does not contain any whitespace between words, indicating that it most likely does not follow a proper grammatical structure required for documentation text.
101
False
The documentation text within the summary tag contains incorrectly spelled words: '查询个人事项'
101
False
The returns section in the documentation header must not be empty.
101
False
If the method parameters are on separate lines, the first parameter must begin on the line beneath the name of the method.
103
False
The parameter must begin on the line after the previous parameter.
106
False
The call to TryProcess must begin with the 'this.', 'base.', 'object.' or 'SysConfigDataController.' or 'BaseApiController<SysConfigDataController>.' prefix to indicate the intended method call.
103
3463
3472
103
26
103
35
False
The call to LoginInfo must begin with the 'this.', 'base.', 'object.' or 'SysConfigDataController.' or 'BaseApiController<SysConfigDataController>.' prefix to indicate the intended method call.
106
3584
3592
106
16
106
24
False
The documentation text within the summary tag does not contain any whitespace between words, indicating that it most likely does not follow a proper grammatical structure required for documentation text.
114
False
The documentation text within the summary tag contains incorrectly spelled words: '查询个人事项返回'
114
False
The documentation header must contain param tags matching the element's parameter list.
114
False
The returns section in the documentation header must not be empty.
114
False
If the method parameters are on separate lines, the first parameter must begin on the line beneath the name of the method.
116
False
The parameter must begin on the line after the previous parameter.
119
False
The call to TryProcess must begin with the 'this.', 'base.', 'object.' or 'SysConfigDataController.' or 'BaseApiController<SysConfigDataController>.' prefix to indicate the intended method call.
116
3877
3886
116
26
116
35
False
The documentation text within the summary tag does not contain any whitespace between words, indicating that it most likely does not follow a proper grammatical structure required for documentation text.
128
False
The documentation text within the summary tag contains incorrectly spelled words: '获取系统使用的基本信息'
128
False
The documentation text within the param tag for the '<param name="paramaters" />' parameter must not be empty.
128
False
The returns section in the documentation header must not be empty.
128
False
If the method parameters are on separate lines, the first parameter must begin on the line beneath the name of the method.
130
False
The parameter must begin on the line after the previous parameter.
133
False
The call to TryProcess must begin with the 'this.', 'base.', 'object.' or 'SysConfigDataController.' or 'BaseApiController<SysConfigDataController>.' prefix to indicate the intended method call.
130
4349
4358
130
26
130
35
False
The documentation text within the summary tag does not contain any whitespace between words, indicating that it most likely does not follow a proper grammatical structure required for documentation text.
142
False
The documentation text within the summary tag contains incorrectly spelled words: '获取用户信息'
142
False
The param tags in the documentation header must match the element's parameter list.
142
False
The documentation text within the param tag for the '<param name="paramaters" />' parameter must not be empty.
142
False
The returns section in the documentation header must not be empty.
142
False
If the method parameters are on separate lines, the first parameter must begin on the line beneath the name of the method.
144
False
The parameter must begin on the line after the previous parameter.
147
False
The call to TryProcess must begin with the 'this.', 'base.', 'object.' or 'SysConfigDataController.' or 'BaseApiController<SysConfigDataController>.' prefix to indicate the intended method call.
144
4787
4796
144
26
144
35
False
The documentation text within the summary tag does not contain any whitespace between words, indicating that it most likely does not follow a proper grammatical structure required for documentation text.
157
False
The documentation text within the summary tag contains incorrectly spelled words: '上传图片'
157
False
The documentation text within the param tag for the '<param name="file" />' parameter must not be empty.
157
False
The returns section in the documentation header must not be empty.
157
False
If the method parameters are on separate lines, the first parameter must begin on the line beneath the name of the method.
159
False
The parameter must begin on the line after the previous parameter.
162
False
The call to TryProcess must begin with the 'this.', 'base.', 'object.' or 'SysConfigDataController.' or 'BaseApiController<SysConfigDataController>.' prefix to indicate the intended method call.
159
5205
5214
159
30
159
39
False
The documentation text within the summary tag does not contain any whitespace between words, indicating that it most likely does not follow a proper grammatical structure required for documentation text.
171
False
The documentation text within the summary tag contains incorrectly spelled words: '获取系统打印参数'
171
False
The documentation text within the param tag for the '<param name="SData" />' parameter must not be empty.
171
False
The returns section in the documentation header must not be empty.
171
False
Variable names and private field names must start with a lower-case letter: SData.
171
False
If the method parameters are on separate lines, the first parameter must begin on the line beneath the name of the method.
173
False
The parameter must begin on the line after the previous parameter.
176
False
The call to TryProcess must begin with the 'this.', 'base.', 'object.' or 'SysConfigDataController.' or 'BaseApiController<SysConfigDataController>.' prefix to indicate the intended method call.
173
5632
5641
173
26
173
35
False
The documentation text within the summary tag does not contain any whitespace between words, indicating that it most likely does not follow a proper grammatical structure required for documentation text.
184
False
The documentation text within the summary tag contains incorrectly spelled words: '获取全部蓝牙打印机设置'
184
False
The documentation header must contain param tags matching the element's parameter list.
184
False
The returns section in the documentation header must not be empty.
184
False
Variable names and private field names must start with a lower-case letter: SData.
184
False
If the method parameters are on separate lines, the first parameter must begin on the line beneath the name of the method.
186
False
The parameter must begin on the line after the previous parameter.
189
False
The call to TryProcess must begin with the 'this.', 'base.', 'object.' or 'SysConfigDataController.' or 'BaseApiController<SysConfigDataController>.' prefix to indicate the intended method call.
186
6022
6031
186
26
186
35
False
The call to LoginInfo must begin with the 'this.', 'base.', 'object.' or 'SysConfigDataController.' or 'BaseApiController<SysConfigDataController>.' prefix to indicate the intended method call.
189
6144
6152
189
16
189
24
False
2021/06/04 14:57:46.270
2021/06/04 14:57:46.258
2022/01/11 09:25:10.089
2021/06/04 14:57:46.270
2021/06/04 14:57:46.270
-2040176723
2021/06/04 14:57:46.270
0
2021/06/04 14:57:46.270
0
2021/06/04 14:57:46.270
0
2021/06/04 14:57:46.270
0
2021/06/04 14:57:46.270
0
2021/06/04 14:57:46.270
0
The file has no header, the header Xml is invalid, or the header is not located at the top of the file.
1
False
The code must not contain blank lines at the start of the file.
1
False
All using directives must be placed inside of the namespace.
2
False
All using directives must be placed inside of the namespace.
3
False
All using directives must be placed inside of the namespace.
4
False
All using directives must be placed inside of the namespace.
5
False
All using directives must be placed inside of the namespace.
6
False
All using directives must be placed inside of the namespace.
7
False
All using directives must be placed inside of the namespace.
8
False
System using directives must be placed before all other using directives.
8
False
All using directives must be placed inside of the namespace.
9
False
The class must have a documentation header.
14
False
The code must not contain multiple blank lines in a row.
39
False
The code must not contain multiple blank lines in a row.
98
False
The code must not contain multiple blank lines in a row.
99
False
The field must have a documentation header.
16
False
Field names must not start with an underscore.
16
False
The constructor must have a documentation header.
17
False
Adjacent elements must be separated by a blank line.
17
False
Variable names and private field names must start with a lower-case letter: Service.
17
False
The call to _service must begin with the 'this.', 'base.', 'object.' or 'SysMessageController.' or 'BaseApiController<SysMessageController>.' prefix to indicate the intended method call.
20
756
763
20
13
20
20
False
The documentation text within the summary tag does not contain any whitespace between words, indicating that it most likely does not follow a proper grammatical structure required for documentation text.
30
False
The documentation text within the summary tag contains incorrectly spelled words: '获取所有消息'
30
False
The documentation text within the param tag for the '<param name="pageNum" />' parameter must not be empty.
30
False
The documentation text within the param tag for the '<param name="pageCount" />' parameter must not be empty.
30
False
The returns section in the documentation header must not be empty.
30
False
If the method parameters are on separate lines, the first parameter must begin on the line beneath the name of the method.
33
False
The parameter must begin on the line after the previous parameter.
36
False
The call to TryProcess must begin with the 'this.', 'base.', 'object.' or 'SysMessageController.' or 'BaseApiController<SysMessageController>.' prefix to indicate the intended method call.
33
1215
1224
33
26
33
35
False
The spacing around the symbol '=' is invalid.
32
1153
1153
32
37
32
37
False
The documentation header is composed of invalid Xml: 第 1 行,位置 2 上的开始标记“root”与结束标记“summary”不匹配。 第 2 行,位置 3。
45
False
A documentation header line must not be followed by a blank line.
40
False
If the method parameters are on separate lines, the first parameter must begin on the line beneath the name of the method.
47
False
The parameter must begin on the line after the previous parameter.
50
False
The call to TryProcess must begin with the 'this.', 'base.', 'object.' or 'SysMessageController.' or 'BaseApiController<SysMessageController>.' prefix to indicate the intended method call.
47
1619
1628
47
26
47
35
False
The call to LoginInfo must begin with the 'this.', 'base.', 'object.' or 'SysMessageController.' or 'BaseApiController<SysMessageController>.' prefix to indicate the intended method call.
50
1747
1755
50
16
50
24
False
The documentation text within the summary tag does not contain any whitespace between words, indicating that it most likely does not follow a proper grammatical structure required for documentation text.
59
False
The documentation text within the summary tag contains incorrectly spelled words: '已读消息返回'
59
False
The documentation text within the param tag for the '<param name="pageNum" />' parameter must not be empty.
59
False
The documentation text within the param tag for the '<param name="pageCount" />' parameter must not be empty.
59
False
The returns section in the documentation header must not be empty.
59
False
If the method parameters are on separate lines, the first parameter must begin on the line beneath the name of the method.
62
False
The parameter must begin on the line after the previous parameter.
65
False
The call to TryProcess must begin with the 'this.', 'base.', 'object.' or 'SysMessageController.' or 'BaseApiController<SysMessageController>.' prefix to indicate the intended method call.
62
2184
2193
62
26
62
35
False
The documentation text within the summary tag does not contain any whitespace between words, indicating that it most likely does not follow a proper grammatical structure required for documentation text.
73
False
The documentation text within the summary tag contains incorrectly spelled words: '消息标记为已读'
73
False
The documentation text within the param tag does not contain any whitespace between words, indicating that it most likely does not follow a proper grammatical structure required for documentation text.
73
False
The documentation text within the param tag contains incorrectly spelled words: '前端穿内码字段'
73
False
The returns section in the documentation header must not be empty.
73
False
The variable name 'fInterid' begins with a prefix that looks like Hungarian notation. Remove the prefix or add it to the list of allowed prefixes.
73
False
If the method parameters are on separate lines, the first parameter must begin on the line beneath the name of the method.
76
False
The parameter must begin on the line after the previous parameter.
79
False
The call to TryProcess must begin with the 'this.', 'base.', 'object.' or 'SysMessageController.' or 'BaseApiController<SysMessageController>.' prefix to indicate the intended method call.
76
2683
2692
76
26
76
35
False
The spacing around the symbol '=' is invalid.
75
2645
2645
75
38
75
38
False
The spacing around the symbol '=' is invalid.
75
False
Invalid spacing around the closing curly bracket.
75
2654
2654
75
47
75
47
False
The documentation text within the summary tag does not contain any whitespace between words, indicating that it most likely does not follow a proper grammatical structure required for documentation text.
88
False
The documentation text within the summary tag contains incorrectly spelled words: '新闻列表显示方法'
88
False
The param tags in the documentation header must match the element's parameter list.
88
False
The documentation header must contain param tags matching the element's parameter list.
88
False
The documentation text within the param tag for the '<param name="data" />' parameter must not be empty.
88
False
The returns section in the documentation header must not be empty.
88
False
An opening curly bracket must not be followed by a blank line.
89
False
If the method parameters are on separate lines, the first parameter must begin on the line beneath the name of the method.
92
False
The parameter must begin on the line after the previous parameter.
95
False
The call to TryProcess must begin with the 'this.', 'base.', 'object.' or 'SysMessageController.' or 'BaseApiController<SysMessageController>.' prefix to indicate the intended method call.
92
3220
3229
92
26
92
35
False
The documentation text within the summary tag does not contain any whitespace between words, indicating that it most likely does not follow a proper grammatical structure required for documentation text.
106
False
The documentation text within the summary tag contains incorrectly spelled words: '获取新闻公告'
106
False
The param tags in the documentation header must match the element's parameter list.
106
False
The documentation text within the param tag for the '<param name="data" />' parameter must not be empty.
106
False
The returns section in the documentation header must not be empty.
106
False
Variable names and private field names must start with a lower-case letter: SData.
106
False
If the method parameters are on separate lines, the first parameter must begin on the line beneath the name of the method.
108
False
The parameter must begin on the line after the previous parameter.
111
False
The call to TryProcess must begin with the 'this.', 'base.', 'object.' or 'SysMessageController.' or 'BaseApiController<SysMessageController>.' prefix to indicate the intended method call.
108
3658
3667
108
26
108
35
False
2021/06/04 14:57:46.270
2021/06/04 14:57:46.258
2022/01/11 09:25:10.126
2021/06/04 14:57:46.270
2021/06/04 14:57:46.270
-2040176723
2021/06/04 14:57:46.270
0
2021/06/04 14:57:46.270
0
2021/06/04 14:57:46.270
0
2021/06/04 14:57:46.270
0
2021/06/04 14:57:46.270
0
2021/06/04 14:57:46.270
0
The file has no header, the header Xml is invalid, or the header is not located at the top of the file.
1
False
All using directives must be placed inside of the namespace.
1
False
All using directives must be placed inside of the namespace.
2
False
All using directives must be placed inside of the namespace.
3
False
All using directives must be placed inside of the namespace.
4
False
All using directives must be placed inside of the namespace.
5
False
Using directives must be sorted alphabetically by the namespaces.
5
False
All using directives must be placed inside of the namespace.
6
False
Using directives must be sorted alphabetically by the namespaces.
6
False
All using directives must be placed inside of the namespace.
7
False
Using directives must be sorted alphabetically by the namespaces.
7
False
All using directives must be placed inside of the namespace.
8
False
All using directives must be placed inside of the namespace.
9
False
All using directives must be placed inside of the namespace.
10
False
All using directives must be placed inside of the namespace.
11
False
The class must have a documentation header.
16
False
The code must not contain multiple blank lines in a row.
39
False
The code must not contain multiple blank lines in a row.
40
False
The code must not contain multiple blank lines in a row.
56
False
The code must not contain multiple blank lines in a row.
87
False
The code must not contain multiple blank lines in a row.
116
False
The code must not contain multiple blank lines in a row.
131
False
The code must not contain multiple blank lines in a row.
146
False
The code must not contain multiple blank lines in a row.
161
False
The field must have a documentation header.
18
False
The constructor must have a documentation header.
19
False
Adjacent elements must be separated by a blank line.
19
False
The call to service must begin with the 'this.', 'base.', 'object.' or 'RepairOrederController.' or 'BaseApiController<RepairOrederController>.' prefix to indicate the intended method call.
22
842
848
22
13
22
19
False
The documentation header is composed of invalid Xml: “>”是意外的标记。标记应为“=”。 第 4 行,位置 36。
30
False
Adjacent elements must be separated by a blank line.
30
False
A documentation header must be preceded by a blank line or must be the first item in its scope.
24
False
The variable name 'fName' begins with a prefix that looks like Hungarian notation. Remove the prefix or add it to the list of allowed prefixes.
30
False
If the method parameters are on separate lines, the first parameter must begin on the line beneath the name of the method.
33
False
The parameter must begin on the line after the previous parameter.
36
False
The call to TryProcess must begin with the 'this.', 'base.', 'object.' or 'RepairOrederController.' or 'BaseApiController<RepairOrederController>.' prefix to indicate the intended method call.
33
1352
1361
33
26
33
35
False
Invalid spacing around the closing parenthesis.
30
1251
1251
30
143
30
143
False
The code contains multiple spaces in a row. Only one space is needed.
32
1294
1295
32
29
32
30
False
Invalid spacing around the comma.
32
1317
1317
32
52
32
52
False
The documentation header is composed of invalid Xml: “pageSize每页显示数量”是意外的标记。标记应为“=”。 第 4 行,位置 32。
47
False
Variable names and private field names must start with a lower-case letter: PageNumber.
47
False
Variable names and private field names must start with a lower-case letter: BarNumber.
47
False
If the method parameters are on separate lines, the first parameter must begin on the line beneath the name of the method.
50
False
The parameter must begin on the line after the previous parameter.
53
False
The call to TryProcess must begin with the 'this.', 'base.', 'object.' or 'RepairOrederController.' or 'BaseApiController<RepairOrederController>.' prefix to indicate the intended method call.
50
2039
2048
50
26
50
35
False
Invalid spacing around the comma.
47
1853
1853
47
91
47
91
False
Invalid spacing around the comma.
47
1870
1870
47
108
47
108
False
Invalid spacing around the comma.
47
1899
1899
47
137
47
137
False
The documentation header is composed of invalid Xml: “basicType获取列表类型”是一个意外标记。应为空格。 第 4 行,位置 19。
63
False
If the method parameters are on separate lines, the first parameter must begin on the line beneath the name of the method.
66
False
The parameter must begin on the line after the previous parameter.
69
False
The call to TryProcess must begin with the 'this.', 'base.', 'object.' or 'RepairOrederController.' or 'BaseApiController<RepairOrederController>.' prefix to indicate the intended method call.
66
2596
2605
66
26
66
35
False
The documentation text within the summary tag does not contain any whitespace between words, indicating that it most likely does not follow a proper grammatical structure required for documentation text.
78
False
The documentation text within the summary tag contains incorrectly spelled words: '按单据表体内码获取维修', '保养工单部位信息', '维修', '保养'
78
False
The param tags in the documentation header must match the element's parameter list.
78
False
The documentation header must contain param tags matching the element's parameter list.
78
False
The documentation text within the param tag for the '<param name="data" />' parameter must not be empty.
78
False
The returns section in the documentation header must not be empty.
78
False
If the method parameters are on separate lines, the first parameter must begin on the line beneath the name of the method.
81
False
The parameter must begin on the line after the previous parameter.
84
False
The call to TryProcess must begin with the 'this.', 'base.', 'object.' or 'RepairOrederController.' or 'BaseApiController<RepairOrederController>.' prefix to indicate the intended method call.
81
3155
3164
81
26
81
35
False
The documentation text within the summary tag does not contain any whitespace between words, indicating that it most likely does not follow a proper grammatical structure required for documentation text.
94
False
The documentation text within the summary tag contains incorrectly spelled words: '修改维修', '保养工单部位信息', '完工提交'
94
False
The documentation text within the param tag for the '<param name="SData" />' parameter must not be empty.
94
False
The returns section in the documentation header must not be empty.
94
False
Variable names and private field names must start with a lower-case letter: SData.
94
False
If the method parameters are on separate lines, the first parameter must begin on the line beneath the name of the method.
96
False
The parameter must begin on the line after the previous parameter.
99
False
The call to TryProcess must begin with the 'this.', 'base.', 'object.' or 'RepairOrederController.' or 'BaseApiController<RepairOrederController>.' prefix to indicate the intended method call.
96
3631
3640
96
26
96
35
False
The documentation text within the summary tag does not contain any whitespace between words, indicating that it most likely does not follow a proper grammatical structure required for documentation text.
108
False
The documentation text within the summary tag contains incorrectly spelled words: '修改维修', '保养工单部位信息', '验收提交'
108
False
The documentation text within the param tag for the '<param name="SData" />' parameter must not be empty.
108
False
The returns section in the documentation header must not be empty.
108
False
Variable names and private field names must start with a lower-case letter: SData.
108
False
If the method parameters are on separate lines, the first parameter must begin on the line beneath the name of the method.
110
False
The parameter must begin on the line after the previous parameter.
113
False
The call to TryProcess must begin with the 'this.', 'base.', 'object.' or 'RepairOrederController.' or 'BaseApiController<RepairOrederController>.' prefix to indicate the intended method call.
110
4100
4109
110
26
110
35
False
The documentation text within the summary tag does not contain any whitespace between words, indicating that it most likely does not follow a proper grammatical structure required for documentation text.
123
False
The documentation text within the summary tag contains incorrectly spelled words: '修改维修', '保养工单信息', '验收提交'
123
False
The documentation text within the param tag for the '<param name="SData" />' parameter must not be empty.
123
False
The returns section in the documentation header must not be empty.
123
False
Variable names and private field names must start with a lower-case letter: SData.
123
False
If the method parameters are on separate lines, the first parameter must begin on the line beneath the name of the method.
125
False
The parameter must begin on the line after the previous parameter.
128
False
The call to TryProcess must begin with the 'this.', 'base.', 'object.' or 'RepairOrederController.' or 'BaseApiController<RepairOrederController>.' prefix to indicate the intended method call.
125
4573
4582
125
26
125
35
False
The documentation text within the summary tag does not contain any whitespace between words, indicating that it most likely does not follow a proper grammatical structure required for documentation text.
138
False
The documentation text within the summary tag contains incorrectly spelled words: '按单据表体内码删除工单部位信息'
138
False
The documentation text within the param tag for the '<param name="SData" />' parameter must not be empty.
138
False
The returns section in the documentation header must not be empty.
138
False
Variable names and private field names must start with a lower-case letter: SData.
138
False
If the method parameters are on separate lines, the first parameter must begin on the line beneath the name of the method.
140
False
The parameter must begin on the line after the previous parameter.
143
False
The call to TryProcess must begin with the 'this.', 'base.', 'object.' or 'RepairOrederController.' or 'BaseApiController<RepairOrederController>.' prefix to indicate the intended method call.
140
5027
5036
140
26
140
35
False
The documentation text within the summary tag does not contain any whitespace between words, indicating that it most likely does not follow a proper grammatical structure required for documentation text.
153
False
The documentation text within the summary tag contains incorrectly spelled words: '按内码删除维修', '保养工单'
153
False
The documentation text within the param tag for the '<param name="SData" />' parameter must not be empty.
153
False
The returns section in the documentation header must not be empty.
153
False
Variable names and private field names must start with a lower-case letter: SData.
153
False
If the method parameters are on separate lines, the first parameter must begin on the line beneath the name of the method.
155
False
The parameter must begin on the line after the previous parameter.
158
False
The call to TryProcess must begin with the 'this.', 'base.', 'object.' or 'RepairOrederController.' or 'BaseApiController<RepairOrederController>.' prefix to indicate the intended method call.
155
5472
5481
155
26
155
35
False
The documentation text within the summary tag does not contain any whitespace between words, indicating that it most likely does not follow a proper grammatical structure required for documentation text.
168
False
The documentation text within the summary tag contains incorrectly spelled words: '按内码删除维修', '保养工单'
168
False
The documentation text within the param tag for the '<param name="SData" />' parameter must not be empty.
168
False
The returns section in the documentation header must not be empty.
168
False
Variable names and private field names must start with a lower-case letter: SData.
168
False
If the method parameters are on separate lines, the first parameter must begin on the line beneath the name of the method.
170
False
The parameter must begin on the line after the previous parameter.
173
False
The call to TryProcess must begin with the 'this.', 'base.', 'object.' or 'RepairOrederController.' or 'BaseApiController<RepairOrederController>.' prefix to indicate the intended method call.
170
5910
5919
170
26
170
35
False
2021/06/04 14:57:46.270
2021/06/04 14:57:46.258
2022/01/11 09:25:10.124
2021/06/04 14:57:46.270
2021/06/04 14:57:46.270
-2040176723
2021/06/04 14:57:46.270
0
2021/06/04 14:57:46.270
0
2021/06/04 14:57:46.270
0
2021/06/04 14:57:46.270
0
2021/06/04 14:57:46.270
0
2021/06/04 14:57:46.270
0
The file has no header, the header Xml is invalid, or the header is not located at the top of the file.
1
False
All using directives must be placed inside of the namespace.
1
False
All using directives must be placed inside of the namespace.
2
False
All using directives must be placed inside of the namespace.
3
False
All using directives must be placed inside of the namespace.
4
False
All using directives must be placed inside of the namespace.
5
False
Using directives must be sorted alphabetically by the namespaces.
5
False
All using directives must be placed inside of the namespace.
6
False
Using directives must be sorted alphabetically by the namespaces.
6
False
All using directives must be placed inside of the namespace.
7
False
Using directives must be sorted alphabetically by the namespaces.
7
False
All using directives must be placed inside of the namespace.
8
False
All using directives must be placed inside of the namespace.
9
False
All using directives must be placed inside of the namespace.
10
False
All using directives must be placed inside of the namespace.
11
False
An opening curly bracket must not be followed by a blank line.
14
False
The documentation text within the summary tag does not contain any whitespace between words, indicating that it most likely does not follow a proper grammatical structure required for documentation text.
20
False
The documentation text within the summary tag contains incorrectly spelled words: '设备管理系统', '备件'
20
False
A documentation header must be preceded by a blank line or must be the first item in its scope.
17
False
The code must not contain multiple blank lines in a row.
29
False
The code must not contain multiple blank lines in a row.
45
False
The code must not contain multiple blank lines in a row.
60
False
The field must have a documentation header.
22
False
The constructor must have a documentation header.
23
False
Adjacent elements must be separated by a blank line.
23
False
The call to service must begin with the 'this.', 'base.', 'object.' or 'SparePartController.' or 'BaseApiController<SparePartController>.' prefix to indicate the intended method call.
26
885
891
26
13
26
19
False
The documentation text within the summary tag does not contain any whitespace between words, indicating that it most likely does not follow a proper grammatical structure required for documentation text.
36
False
The documentation text within the summary tag contains incorrectly spelled words: '获取备件列表'
36
False
The param tags in the documentation header must match the element's parameter list.
36
False
The documentation header must contain param tags matching the element's parameter list.
36
False
The documentation text within the param tag for the '<param name="data" />' parameter must not be empty.
36
False
The returns section in the documentation header must not be empty.
36
False
If the method parameters are on separate lines, the first parameter must begin on the line beneath the name of the method.
39
False
The parameter must begin on the line after the previous parameter.
42
False
The call to TryProcess must begin with the 'this.', 'base.', 'object.' or 'SparePartController.' or 'BaseApiController<SparePartController>.' prefix to indicate the intended method call.
39
1321
1330
39
26
39
35
False
Invalid spacing around the closing curly bracket.
38
1292
1292
38
63
38
63
False
The documentation text within the summary tag does not contain any whitespace between words, indicating that it most likely does not follow a proper grammatical structure required for documentation text.
52
False
The documentation text within the summary tag contains incorrectly spelled words: '备件入库提交'
52
False
The param tags in the documentation header must match the element's parameter list.
52
False
The documentation text within the param tag for the '<param name="data" />' parameter must not be empty.
52
False
The returns section in the documentation header must not be empty.
52
False
Variable names and private field names must start with a lower-case letter: SData.
52
False
If the method parameters are on separate lines, the first parameter must begin on the line beneath the name of the method.
54
False
The parameter must begin on the line after the previous parameter.
57
False
The call to TryProcess must begin with the 'this.', 'base.', 'object.' or 'SparePartController.' or 'BaseApiController<SparePartController>.' prefix to indicate the intended method call.
54
1766
1775
54
26
54
35
False
The documentation text within the summary tag does not contain any whitespace between words, indicating that it most likely does not follow a proper grammatical structure required for documentation text.
67
False
The documentation text within the summary tag contains incorrectly spelled words: '备件盘点提交'
67
False
The param tags in the documentation header must match the element's parameter list.
67
False
The documentation text within the param tag for the '<param name="data" />' parameter must not be empty.
67
False
The returns section in the documentation header must not be empty.
67
False
Variable names and private field names must start with a lower-case letter: SData.
67
False
If the method parameters are on separate lines, the first parameter must begin on the line beneath the name of the method.
69
False
The parameter must begin on the line after the previous parameter.
72
False
The call to TryProcess must begin with the 'this.', 'base.', 'object.' or 'SparePartController.' or 'BaseApiController<SparePartController>.' prefix to indicate the intended method call.
69
2210
2219
69
26
69
35
False
2021/06/04 14:57:46.270
2021/06/04 14:57:46.258
2022/01/11 09:25:10.128
2021/06/04 14:57:46.270
2021/06/04 14:57:46.270
-2040176723
2021/06/04 14:57:46.270
0
2021/06/04 14:57:46.270
0
2021/06/04 14:57:46.270
0
2021/06/04 14:57:46.270
0
2021/06/04 14:57:46.270
0
2021/06/04 14:57:46.270
0
The file has no header, the header Xml is invalid, or the header is not located at the top of the file.
1
False
The code must not contain multiple blank lines in a row.
13
False
All using directives must be placed inside of the namespace.
1
False
All using directives must be placed inside of the namespace.
2
False
All using directives must be placed inside of the namespace.
3
False
All using directives must be placed inside of the namespace.
4
False
All using directives must be placed inside of the namespace.
5
False
Using directives must be sorted alphabetically by the namespaces.
5
False
All using directives must be placed inside of the namespace.
6
False
Using directives must be sorted alphabetically by the namespaces.
6
False
All using directives must be placed inside of the namespace.
7
False
Using directives must be sorted alphabetically by the namespaces.
7
False
All using directives must be placed inside of the namespace.
8
False
All using directives must be placed inside of the namespace.
9
False
All using directives must be placed inside of the namespace.
10
False
All using directives must be placed inside of the namespace.
11
False
The class must have a documentation header.
17
False
The code must not contain multiple blank lines in a row.
41
False
The code must not contain multiple blank lines in a row.
57
False
The field must have a documentation header.
19
False
The constructor must have a documentation header.
20
False
Adjacent elements must be separated by a blank line.
20
False
The call to service must begin with the 'this.', 'base.', 'object.' or 'SpotCheckController.' or 'BaseApiController<SpotCheckController>.' prefix to indicate the intended method call.
23
830
836
23
13
23
19
False
The documentation header is composed of invalid Xml: “pageSize每页显示数量”是意外的标记。标记应为“=”。 第 4 行,位置 32。
32
False
If the method parameters are on separate lines, the first parameter must begin on the line beneath the name of the method.
35
False
The parameter must begin on the line after the previous parameter.
38
False
The call to TryProcess must begin with the 'this.', 'base.', 'object.' or 'SpotCheckController.' or 'BaseApiController<SpotCheckController>.' prefix to indicate the intended method call.
35
1380
1389
35
26
35
35
False
Invalid spacing around the comma.
32
1232
1232
32
128
32
128
False
Invalid spacing around the comma.
32
1244
1244
32
140
32
140
False
Invalid spacing around the opening curly bracket.
34
1303
1303
34
28
34
28
False
Invalid spacing around the comma.
34
1335
1335
34
60
34
60
False
Invalid spacing around the comma.
34
1340
1340
34
65
34
65
False
Invalid spacing around the closing curly bracket.
34
1351
1351
34
76
34
76
False
The documentation header is composed of invalid Xml: “>”是意外的标记。标记应为“=”。 第 4 行,位置 37。
48
False
If the method parameters are on separate lines, the first parameter must begin on the line beneath the name of the method.
51
False
The parameter must begin on the line after the previous parameter.
54
False
The call to TryProcess must begin with the 'this.', 'base.', 'object.' or 'SpotCheckController.' or 'BaseApiController<SpotCheckController>.' prefix to indicate the intended method call.
51
1886
1895
51
26
51
35
False
Invalid spacing around the opening curly bracket.
50
1848
1848
50
28
50
28
False
Invalid spacing around the closing curly bracket.
50
1857
1857
50
37
50
37
False
The documentation header is composed of invalid Xml: “RepairNote情况简述”是意外的标记。标记应为“=”。 第 4 行,位置 43。
64
False
Variable names and private field names must start with a lower-case letter: SData.
64
False
If the method parameters are on separate lines, the first parameter must begin on the line beneath the name of the method.
66
False
The parameter must begin on the line after the previous parameter.
69
False
The call to TryProcess must begin with the 'this.', 'base.', 'object.' or 'SpotCheckController.' or 'BaseApiController<SpotCheckController>.' prefix to indicate the intended method call.
66
2405
2414
66
26
66
35
False
2021/06/04 14:57:46.270
2021/06/04 14:57:46.258
2022/01/11 09:25:10.062
2021/06/04 14:57:46.270
2021/06/04 14:57:46.270
-2040176723
2021/06/04 14:57:46.270
0
2021/06/04 14:57:46.270
0
2021/06/04 14:57:46.270
0
2021/06/04 14:57:46.270
0
2021/06/04 14:57:46.270
0
2021/06/04 14:57:46.270
0
The file has no header, the header Xml is invalid, or the header is not located at the top of the file.
1
False
All using directives must be placed inside of the namespace.
1
False
Using directives must be sorted alphabetically by the namespaces.
1
False
All using directives must be placed inside of the namespace.
2
False
Using directives must be sorted alphabetically by the namespaces.
2
False
All using directives must be placed inside of the namespace.
3
False
All using directives must be placed inside of the namespace.
4
False
All using directives must be placed inside of the namespace.
5
False
All using directives must be placed inside of the namespace.
6
False
Using directives must be sorted alphabetically by the namespaces.
6
False
All using directives must be placed inside of the namespace.
7
False
All using directives must be placed inside of the namespace.
8
False
All using directives must be placed inside of the namespace.
9
False
System using directives must be placed before all other using directives.
9
False
The class must have a documentation header.
14
False
The code must not contain multiple blank lines in a row.
23
False
The code must not contain multiple blank lines in a row.
38
False
The code must not contain multiple blank lines in a row.
53
False
The code must not contain multiple blank lines in a row.
68
False
The code must not contain multiple blank lines in a row.
83
False
The code must not contain multiple blank lines in a row.
98
False
The code must not contain multiple blank lines in a row.
99
False
The code must not contain multiple blank lines in a row.
114
False
The code must not contain multiple blank lines in a row.
129
False
The code must not contain multiple blank lines in a row.
144
False
The code must not contain multiple blank lines in a row.
145
False
The field must have a documentation header.
16
False
The constructor must have a documentation header.
17
False
Adjacent elements must be separated by a blank line.
17
False
The call to service must begin with the 'this.', 'base.', 'object.' or 'InspectionController.' or 'BaseApiController<InspectionController>.' prefix to indicate the intended method call.
20
800
806
20
13
20
19
False
The documentation text within the summary tag does not contain any whitespace between words, indicating that it most likely does not follow a proper grammatical structure required for documentation text.
30
False
The documentation text within the summary tag contains incorrectly spelled words: '工序首检列表接口', '状态查询', '已完成', '未完成'
30
False
The documentation text within the param tag for the '<param name="SData" />' parameter must not be empty.
30
False
The returns section in the documentation header must not be empty.
30
False
Variable names and private field names must start with a lower-case letter: SData.
30
False
If the method parameters are on separate lines, the first parameter must begin on the line beneath the name of the method.
32
False
The parameter must begin on the line after the previous parameter.
35
False
The call to TryProcess must begin with the 'this.', 'base.', 'object.' or 'InspectionController.' or 'BaseApiController<InspectionController>.' prefix to indicate the intended method call.
32
1157
1166
32
26
32
35
False
The documentation text within the summary tag does not contain any whitespace between words, indicating that it most likely does not follow a proper grammatical structure required for documentation text.
45
False
The documentation text within the summary tag contains incorrectly spelled words: '首检数据保存'
45
False
The documentation text within the param tag for the '<param name="SData" />' parameter must not be empty.
45
False
The returns section in the documentation header must not be empty.
45
False
Variable names and private field names must start with a lower-case letter: SData.
45
False
If the method parameters are on separate lines, the first parameter must begin on the line beneath the name of the method.
47
False
The parameter must begin on the line after the previous parameter.
50
False
The call to TryProcess must begin with the 'this.', 'base.', 'object.' or 'InspectionController.' or 'BaseApiController<InspectionController>.' prefix to indicate the intended method call.
47
1608
1617
47
26
47
35
False
The documentation text within the summary tag does not contain any whitespace between words, indicating that it most likely does not follow a proper grammatical structure required for documentation text.
60
False
The documentation text within the summary tag contains incorrectly spelled words: '工序巡检列表接口', '状态查询', '已完成', '未完成'
60
False
The documentation text within the param tag for the '<param name="SData" />' parameter must not be empty.
60
False
The returns section in the documentation header must not be empty.
60
False
Variable names and private field names must start with a lower-case letter: SData.
60
False
If the method parameters are on separate lines, the first parameter must begin on the line beneath the name of the method.
62
False
The parameter must begin on the line after the previous parameter.
65
False
The call to TryProcess must begin with the 'this.', 'base.', 'object.' or 'InspectionController.' or 'BaseApiController<InspectionController>.' prefix to indicate the intended method call.
62
2070
2079
62
26
62
35
False
The documentation text within the summary tag does not contain any whitespace between words, indicating that it most likely does not follow a proper grammatical structure required for documentation text.
75
False
The documentation text within the summary tag contains incorrectly spelled words: '巡检条码扫入验证获取数据'
75
False
The documentation text within the param tag for the '<param name="SData" />' parameter must not be empty.
75
False
The returns section in the documentation header must not be empty.
75
False
Variable names and private field names must start with a lower-case letter: SData.
75
False
If the method parameters are on separate lines, the first parameter must begin on the line beneath the name of the method.
77
False
The parameter must begin on the line after the previous parameter.
80
False
The call to TryProcess must begin with the 'this.', 'base.', 'object.' or 'InspectionController.' or 'BaseApiController<InspectionController>.' prefix to indicate the intended method call.
77
2509
2518
77
26
77
35
False
The documentation text within the summary tag does not contain any whitespace between words, indicating that it most likely does not follow a proper grammatical structure required for documentation text.
90
False
The documentation text within the summary tag contains incorrectly spelled words: '巡检数据保存'
90
False
The documentation text within the param tag for the '<param name="SData" />' parameter must not be empty.
90
False
The returns section in the documentation header must not be empty.
90
False
Variable names and private field names must start with a lower-case letter: SData.
90
False
If the method parameters are on separate lines, the first parameter must begin on the line beneath the name of the method.
92
False
The parameter must begin on the line after the previous parameter.
95
False
The call to TryProcess must begin with the 'this.', 'base.', 'object.' or 'InspectionController.' or 'BaseApiController<InspectionController>.' prefix to indicate the intended method call.
92
2961
2970
92
26
92
35
False
The documentation text within the summary tag does not contain any whitespace between words, indicating that it most likely does not follow a proper grammatical structure required for documentation text.
106
False
The documentation text within the summary tag contains incorrectly spelled words: '文档查看功能'
106
False
The documentation text within the param tag for the '<param name="SData" />' parameter must not be empty.
106
False
The returns section in the documentation header must not be empty.
106
False
Variable names and private field names must start with a lower-case letter: SData.
106
False
If the method parameters are on separate lines, the first parameter must begin on the line beneath the name of the method.
108
False
The parameter must begin on the line after the previous parameter.
111
False
The call to TryProcess must begin with the 'this.', 'base.', 'object.' or 'InspectionController.' or 'BaseApiController<InspectionController>.' prefix to indicate the intended method call.
108
3401
3410
108
26
108
35
False
The documentation text within the summary tag does not contain any whitespace between words, indicating that it most likely does not follow a proper grammatical structure required for documentation text.
121
False
The documentation text within the summary tag contains incorrectly spelled words: '下载作业文档并查看'
121
False
The documentation text within the param tag for the '<param name="SData" />' parameter must not be empty.
121
False
The returns section in the documentation header must not be empty.
121
False
Variable names and private field names must start with a lower-case letter: SData.
121
False
If the method parameters are on separate lines, the first parameter must begin on the line beneath the name of the method.
123
False
The parameter must begin on the line after the previous parameter.
126
False
The call to TryProcess must begin with the 'this.', 'base.', 'object.' or 'InspectionController.' or 'BaseApiController<InspectionController>.' prefix to indicate the intended method call.
123
3840
3849
123
26
123
35
False
The documentation text within the summary tag does not contain any whitespace between words, indicating that it most likely does not follow a proper grammatical structure required for documentation text.
136
False
The documentation text within the summary tag contains incorrectly spelled words: '安灯异常呼叫列表接口'
136
False
The documentation text within the param tag for the '<param name="SData" />' parameter must not be empty.
136
False
The returns section in the documentation header must not be empty.
136
False
Variable names and private field names must start with a lower-case letter: SData.
136
False
If the method parameters are on separate lines, the first parameter must begin on the line beneath the name of the method.
138
False
The parameter must begin on the line after the previous parameter.
141
False
The call to TryProcess must begin with the 'this.', 'base.', 'object.' or 'InspectionController.' or 'BaseApiController<InspectionController>.' prefix to indicate the intended method call.
138
4275
4284
138
26
138
35
False
The documentation text within the summary tag does not contain any whitespace between words, indicating that it most likely does not follow a proper grammatical structure required for documentation text.
152
False
The documentation text within the summary tag contains incorrectly spelled words: '安灯异常呼叫处理'
152
False
The documentation text within the param tag for the '<param name="SData" />' parameter must not be empty.
152
False
The returns section in the documentation header must not be empty.
152
False
Variable names and private field names must start with a lower-case letter: SData.
152
False
If the method parameters are on separate lines, the first parameter must begin on the line beneath the name of the method.
154
False
The parameter must begin on the line after the previous parameter.
157
False
The call to TryProcess must begin with the 'this.', 'base.', 'object.' or 'InspectionController.' or 'BaseApiController<InspectionController>.' prefix to indicate the intended method call.
154
4716
4725
154
26
154
35
False
2021/06/04 14:57:46.270
2021/06/04 14:57:46.258
2022/01/11 09:25:10.060
2021/06/04 14:57:46.270
2021/06/04 14:57:46.270
-2040176723
2021/06/04 14:57:46.270
0
2021/06/04 14:57:46.270
0
2021/06/04 14:57:46.270
0
2021/06/04 14:57:46.270
0
2021/06/04 14:57:46.270
0
2021/06/04 14:57:46.270
0
The file has no header, the header Xml is invalid, or the header is not located at the top of the file.
1
False
The documentation text within the summary tag does not contain any whitespace between words, indicating that it most likely does not follow a proper grammatical structure required for documentation text.
17
False
The documentation text within the summary tag contains incorrectly spelled words: '汇报信息查询控制层'
17
False
The field must have a documentation header.
20
False
The constructor must have a documentation header.
21
False
The documentation text within the summary tag does not contain any whitespace between words, indicating that it most likely does not follow a proper grammatical structure required for documentation text.
33
False
The documentation text within the summary tag contains incorrectly spelled words: '按工作中心代码获取资源信息'
33
False
The documentation text within the param tag for the '<param name="paramaters" />' parameter must not be empty.
33
False
The returns section in the documentation header must not be empty.
33
False
The documentation text within the summary tag does not contain any whitespace between words, indicating that it most likely does not follow a proper grammatical structure required for documentation text.
47
False
The documentation text within the summary tag contains incorrectly spelled words: '依据班组', '员工信息', '员工信息', '班组'
47
False
The documentation text within the param tag for the '<param name="paramaters" />' parameter must not be empty.
47
False
The returns section in the documentation header must not be empty.
47
False
The documentation text within the summary tag does not contain any whitespace between words, indicating that it most likely does not follow a proper grammatical structure required for documentation text.
61
False
The documentation text within the summary tag contains incorrectly spelled words: '历史汇报信息加载'
61
False
The documentation text within the param tag for the '<param name="paramaters" />' parameter must not be empty.
61
False
The returns section in the documentation header must not be empty.
61
False
The documentation text within the summary tag does not contain any whitespace between words, indicating that it most likely does not follow a proper grammatical structure required for documentation text.
75
False
The documentation text within the summary tag contains incorrectly spelled words: '单资源汇报信息加载'
75
False
The documentation text within the param tag for the '<param name="paramaters" />' parameter must not be empty.
75
False
The returns section in the documentation header must not be empty.
75
False
The documentation text within the summary tag does not contain any whitespace between words, indicating that it most likely does not follow a proper grammatical structure required for documentation text.
89
False
The documentation text within the summary tag contains incorrectly spelled words: '提交资源信息'
89
False
The documentation text within the param tag for the '<param name="paramaters" />' parameter must not be empty.
89
False
The returns section in the documentation header must not be empty.
89
False
The documentation text within the summary tag does not contain any whitespace between words, indicating that it most likely does not follow a proper grammatical structure required for documentation text.
103
False
The documentation text within the summary tag contains incorrectly spelled words: '删除资源信息'
103
False
The documentation text within the param tag for the '<param name="paramaters" />' parameter must not be empty.
103
False
The returns section in the documentation header must not be empty.
103
False
The documentation text within the summary tag does not contain any whitespace between words, indicating that it most likely does not follow a proper grammatical structure required for documentation text.
117
False
The documentation text within the summary tag contains incorrectly spelled words: '查询条码类型及信息'
117
False
The documentation text within the param tag for the '<param name="paramaters" />' parameter must not be empty.
117
False
The returns section in the documentation header must not be empty.
117
False
The documentation text within the summary tag does not contain any whitespace between words, indicating that it most likely does not follow a proper grammatical structure required for documentation text.
131
False
The documentation text within the summary tag contains incorrectly spelled words: '查询', '汇报扫描条码信息'
131
False
The documentation text within the param tag for the '<param name="paramaters" />' parameter must not be empty.
131
False
The returns section in the documentation header must not be empty.
131
False
The documentation text within the summary tag does not contain any whitespace between words, indicating that it most likely does not follow a proper grammatical structure required for documentation text.
145
False
The documentation text within the summary tag contains incorrectly spelled words: '查询周转码汇报数量'
145
False
The documentation text within the param tag for the '<param name="paramaters" />' parameter must not be empty.
145
False
The returns section in the documentation header must not be empty.
145
False
The documentation text within the summary tag does not contain any whitespace between words, indicating that it most likely does not follow a proper grammatical structure required for documentation text.
159
False
The documentation text within the summary tag contains incorrectly spelled words: '重置汇报系统参数'
159
False
The documentation text within the param tag for the '<param name="paramaters" />' parameter must not be empty.
159
False
The param tags in the documentation header must match the element's parameter list.
159
False
The returns section in the documentation header must not be empty.
159
False