-
Notifications
You must be signed in to change notification settings - Fork 457
/
MicrosoftNetCoreAnalyzersResources.zh-Hans.xlf
1707 lines (1707 loc) · 141 KB
/
MicrosoftNetCoreAnalyzersResources.zh-Hans.xlf
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
<?xml version="1.0" encoding="utf-8"?>
<xliff xmlns="urn:oasis:names:tc:xliff:document:1.2" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" version="1.2" xsi:schemaLocation="urn:oasis:names:tc:xliff:document:1.2 xliff-core-1.2-transitional.xsd">
<file datatype="xml" source-language="en" target-language="zh-Hans" original="../MicrosoftNetCoreAnalyzersResources.resx">
<body>
<trans-unit id="DoNotUseInsecureRandomness">
<source>Do not use insecure randomness</source>
<target state="new">Do not use insecure randomness</target>
<note />
</trans-unit>
<trans-unit id="DoNotUseInsecureRandomnessDescription">
<source>{0} is an insecure random number generator. Use cryptographically secure random number generators when randomness is required for security</source>
<target state="new">{0} is an insecure random number generator. Use cryptographically secure random number generators when randomness is required for security</target>
<note />
</trans-unit>
<trans-unit id="DoNotUseInsecureRandomnessMessage">
<source>Using a cryptographically weak pseudo-random number generator may allow an attacker to predict what security sensitive value will be generated. Use a cryptographically strong random number generator if an unpredictable value is required, or ensure that weak pseudo-random numbers aren't used in a security sensitive manner.</source>
<target state="new">Using a cryptographically weak pseudo-random number generator may allow an attacker to predict what security sensitive value will be generated. Use a cryptographically strong random number generator if an unpredictable value is required, or ensure that weak pseudo-random numbers aren't used in a security sensitive manner.</target>
<note />
</trans-unit>
<trans-unit id="DoNotUseUnsafeDllImportSearchPath">
<source>Do not use unsafe DllImportSearchPath value</source>
<target state="new">Do not use unsafe DllImportSearchPath value</target>
<note />
</trans-unit>
<trans-unit id="DoNotUseUnsafeDllImportSearchPathDescription">
<source>There could be a malicious DLL in the default DLL search directories. Or, depending on where your application is run from, there could be a malicious DLL in the application's directory. Use a DllImportSearchPath value that specifies an explicit search path instead. The DllImportSearchPath flags that this rule looks for can be configured in .editorconfig.</source>
<target state="new">There could be a malicious DLL in the default DLL search directories. Or, depending on where your application is run from, there could be a malicious DLL in the application's directory. Use a DllImportSearchPath value that specifies an explicit search path instead. The DllImportSearchPath flags that this rule looks for can be configured in .editorconfig.</target>
<note />
</trans-unit>
<trans-unit id="DoNotUseUnsafeDllImportSearchPathMessage">
<source>Use of unsafe DllImportSearchPath value {0}</source>
<target state="new">Use of unsafe DllImportSearchPath value {0}</target>
<note />
</trans-unit>
<trans-unit id="JsonNetInsecureSerializerMessage">
<source>When deserializing untrusted input, allowing arbitrary types to be deserialized is insecure. When using deserializing JsonSerializer, use TypeNameHandling.None, or for values other than None, restrict deserialized types with a SerializationBinder.</source>
<target state="new">When deserializing untrusted input, allowing arbitrary types to be deserialized is insecure. When using deserializing JsonSerializer, use TypeNameHandling.None, or for values other than None, restrict deserialized types with a SerializationBinder.</target>
<note />
</trans-unit>
<trans-unit id="JsonNetInsecureSerializerTitle">
<source>Do not deserialize with JsonSerializer using an insecure configuration</source>
<target state="new">Do not deserialize with JsonSerializer using an insecure configuration</target>
<note />
</trans-unit>
<trans-unit id="JsonNetMaybeInsecureSerializerMessage">
<source>When deserializing untrusted input, allowing arbitrary types to be deserialized is insecure. When using deserializing JsonSerializer, use TypeNameHandling.None, or for values other than None, restrict deserialized types with a SerializationBinder.</source>
<target state="new">When deserializing untrusted input, allowing arbitrary types to be deserialized is insecure. When using deserializing JsonSerializer, use TypeNameHandling.None, or for values other than None, restrict deserialized types with a SerializationBinder.</target>
<note />
</trans-unit>
<trans-unit id="JsonNetMaybeInsecureSerializerTitle">
<source>Ensure that JsonSerializer has a secure configuration when deserializing</source>
<target state="new">Ensure that JsonSerializer has a secure configuration when deserializing</target>
<note />
</trans-unit>
<trans-unit id="DoNotUseCountAsyncWhenAnyAsyncCanBeUsedDescription">
<source>For non-empty collections, CountAsync() and LongCountAsync() enumerate the entire sequence, while AnyAsync() stops at the first item or the first item that satisfies a condition.</source>
<target state="new">For non-empty collections, CountAsync() and LongCountAsync() enumerate the entire sequence, while AnyAsync() stops at the first item or the first item that satisfies a condition.</target>
<note />
</trans-unit>
<trans-unit id="DoNotUseCountAsyncWhenAnyAsyncCanBeUsedMessage">
<source>{0}() is used where AnyAsync() could be used instead to improve performance.</source>
<target state="new">{0}() is used where AnyAsync() could be used instead to improve performance.</target>
<note />
</trans-unit>
<trans-unit id="DoNotUseCountAsyncWhenAnyAsyncCanBeUsedTitle">
<source>Do not use CountAsync() or LongCountAsync() when AnyAsync() can be used</source>
<target state="new">Do not use CountAsync() or LongCountAsync() when AnyAsync() can be used</target>
<note />
</trans-unit>
<trans-unit id="DoNotUseCountWhenAnyCanBeUsedDescription">
<source>For non-empty collections, Count() and LongCount() enumerate the entire sequence, while Any() stops at the first item or the first item that satisfies a condition.</source>
<target state="new">For non-empty collections, Count() and LongCount() enumerate the entire sequence, while Any() stops at the first item or the first item that satisfies a condition.</target>
<note />
</trans-unit>
<trans-unit id="DoNotUseCountWhenAnyCanBeUsedMessage">
<source>{0}() is used where Any() could be used instead to improve performance.</source>
<target state="new">{0}() is used where Any() could be used instead to improve performance.</target>
<note />
</trans-unit>
<trans-unit id="DoNotUseCountWhenAnyCanBeUsedTitle">
<source>Do not use Count() or LongCount() when Any() can be used</source>
<target state="new">Do not use Count() or LongCount() when Any() can be used</target>
<note />
</trans-unit>
<trans-unit id="ReviewSQLQueriesForSecurityVulnerabilitiesDescription">
<source>SQL queries that directly use user input can be vulnerable to SQL injection attacks. Review this SQL query for potential vulnerabilities, and consider using a parameterized SQL query.</source>
<target state="translated">直接使用用户输入的 SQL 查询可能容易受到 SQL 注入攻击。查看此 SQL 查询以查找潜在漏洞,请考虑使用参数化 SQL 查询。</target>
<note />
</trans-unit>
<trans-unit id="ReviewSQLQueriesForSecurityVulnerabilitiesMessageNoNonLiterals">
<source>Review if the query string passed to '{0}' in '{1}', accepts any user input.</source>
<target state="translated">查看传递给“{1}”中的“{0}”的查询字符串是否接受任何用户输入。</target>
<note />
</trans-unit>
<trans-unit id="ReviewSQLQueriesForSecurityVulnerabilitiesTitle">
<source>Review SQL queries for security vulnerabilities</source>
<target state="translated">检查 SQL 查询是否存在安全漏洞</target>
<note />
</trans-unit>
<trans-unit id="CategoryReliability">
<source>Reliability</source>
<target state="translated">可靠性</target>
<note />
</trans-unit>
<trans-unit id="DoNotCallToImmutableCollectionOnAnImmutableCollectionValueTitle">
<source>Do not call ToImmutableCollection on an ImmutableCollection value</source>
<target state="translated">请勿对 ImmutableCollection 值调用 ToImmutableCollection</target>
<note />
</trans-unit>
<trans-unit id="DoNotCallToImmutableCollectionOnAnImmutableCollectionValueMessage">
<source>Do not call {0} on an {1} value</source>
<target state="translated">请勿对 {1} 值调用 {0}</target>
<note />
</trans-unit>
<trans-unit id="RemoveRedundantCall">
<source>Remove redundant call</source>
<target state="translated">删除冗余的调用</target>
<note />
</trans-unit>
<trans-unit id="PInvokesShouldNotBeVisibleTitle">
<source>P/Invokes should not be visible</source>
<target state="translated">P/Invokes 应该是不可见的</target>
<note />
</trans-unit>
<trans-unit id="PInvokesShouldNotBeVisibleDescription">
<source>A public or protected method in a public type has the System.Runtime.InteropServices.DllImportAttribute attribute (also implemented by the Declare keyword in Visual Basic). Such methods should not be exposed.</source>
<target state="translated">公共类型中的公共方法或受保护的方法具有 System.Runtime.InteropServices.DllImportAttribute 属性(在 Visual Basic 中也由 Declare 关键字实现)。不应公开此类方法。</target>
<note />
</trans-unit>
<trans-unit id="PInvokesShouldNotBeVisibleMessage">
<source>P/Invoke method '{0}' should not be visible</source>
<target state="translated">P/Invoke 方法“{0}”应该是不可见的</target>
<note />
</trans-unit>
<trans-unit id="PInvokeDeclarationsShouldBePortableTitle">
<source>PInvoke declarations should be portable</source>
<target state="translated">PInvoke 声明应为可移植声明</target>
<note />
</trans-unit>
<trans-unit id="PInvokeDeclarationsShouldBePortableDescription">
<source>This rule evaluates the size of each parameter and the return value of a P/Invoke, and verifies that the size of the parameter is correct when marshaled to unmanaged code on 32-bit and 64-bit operating systems.</source>
<target state="translated">此规则计算每个参数的大小和 P/Invoke 的返回值,并在封送处理为 32 位和 64 位操作系统上的非托管代码时验证参数大小是否正确。</target>
<note />
</trans-unit>
<trans-unit id="PInvokeDeclarationsShouldBePortableMessageParameter">
<source>As it is declared in your code, parameter {0} of P/Invoke {1} will be {2} bytes wide on {3} platforms. This is not correct, as the actual native declaration of this API indicates it should be {4} bytes wide on {3} platforms. Consult the MSDN Platform SDK documentation for help determining what data type should be used instead of {5}.</source>
<target state="translated">如代码中所声明的,P/Invoke {1} 的参数 {0} 在 {3} 平台上的字节宽度将为 {2}。这是不正确的,因为此 API 的实际本机声明表明该参数在 {3} 平台上的字节宽度应为 {4}。请参考 MSDN Platform SDK 文档来获取帮助,确定应使用哪种数据类型来代替 {5}。</target>
<note />
</trans-unit>
<trans-unit id="PInvokeDeclarationsShouldBePortableMessageReturn">
<source>As it is declared in your code, the return type of P/Invoke {0} will be {1} bytes wide on {2} platforms. This is not correct, as the actual native declaration of this API indicates it should be {3} bytes wide on {2} platforms. Consult the MSDN Platform SDK documentation for help determining what data type should be used instead of {4}.</source>
<target state="translated">如代码中所声明的,P/Invoke {0} 的返回类型在 {2} 平台上的字节宽度将为 {1}。这是不正确的,因为此 API 的实际本机声明表明该返回类型在 {2} 平台上的字节宽度应为 {3}。请参考 MSDN Platform SDK 文档来获取帮助,确定应使用哪种数据类型来代替 {4}。</target>
<note />
</trans-unit>
<trans-unit id="SetHttpOnlyForHttpCookie">
<source>Set HttpOnly to true for HttpCookie</source>
<target state="new">Set HttpOnly to true for HttpCookie</target>
<note />
</trans-unit>
<trans-unit id="SetHttpOnlyForHttpCookieDescription">
<source>As a defense in depth measure, ensure security sensitive HTTP cookies are marked as HttpOnly. This indicates web browsers should disallow scripts from accessing the cookies. Injected malicious scripts are a common way of stealing cookies.</source>
<target state="new">As a defense in depth measure, ensure security sensitive HTTP cookies are marked as HttpOnly. This indicates web browsers should disallow scripts from accessing the cookies. Injected malicious scripts are a common way of stealing cookies.</target>
<note />
</trans-unit>
<trans-unit id="SetHttpOnlyForHttpCookieMessage">
<source>HttpCookie.HttpOnly is set to false or not set at all when using an HttpCookie. Ensure security sensitive cookies are marked as HttpOnly to prevent malicious scripts from stealing the cookies</source>
<target state="new">HttpCookie.HttpOnly is set to false or not set at all when using an HttpCookie. Ensure security sensitive cookies are marked as HttpOnly to prevent malicious scripts from stealing the cookies</target>
<note />
</trans-unit>
<trans-unit id="SpecifyMarshalingForPInvokeStringArgumentsTitle">
<source>Specify marshaling for P/Invoke string arguments</source>
<target state="translated">指定对 P/Invoke 字符串参数进行封送处理</target>
<note />
</trans-unit>
<trans-unit id="SpecifyMarshalingForPInvokeStringArgumentsDescription">
<source>A platform invoke member allows partially trusted callers, has a string parameter, and does not explicitly marshal the string. This can cause a potential security vulnerability.</source>
<target state="translated">平台调用成员允许部分受信任的调用方,具有字符串参数,且不显式封送字符串。这可能导致潜在的安全漏洞。</target>
<note />
</trans-unit>
<trans-unit id="SpecifyMarshalingForPInvokeStringArgumentsMessageParameter">
<source>To reduce security risk, marshal parameter {0} as Unicode, by setting DllImport.CharSet to CharSet.Unicode, or by explicitly marshaling the parameter as UnmanagedType.LPWStr. If you need to marshal this string as ANSI or system-dependent, set BestFitMapping=false; for added security, also set ThrowOnUnmappableChar=true.</source>
<target state="translated">为了降低安全风险,请将参数 {0} 封送为 Unicode,方法是将 DllImport.CharSet 设置为 CharSet.Unicode 或者将该参数显式封送为 UnmanagedType.LPWStr。如果你需要将该字符串封送为 ANSI 或与系统相关的编码,请设置 BestFitMapping=false;为了提高安全性,还可以设置 ThrowOnUnmappableChar=true。</target>
<note />
</trans-unit>
<trans-unit id="SpecifyMarshalingForPInvokeStringArgumentsMessageField">
<source>To reduce security risk, marshal field {0} as Unicode, by setting StructLayout.CharSet on {1} to CharSet.Unicode, or by explicitly marshaling the field as UnmanagedType.LPWStr. If you need to marshal this string as ANSI or system-dependent, use the BestFitMapping attribute to turn best-fit mapping off, and for added security, ensure ThrowOnUnmappableChar is on.</source>
<target state="translated">为了降低安全风险,请将字段 {0} 封送为 Unicode,方法是将 {1} 上的 StructLayout.CharSet 设置为 CharSet.Unicode,或者将该字段显式封送为 UnmanagedType.LPWStr。如果需要将该字符串封送为 ANSI 或者与系统相关的编码,请使用 BestFitMapping 属性来禁用最佳匹配映射。另外,为了提高安全性,请确保启用 ThrowOnUnmappableChar。</target>
<note />
</trans-unit>
<trans-unit id="SpecifyMarshalingForPInvokeStringArgumentsMessageParameterImplicitAnsi">
<source>To reduce security risk, marshal parameter {0} as Unicode, by setting DllImport.CharSet to CharSet.Unicode, or by explicitly marshaling the parameter as UnmanagedType.LPWStr. If you need to marshal this string as ANSI or system-dependent, specify MarshalAs explicitly, and set BestFitMapping=false; for added security, also set ThrowOnUnmappableChar=true.</source>
<target state="translated">为了降低安全风险,请将参数 {0} 封送为 Unicode,方法是将 DllImport.CharSet 设置为 CharSet.Unicode 或者将该参数显式封送为 UnmanagedType.LPWStr。如果需要将该字符串封送为 ANSI 或者与系统相关的编码,请显式指定 MarshalAs,并设置 BestFitMapping=false;为了提高安全性,还应设置 ThrowOnUnmappableChar=true。</target>
<note />
</trans-unit>
<trans-unit id="SpecifyMarshalingForPInvokeStringArgumentsMessageFieldImplicitAnsi">
<source>To reduce security risk, marshal field {0} as Unicode, by setting StructLayout.CharSet on {1} to CharSet.Unicode, or by explicitly marshaling the field as UnmanagedType.LPWStr. If you need to marshal this string as ANSI or system-dependent, specify MarshalAs explicitly, use the BestFitMapping attribute to turn best-fit mapping off, and for added security, to turn ThrowOnUnmappableChar on.</source>
<target state="translated">为了降低安全风险,请将字段 {0} 封送为 Unicode,方法是将 {1} 上的 StructLayout.CharSet 设置为 CharSet.Unicode,或者将该字段显式封送为 UnmanagedType.LPWStr。如果需要将该字符串封送为 ANSI 或者与系统相关的编码,请显式指定 MarshalAs,并使用 BestFitMapping 属性来禁用最佳匹配映射;为了提高安全性,启用 ThrowOnUnmappableChar。</target>
<note />
</trans-unit>
<trans-unit id="UseDefaultDllImportSearchPathsAttribute">
<source>Use DefaultDllImportSearchPaths attribute for P/Invokes</source>
<target state="new">Use DefaultDllImportSearchPaths attribute for P/Invokes</target>
<note />
</trans-unit>
<trans-unit id="UseDefaultDllImportSearchPathsAttributeDescription">
<source>By default, P/Invokes using DllImportAttribute probe a number of directories, including the current working directory for the library to load. This can be a security issue for certain applications, leading to DLL hijacking.</source>
<target state="new">By default, P/Invokes using DllImportAttribute probe a number of directories, including the current working directory for the library to load. This can be a security issue for certain applications, leading to DLL hijacking.</target>
<note />
</trans-unit>
<trans-unit id="UseDefaultDllImportSearchPathsAttributeMessage">
<source>The method {0} didn't use DefaultDllImportSearchPaths attribute for P/Invokes.</source>
<target state="new">The method {0} didn't use DefaultDllImportSearchPaths attribute for P/Invokes.</target>
<note />
</trans-unit>
<trans-unit id="UseManagedEquivalentsOfWin32ApiTitle">
<source>Use managed equivalents of win32 api</source>
<target state="translated">使用 Win32 API 的托管等效项</target>
<note />
</trans-unit>
<trans-unit id="UseManagedEquivalentsOfWin32ApiDescription">
<source>An operating system invoke method is defined and a method that has the equivalent functionality is located in the .NET Framework class library.</source>
<target state="translated">已定义操作系统调用方法,且具有等效功能的方法位于 .NET Framework 类库中。</target>
<note />
</trans-unit>
<trans-unit id="UseManagedEquivalentsOfWin32ApiMessage">
<source>Use managed equivalents of win32 api</source>
<target state="translated">使用 Win32 API 的托管等效项</target>
<note />
</trans-unit>
<trans-unit id="AlwaysConsumeTheValueReturnedByMethodsMarkedWithPreserveSigAttributeTitle">
<source>Always consume the value returned by methods marked with PreserveSigAttribute</source>
<target state="translated">始终使用带有 PreserveSigAttribute 标记的方法返回的值</target>
<note />
</trans-unit>
<trans-unit id="AlwaysConsumeTheValueReturnedByMethodsMarkedWithPreserveSigAttributeDescription">
<source>PreserveSigAttribute indicates that a method will return an HRESULT, rather than throwing an exception. Therefore, it is important to consume the HRESULT returned by the method, so that errors can be detected. Generally, this is done by calling Marshal.ThrowExceptionForHR.</source>
<target state="translated">PreserveSigAttribute 表示方法将返回一个 HRESULT,而不是引发异常。因此,请务必使用方法返回的 HRESULT,以便可以检测到错误。通常,通过调用 Marshal.ThrowExceptionForHR 来执行此操作。</target>
<note />
</trans-unit>
<trans-unit id="AlwaysConsumeTheValueReturnedByMethodsMarkedWithPreserveSigAttributeMessage">
<source>Consume the hresult returned by method '{0}' and call Marshal.ThrowExceptionForHR.</source>
<target state="translated">使用方法“{0}”返回的 HRESULT,并调用 Marshal.ThrowExceptionForHR。</target>
<note />
</trans-unit>
<trans-unit id="MarkBooleanPInvokeArgumentsWithMarshalAsTitle">
<source>Mark boolean PInvoke arguments with MarshalAs</source>
<target state="translated">用 MarshalAs 标记布尔型 PInvoke 参数</target>
<note />
</trans-unit>
<trans-unit id="MarkBooleanPInvokeArgumentsWithMarshalAsDescription">
<source>The Boolean data type has multiple representations in unmanaged code.</source>
<target state="translated">布尔数据类型在非托管代码中有多个表示形式。</target>
<note />
</trans-unit>
<trans-unit id="MarkBooleanPInvokeArgumentsWithMarshalAsMessageDefault">
<source>Add the MarshalAsAttribute to parameter {0} of P/Invoke {1}. If the corresponding unmanaged parameter is a 4-byte Win32 'BOOL', use [MarshalAs(UnmanagedType.Bool)]. For a 1-byte C++ 'bool', use MarshalAs(UnmanagedType.U1).</source>
<target state="translated">向 P/Invoke {1} 的参数 {0} 添加 MarshalAsAttribute。如果对应的非托管参数为 4 字节的 Win32 "BOOL",则使用 [MarshalAs(UnmanagedType.Bool)]。对于 1 字节的 C++ "bool",请使用 MarshalAs(UnmanagedType.U1)。</target>
<note />
</trans-unit>
<trans-unit id="MarkBooleanPInvokeArgumentsWithMarshalAsMessageReturn">
<source>Add the MarshalAsAttribute to the return type of P/Invoke {0}. If the corresponding unmanaged return type is a 4-byte Win32 'BOOL', use MarshalAs(UnmanagedType.Bool). For a 1-byte C++ 'bool', use MarshalAs(UnmanagedType.U1).</source>
<target state="translated">向 P/Invoke {0} 的返回类型添加 MarshalAsAttribute。如果对应的非托管返回类型为 4 字节的 Win32 "BOOL",则使用 MarshalAs(UnmanagedType.Bool)。对于 1 字节的 C++ "bool",请使用 MarshalAs(UnmanagedType.U1)。</target>
<note />
</trans-unit>
<trans-unit id="MarkAssembliesWithNeutralResourcesLanguageTitle">
<source>Mark assemblies with NeutralResourcesLanguageAttribute</source>
<target state="translated">用 NeutralResourcesLanguageAttribute 标记程序集</target>
<note />
</trans-unit>
<trans-unit id="MarkAssembliesWithNeutralResourcesLanguageDescription">
<source>The NeutralResourcesLanguage attribute informs the ResourceManager of the language that was used to display the resources of a neutral culture for an assembly. This improves lookup performance for the first resource that you load and can reduce your working set.</source>
<target state="translated">NeutralResourcesLanguage 特性将通知资源管理器用于显示程序集非特定区域性的资源的语言。这样可提高所加载的第一个资源的查找性能,并可减少工作集。</target>
<note />
</trans-unit>
<trans-unit id="MarkAssembliesWithNeutralResourcesLanguageMessage">
<source>Mark assemblies with NeutralResourcesLanguageAttribute</source>
<target state="translated">用 NeutralResourcesLanguageAttribute 标记程序集</target>
<note />
</trans-unit>
<trans-unit id="AddNonSerializedAttributeCodeActionTitle">
<source>Add the 'NonSerialized' attribute to this field.</source>
<target state="translated">将 "NonSerialized" 特性添加到此字段。</target>
<note />
</trans-unit>
<trans-unit id="AddSerializableAttributeCodeActionTitle">
<source>Add Serializable attribute</source>
<target state="translated">添加 Serializable 特性</target>
<note />
</trans-unit>
<trans-unit id="DisposeObjectsBeforeLosingScopeDescription">
<source>If a disposable object is not explicitly disposed before all references to it are out of scope, the object will be disposed at some indeterminate time when the garbage collector runs the finalizer of the object. Because an exceptional event might occur that will prevent the finalizer of the object from running, the object should be explicitly disposed instead.</source>
<target state="translated">如果在对某个可释放对象的所有引用超出范围之前未显式释放该对象,则当垃圾回收器运行该对象的终结器时,会在某个不确定时间释放该对象。由于可能会发生阻止该对象的终结器运行的意外事件,因此应改为显式释放该对象。</target>
<note />
</trans-unit>
<trans-unit id="DisposeObjectsBeforeLosingScopeMayBeDisposedMessage">
<source>Use recommended dispose pattern to ensure that object created by '{0}' is disposed on all paths. If possible, wrap the creation within a 'using' statement or a 'using' declaration. Otherwise, use a try-finally pattern, with a dedicated local variable declared before the try region and an unconditional Dispose invocation on non-null value in the 'finally' region, say 'x?.Dispose()'. If the object is explicitly disposed within the try region or the dispose ownership is transfered to another object or method, assign 'null' to the local variable just after such an operation to prevent double dispose in 'finally'.</source>
<target state="translated">使用推荐的 Dispose 模式以确保“{0}”创建的对象释放于所有路径上。如果可能,将创建包装在 "using" 语句或 "using" 声明中。否则,使用 try-finally 模式,在 try 区域之前声明一个专用的本地变量,在 "finally" 区域中对非 null 值进行无条件 Dispose 调用,比如,"x?.Dispose()"。如果对象显式释放在 try 区域内或释放所有权转让给另一个对象或方法,则在这样的操作之后立即将 "null" 分配给本地变量,以防止在 "finally" 中进行双重释放。</target>
<note />
</trans-unit>
<trans-unit id="DisposeObjectsBeforeLosingScopeMayBeDisposedOnExceptionPathsMessage">
<source>Use recommended dispose pattern to ensure that object created by '{0}' is disposed on all exception paths. If possible, wrap the creation within a 'using' statement or a 'using' declaration. Otherwise, use a try-finally pattern, with a dedicated local variable declared before the try region and an unconditional Dispose invocation on non-null value in the 'finally' region, say 'x?.Dispose()'. If the object is explicitly disposed within the try region or the dispose ownership is transfered to another object or method, assign 'null' to the local variable just after such an operation to prevent double dispose in 'finally'.</source>
<target state="translated">使用推荐的 Dispose 模式以确保“{0}”创建的对象在所有异常路径上释放。如果可能,将创建包装在 "using" 语句或 "using" 声明中。否则,使用 try-finally 模式,在 try 区域之前声明一个专用的本地变量,在 "finally" 区域中对非 null 值进行无条件 Dispose 调用,比如,"x?.Dispose()"。如果对象显式释放在 try 区域内或释放所有权已转让给另一个对象或方法,则在这样的操作之后立即将 "null" 分配给本地变量,以防止在 "finally" 中进行双重释放。</target>
<note />
</trans-unit>
<trans-unit id="DisposeObjectsBeforeLosingScopeNotDisposedMessage">
<source>Call System.IDisposable.Dispose on object created by '{0}' before all references to it are out of scope.</source>
<target state="translated">在对 System.IDisposable.Dispose 的所有引用超出范围之前,在“{0}”创建的对象上对其进行调用。</target>
<note />
</trans-unit>
<trans-unit id="DisposeObjectsBeforeLosingScopeNotDisposedOnExceptionPathsMessage">
<source>Object created by '{0}' is not disposed along all exception paths. Call System.IDisposable.Dispose on the object before all references to it are out of scope.</source>
<target state="translated">“{0}”创建的对象未按所有异常路径释放。请在对 System.IDisposable.Dispose 的所有引用超出范围之前,在该对象上对其进行调用。</target>
<note />
</trans-unit>
<trans-unit id="DisposeObjectsBeforeLosingScopeTitle">
<source>Dispose objects before losing scope</source>
<target state="translated">丢失范围之前释放对象</target>
<note />
</trans-unit>
<trans-unit id="DoNotPassLiteralsAsLocalizedParametersDescription">
<source>A method passes a string literal as a parameter to a constructor or method in the .NET Framework class library and that string should be localizable. To fix a violation of this rule, replace the string literal with a string retrieved through an instance of the ResourceManager class.</source>
<target state="translated">方法将文本字符串作为参数传递到构造函数或 .NET Framework 类库中的方法,该字符串应该是可本地化字符串。若要修复此规则的违规行为,将文本字符串替换为通过 ResourceManager 类的实例检索到的字符串。</target>
<note />
</trans-unit>
<trans-unit id="DoNotPassLiteralsAsLocalizedParametersMessage">
<source>Method '{0}' passes a literal string as parameter '{1}' of a call to '{2}'. Retrieve the following string(s) from a resource table instead: "{3}".</source>
<target state="translated">方法“{0}”将文本字符串作为“{2}”的调用的参数“{1}”进行传递。改为从资源表检索以下字符串:“{3}”。</target>
<note />
</trans-unit>
<trans-unit id="DoNotPassLiteralsAsLocalizedParametersTitle">
<source>Do not pass literals as localized parameters</source>
<target state="translated">请不要将文本作为本地化参数传递</target>
<note />
</trans-unit>
<trans-unit id="ImplementISerializableCorrectlyDescription">
<source>To fix a violation of this rule, make the GetObjectData method visible and overridable, and make sure that all instance fields are included in the serialization process or explicitly marked by using the NonSerializedAttribute attribute.</source>
<target state="translated">若要修复此规则的违规行为,将 GetObjectData 方法设置为可见并可重写,并确保所有实例字段都包含在序列化进程中或使用 NonSerializedAttribute 特性显式标记所有实例字段。</target>
<note />
</trans-unit>
<trans-unit id="ImplementISerializableCorrectlyMessageDefault">
<source>Add an implementation of GetObjectData to type {0}.</source>
<target state="translated">向类型 {0} 中添加对 GetObjectData 的实现。</target>
<note />
</trans-unit>
<trans-unit id="ImplementISerializableCorrectlyMessageMakeOverridable">
<source>Make {0}.GetObjectData virtual and overridable.</source>
<target state="translated">将 {0}.GetObjectData 设置为虚拟的和可重写的。</target>
<note />
</trans-unit>
<trans-unit id="ImplementISerializableCorrectlyMessageMakeVisible">
<source>Increase the accessibility of {0}.GetObjectData so that it is visible to derived types.</source>
<target state="translated">提高 {0}.GetObjectData 的可访问性以便它对于派生类型可见。</target>
<note />
</trans-unit>
<trans-unit id="ImplementISerializableCorrectlyTitle">
<source>Implement ISerializable correctly</source>
<target state="translated">正确实现 ISerializable</target>
<note />
</trans-unit>
<trans-unit id="ImplementSerializationConstructorsCodeActionTitle">
<source>Implement Serialization constructor</source>
<target state="translated">实现序列化构造函数</target>
<note />
</trans-unit>
<trans-unit id="ImplementSerializationConstructorsDescription">
<source>To fix a violation of this rule, implement the serialization constructor. For a sealed class, make the constructor private; otherwise, make it protected.</source>
<target state="translated">若要修复此规则的违规行为,请实现序列化构造函数。对于密封类,请将构造函数设为专用;否则,使它处于受保护状态。</target>
<note />
</trans-unit>
<trans-unit id="ImplementSerializationConstructorsMessageCreateMagicConstructor">
<source>Add a constructor to {0} with the following signature: 'protected {0}(SerializationInfo info, StreamingContext context)'.</source>
<target state="translated">使用以下签名向 {0} 添加构造函数: “protected {0} (SerializationInfo info, StreamingContext context)”。</target>
<note />
</trans-unit>
<trans-unit id="ImplementSerializationConstructorsMessageMakeSealedMagicConstructorPrivate">
<source>Declare the serialization constructor of {0}, a sealed type, as private.</source>
<target state="translated">将密封类型 {0} 的序列化构造函数声明为 private。</target>
<note />
</trans-unit>
<trans-unit id="ImplementSerializationConstructorsMessageMakeUnsealedMagicConstructorFamily">
<source>Declare the serialization constructor of {0}, an unsealed type, as protected.</source>
<target state="translated">将非密封类型 {0} 的序列化构造函数声明为 protected。</target>
<note />
</trans-unit>
<trans-unit id="ImplementSerializationConstructorsTitle">
<source>Implement serialization constructors</source>
<target state="translated">实现序列化构造函数</target>
<note />
</trans-unit>
<trans-unit id="ImplementSerializationMethodsCorrectlyDescription">
<source>A method that handles a serialization event does not have the correct signature, return type, or visibility.</source>
<target state="translated">处理序列化事件的方法没有正确的签名、返回类型或可见性。</target>
<note />
</trans-unit>
<trans-unit id="ImplementSerializationMethodsCorrectlyMessageGeneric">
<source>Because {0} is marked with OnSerializing, OnSerialized, OnDeserializing, or OnDeserialized, change its signature so that it is no longer generic.</source>
<target state="translated">由于 {0} 标记有 OnSerializing、OnSerialized、OnDeserializing 或 OnDeserialized,因此请更改它的签名,使它不再是泛型的。</target>
<note />
</trans-unit>
<trans-unit id="ImplementSerializationMethodsCorrectlyMessageParameters">
<source>Because {0} is marked with OnSerializing, OnSerialized, OnDeserializing, or OnDeserialized, change its signature so that it takes a single parameter of type 'System.Runtime.Serialization.StreamingContext'.</source>
<target state="translated">由于 {0} 标记有 OnSerializing、OnSerialized、OnDeserializing 或 OnDeserialized,因此请更改它的签名,使它采用类型为“System.Runtime.Serialization.StreamingContext”的单个参数。</target>
<note />
</trans-unit>
<trans-unit id="ImplementSerializationMethodsCorrectlyMessageReturnType">
<source>Because {0} is marked with OnSerializing, OnSerialized, OnDeserializing, or OnDeserialized, change its return type from {1} to void (Sub in Visual Basic).</source>
<target state="translated">由于 {0} 标记有 OnSerializing、OnSerialized、OnDeserializing 或 OnDeserialized,因此请将它的返回类型从 {1} 改为 void (Visual Basic 中为 Sub)。</target>
<note />
</trans-unit>
<trans-unit id="ImplementSerializationMethodsCorrectlyMessageStatic">
<source>Because {0} is marked with OnSerializing, OnSerialized, OnDeserializing, or OnDeserialized, change it from static (Shared in Visual Basic) to an instance method.</source>
<target state="translated">由于 {0} 标记有 OnSerializing、OnSerialized、OnDeserializing 或 OnDeserialized,因此请将它从 static (Visual Basic 中为 Shared)改为实例方法。</target>
<note />
</trans-unit>
<trans-unit id="ImplementSerializationMethodsCorrectlyMessageVisibility">
<source>Because {0} is marked with OnSerializing, OnSerialized, OnDeserializing, or OnDeserialized, change its accessibility to private.</source>
<target state="translated">由于 {0} 标记有 OnSerializing、OnSerialized、OnDeserializing 或 OnDeserialized,因此请将它的可访问性改为 private。</target>
<note />
</trans-unit>
<trans-unit id="ImplementSerializationMethodsCorrectlyTitle">
<source>Implement serialization methods correctly</source>
<target state="translated">正确实现序列化方法</target>
<note />
</trans-unit>
<trans-unit id="MarkAllNonSerializableFieldsDescription">
<source>An instance field of a type that is not serializable is declared in a type that is serializable.</source>
<target state="translated">不可序列化类型的实例字段在可序列化类型中声明。</target>
<note />
</trans-unit>
<trans-unit id="MarkAllNonSerializableFieldsMessage">
<source>Field {0} is a member of type {1} which is serializable but is of type {2} which is not serializable</source>
<target state="translated">字段 {0} 是可序列化类型 {1} 的成员,但该字段是不可序列化的类型 {2}。</target>
<note />
</trans-unit>
<trans-unit id="MarkAllNonSerializableFieldsTitle">
<source>Mark all non-serializable fields</source>
<target state="translated">标记所有不可序列化的字段</target>
<note />
</trans-unit>
<trans-unit id="MarkISerializableTypesWithSerializableDescription">
<source>To be recognized by the common language runtime as serializable, types must be marked by using the SerializableAttribute attribute even when the type uses a custom serialization routine through implementation of the ISerializable interface.</source>
<target state="translated">要被公共语言运行时识别为可序列化,必须使用 SerializableAttribute 特性标记类型,即使类型通过 ISerializable 接口的实现使用自定义序列化例程时也不例外。</target>
<note />
</trans-unit>
<trans-unit id="MarkISerializableTypesWithSerializableMessage">
<source>Add [Serializable] to {0} as this type implements ISerializable</source>
<target state="translated">将 [Serializable] 添加到 {0},因为此类型实现 ISerializable</target>
<note />
</trans-unit>
<trans-unit id="MarkISerializableTypesWithSerializableTitle">
<source>Mark ISerializable types with serializable</source>
<target state="translated">将 ISerializable 类型标记为“可序列化”</target>
<note />
</trans-unit>
<trans-unit id="ProvideDeserializationMethodsForOptionalFieldsDescription">
<source>A type has a field that is marked by using the System.Runtime.Serialization.OptionalFieldAttribute attribute, and the type does not provide deserialization event handling methods.</source>
<target state="translated">类型具有使用 System.Runtime.Serialization.OptionalFieldAttribute 特性标记的字段,并且该类型不提供反序列化事件处理方法。</target>
<note />
</trans-unit>
<trans-unit id="ProvideDeserializationMethodsForOptionalFieldsMessageOnDeserialized">
<source>Add a 'private void OnDeserialized(StreamingContext)' method to type {0} and attribute it with the System.Runtime.Serialization.OnDeserializedAttribute.</source>
<target state="translated">向类型 {0} 中添加“private void OnDeserialized(StreamingContext)”方法并使其具有 System.Runtime.Serialization.OnDeserializedAttribute 特性。</target>
<note />
</trans-unit>
<trans-unit id="ProvideDeserializationMethodsForOptionalFieldsMessageOnDeserializing">
<source>Add a 'private void OnDeserializing(StreamingContext)' method to type {0} and attribute it with the System.Runtime.Serialization.OnDeserializingAttribute.</source>
<target state="translated">向类型 {0} 中添加“private void OnDeserializing(StreamingContext)”方法并使其具有 System.Runtime.Serialization.OnDeserializingAttribute 特性。</target>
<note />
</trans-unit>
<trans-unit id="ProvideDeserializationMethodsForOptionalFieldsTitle">
<source>Provide deserialization methods for optional fields</source>
<target state="translated">为可选字段提供反序列化方法</target>
<note />
</trans-unit>
<trans-unit id="UseIndexer">
<source>Use indexer</source>
<target state="translated">使用索引器</target>
<note />
</trans-unit>
<trans-unit id="UseOrdinalStringComparisonTitle">
<source>Use ordinal stringcomparison</source>
<target state="translated">使用按顺序的 StringComparison</target>
<note />
</trans-unit>
<trans-unit id="UseOrdinalStringComparisonDescription">
<source>A string comparison operation that is nonlinguistic does not set the StringComparison parameter to either Ordinal or OrdinalIgnoreCase. By explicitly setting the parameter to either StringComparison.Ordinal or StringComparison.OrdinalIgnoreCase, your code often gains speed, becomes more correct, and becomes more reliable.</source>
<target state="translated">非语义的字符串比较运算没有将 StringComparison 参数设置为 Ordinal 或 OrdinalIgnoreCase。通过将参数显式设置为 StringComparison.Ordinal 或 StringComparison.OrdinalIgnoreCase,通常可提高代码的速度、准确率和可靠性。</target>
<note />
</trans-unit>
<trans-unit id="UseOrdinalStringComparisonMessageStringComparison">
<source>{0} passes '{1}' as the 'StringComparison' parameter to {2}. To perform a non-linguistic comparison, specify 'StringComparison.Ordinal' or 'StringComparison.OrdinalIgnoreCase' instead.</source>
<target state="translated">{0} 将“{1}”作为 "StringComparison" 参数传递给 {2}。若要执行非语义比较,请改为指定 "StringComparison.Ordinal" 或 "StringComparison.OrdinalIgnoreCase"。</target>
<note />
</trans-unit>
<trans-unit id="UseOrdinalStringComparisonMessageStringComparer">
<source>{0} passes '{1}' as the 'StringComparer' parameter to {2}. To perform a non-linguistic comparison, specify 'StringComparer.Ordinal' or 'StringComparer.OrdinalIgnoreCase' instead.</source>
<target state="translated">{0} 将“{1}”作为 "StringComparer" 参数传递给 {2}。若要执行非语义比较,请改为指定 "StringComparer.Ordinal" 或 "StringComparer.OrdinalIgnoreCase"。</target>
<note />
</trans-unit>
<trans-unit id="DoNotUseTimersThatPreventPowerStateChangesTitle">
<source>Do not use timers that prevent power state changes</source>
<target state="translated">不要使用阻止电源状态更改的计时器</target>
<note />
</trans-unit>
<trans-unit id="DoNotUseTimersThatPreventPowerStateChangesDescription">
<source>Higher-frequency periodic activity will keep the CPU busy and interfere with power-saving idle timers that turn off the display and hard disks.</source>
<target state="translated">频率较高的定期活动会使 CPU 处于繁忙状态并且干扰具有节能功能(关闭显示器和硬盘)的空闲计时器。</target>
<note />
</trans-unit>
<trans-unit id="DoNotUseTimersThatPreventPowerStateChangesMessage">
<source>Do not use timers that prevent power state changes</source>
<target state="translated">不要使用阻止电源状态更改的计时器</target>
<note />
</trans-unit>
<trans-unit id="AvoidUnsealedAttributesTitle">
<source>Avoid unsealed attributes</source>
<target state="translated">避免使用非密封特性</target>
<note />
</trans-unit>
<trans-unit id="AvoidUnsealedAttributesDescription">
<source>The .NET Framework class library provides methods for retrieving custom attributes. By default, these methods search the attribute inheritance hierarchy. Sealing the attribute eliminates the search through the inheritance hierarchy and can improve performance.</source>
<target state="translated">.NET Framework 类库提供用于检索自定义特性的方法。默认情况下,这些方法搜索特性继承层次结构。通过密封特性,将无需搜索继承层次结构并可提高性能。</target>
<note />
</trans-unit>
<trans-unit id="AvoidUnsealedAttributesMessage">
<source>Avoid unsealed attributes</source>
<target state="translated">避免使用非密封特性</target>
<note />
</trans-unit>
<trans-unit id="TestForEmptyStringsUsingStringLengthTitle">
<source>Test for empty strings using string length</source>
<target state="translated">使用字符串长度测试是否有空字符串</target>
<note />
</trans-unit>
<trans-unit id="TestForEmptyStringsUsingStringLengthDescription">
<source>Comparing strings by using the String.Length property or the String.IsNullOrEmpty method is significantly faster than using Equals.</source>
<target state="translated">相比于使用 Equals,使用 String.Length 属性或 String.IsNullOrEmpty 方法比较字符串的速度要快得多。</target>
<note />
</trans-unit>
<trans-unit id="TestForEmptyStringsUsingStringLengthMessage">
<source>Test for empty strings using 'string.Length' property or 'string.IsNullOrEmpty' method instead of an Equality check.</source>
<target state="translated">使用 "string.Length" 属性或 "string.IsNullOrEmpty" 方法而不是 Equality 检查来测试是否有空字符串。</target>
<note />
</trans-unit>
<trans-unit id="DoNotLockOnObjectsWithWeakIdentityTitle">
<source>Do not lock on objects with weak identity</source>
<target state="translated">不要锁定具有弱标识的对象</target>
<note />
</trans-unit>
<trans-unit id="DoNotLockOnObjectsWithWeakIdentityDescription">
<source>An object is said to have a weak identity when it can be directly accessed across application domain boundaries. A thread that tries to acquire a lock on an object that has a weak identity can be blocked by a second thread in a different application domain that has a lock on the same object.</source>
<target state="translated">当可以跨应用程序域边界直接访问对象时,则认为该对象具有弱标识。如果某线程尝试获取具有弱标识的对象上的锁,则该线程可能会被其他应用程序域中持有同一对象的锁的另一线程阻止。</target>
<note />
</trans-unit>
<trans-unit id="DoNotLockOnObjectsWithWeakIdentityMessage">
<source>Do not lock on objects with weak identity</source>
<target state="translated">不要锁定具有弱标识的对象</target>
<note />
</trans-unit>
<trans-unit id="DoNotCatchCorruptedStateExceptionsInGeneralHandlersTitle">
<source>Do not catch corrupted state exceptions in general handlers.</source>
<target state="translated">不要在常规处理程序中捕获损坏状态异常。</target>
<note />
</trans-unit>
<trans-unit id="DoNotCatchCorruptedStateExceptionsInGeneralHandlersDescription">
<source>Do not author general catch handlers in code that receives corrupted state exceptions.</source>
<target state="translated">不要在接收到损坏状态异常的代码中编写常规捕获处理程序。</target>
<note />
</trans-unit>
<trans-unit id="DoNotCatchCorruptedStateExceptionsInGeneralHandlersMessage">
<source>Do not catch corrupted state exceptions in general handlers.</source>
<target state="translated">不要在常规处理程序中捕获损坏状态异常。</target>
<note />
</trans-unit>
<trans-unit id="RethrowToPreserveStackDetailsTitle">
<source>Rethrow to preserve stack details</source>
<target state="translated">再次引发以保留堆栈详细信息</target>
<note />
</trans-unit>
<trans-unit id="RethrowToPreserveStackDetailsDescription">
<source>An exception is rethrown and the exception is explicitly specified in the throw statement. If an exception is rethrown by specifying the exception in the throw statement, the list of method calls between the original method that threw the exception and the current method is lost.</source>
<target state="translated">异常被再次引发并在 throw 语句中显式指定。如果通过在 throw 语句中指定异常来重新引发异常,则引发该异常的原始方法与当前方法之间的方法调用列表将丢失。</target>
<note />
</trans-unit>
<trans-unit id="RethrowToPreserveStackDetailsMessage">
<source>Rethrow to preserve stack details</source>
<target state="translated">再次引发以保留堆栈详细信息</target>
<note />
</trans-unit>
<trans-unit id="DoNotRaiseReservedExceptionTypesTitle">
<source>Do not raise reserved exception types</source>
<target state="translated">不要引发保留的异常类型</target>
<note />
</trans-unit>
<trans-unit id="DoNotRaiseReservedExceptionTypesDescription">
<source>An exception of type that is not sufficiently specific or reserved by the runtime should never be raised by user code. This makes the original error difficult to detect and debug. If this exception instance might be thrown, use a different exception type.</source>
<target state="translated">用户代码永不会引发不够具体或运行时保留的异常类型。这样会使原来的错误难以检测和调试。如有可能引发此异常实例,请使用其他异常类型。</target>
<note />
</trans-unit>
<trans-unit id="DoNotRaiseReservedExceptionTypesMessageTooGeneric">
<source>Exception type {0} is not sufficiently specific.</source>
<target state="translated">异常类型 {0} 不够具体。</target>
<note />
</trans-unit>
<trans-unit id="DoNotRaiseReservedExceptionTypesMessageReserved">
<source>Exception type {0} is reserved by the runtime.</source>
<target state="translated">异常类型 {0} 是运行时保留的。</target>
<note />
</trans-unit>
<trans-unit id="InitializeValueTypeStaticFieldsInlineTitle">
<source>Initialize value type static fields inline</source>
<target state="translated">以内联方式初始化值类型的静态字段</target>
<note />
</trans-unit>
<trans-unit id="InitializeReferenceTypeStaticFieldsInlineTitle">
<source>Initialize reference type static fields inline</source>
<target state="translated">以内联方式初始化引用类型的静态字段</target>
<note />
</trans-unit>
<trans-unit id="InitializeValueTypeStaticFieldsInlineDescription">
<source>A value type declares an explicit static constructor. To fix a violation of this rule, initialize all static data when it is declared and remove the static constructor.</source>
<target state="translated">某值类型声明了显式静态构造函数。要修复与该规则的冲突,请在声明它时初始化所有静态数据,并删除静态构造函数。</target>
<note />
</trans-unit>
<trans-unit id="InitializeReferenceTypeStaticFieldsInlineDescription">
<source>A reference type declares an explicit static constructor. To fix a violation of this rule, initialize all static data when it is declared and remove the static constructor.</source>
<target state="translated">某引用类型声明了显式静态构造函数。要修复与该规则的冲突,请在声明它时初始化所有静态数据,并删除静态构造函数。</target>
<note />
</trans-unit>
<trans-unit id="InitializeStaticFieldsInlineMessage">
<source>Initialize all static fields in '{0}' when those fields are declared and remove the explicit static constructor</source>
<target state="translated">在声明这些字段时初始化“{0}”中的所有静态字段,并删除静态构造函数</target>
<note />
</trans-unit>
<trans-unit id="DisposableFieldsShouldBeDisposedTitle">
<source>Disposable fields should be disposed</source>
<target state="translated">应释放可释放的字段</target>
<note />
</trans-unit>
<trans-unit id="DisposableFieldsShouldBeDisposedDescription">
<source>A type that implements System.IDisposable declares fields that are of types that also implement IDisposable. The Dispose method of the field is not called by the Dispose method of the declaring type. To fix a violation of this rule, call Dispose on fields that are of types that implement IDisposable if you are responsible for allocating and releasing the unmanaged resources held by the field.</source>
<target state="translated">实现 System.IDisposable 的类型将声明一些字段,这些字段所属的类型还实现 IDisposable。字段的 Dispose 方法不由声明类型的 Dispose 方法调用。若要修复此规则的违规行为,如果你负责分配和释放该字段持有的非托管资源,请在其所属类型实现 IDisposable 的字段上调用 Dispose。</target>
<note />
</trans-unit>
<trans-unit id="DisposableFieldsShouldBeDisposedMessage">
<source>'{0}' contains field '{1}' that is of IDisposable type '{2}', but it is never disposed. Change the Dispose method on '{0}' to call Close or Dispose on this field.</source>
<target state="translated">“{0}”包含 IDisposable 类型“{2}”的字段“{1}”,但从未进行释放。请更改“{0}”上的 Dispose 方法以对此字段调用 Close 或 Dispose。</target>
<note />
</trans-unit>
<trans-unit id="DoNotCallOverridableMethodsInConstructorsTitle">
<source>Do not call overridable methods in constructors</source>
<target state="translated">不要在构造函数中调用可重写的方法</target>
<note />
</trans-unit>
<trans-unit id="DoNotCallOverridableMethodsInConstructorsDescription">
<source>When a constructor calls a virtual method, the constructor for the instance that invokes the method may not have executed.</source>
<target state="translated">构造函数调用虚方法时,可能尚未执行调用该方法的实例的构造函数。</target>
<note />
</trans-unit>
<trans-unit id="DoNotCallOverridableMethodsInConstructorsMessage">
<source>Do not call overridable methods in constructors</source>
<target state="translated">不要在构造函数中调用可重写的方法</target>
<note />
</trans-unit>
<trans-unit id="DisposeMethodsShouldCallBaseClassDisposeTitle">
<source>Dispose methods should call base class dispose</source>
<target state="translated">Dispose 方法应调用基类释放</target>
<note />
</trans-unit>
<trans-unit id="DisposeMethodsShouldCallBaseClassDisposeDescription">
<source>A type that implements System.IDisposable inherits from a type that also implements IDisposable. The Dispose method of the inheriting type does not call the Dispose method of the parent type. To fix a violation of this rule, call base.Dispose in your Dispose method.</source>
<target state="translated">实现 System.IDisposable 的类型继承自实现 IDisposable 的类型。继承类型的 Dispose 方法不调用父类型的 Dispose 方法。若要修复此规则的违规行为,请在 Dispose 方法中调用 base.Dispose。</target>
<note />
</trans-unit>
<trans-unit id="DisposeMethodsShouldCallBaseClassDisposeMessage">
<source>Ensure that method '{0}' calls '{1}' in all possible control flow paths.</source>
<target state="translated">请确保方法“{0}”在所有可能的控制流路径中都调用“{1}”。</target>
<note />
</trans-unit>
<trans-unit id="DisposableTypesShouldDeclareFinalizerTitle">
<source>Disposable types should declare finalizer</source>
<target state="translated">可释放类型应声明终结器</target>
<note />
</trans-unit>
<trans-unit id="DisposableTypesShouldDeclareFinalizerDescription">
<source>A type that implements System.IDisposable and has fields that suggest the use of unmanaged resources does not implement a finalizer, as described by Object.Finalize.</source>
<target state="translated">如果某类型实现了 System.IDisposable 且包含建议使用非托管资源的字段,则该类型不会实现 Object.Finalize 所述的终结器。</target>
<note />
</trans-unit>
<trans-unit id="DisposableTypesShouldDeclareFinalizerMessage">
<source>Disposable types should declare finalizer</source>
<target state="translated">可释放类型应声明终结器</target>
<note />
</trans-unit>
<trans-unit id="FinalizersShouldCallBaseClassFinalizerTitle">
<source>Finalizers should call base class finalizer</source>
<target state="translated">终结器应调用基类的终结器</target>
<note />
</trans-unit>
<trans-unit id="FinalizersShouldCallBaseClassFinalizerDescription">
<source>Finalization must be propagated through the inheritance hierarchy. To guarantee this, types must call their base class Finalize method in their own Finalize method.</source>
<target state="translated">终止必须通过继承层次结构传播。要确保这一点,类型必须从其自身的 Finalize 方法调用它们的基类 Finalize 方法。</target>
<note />
</trans-unit>
<trans-unit id="FinalizersShouldCallBaseClassFinalizerMessage">
<source>Finalizers should call base class finalizer</source>
<target state="translated">终结器应调用基类的终结器</target>
<note />
</trans-unit>
<trans-unit id="ProvideCorrectArgumentsToFormattingMethodsTitle">
<source>Provide correct arguments to formatting methods</source>
<target state="translated">为格式化方法提供正确的参数</target>
<note />
</trans-unit>
<trans-unit id="ProvideCorrectArgumentsToFormattingMethodsDescription">
<source>The format argument that is passed to System.String.Format does not contain a format item that corresponds to each object argument, or vice versa.</source>
<target state="translated">传递到 System.String.Format 的 format 参数不包含与各对象参数相对应的格式项,反之亦然。</target>
<note />
</trans-unit>
<trans-unit id="ProvideCorrectArgumentsToFormattingMethodsMessage">
<source>Provide correct arguments to formatting methods</source>
<target state="translated">为格式化方法提供正确的参数</target>
<note />
</trans-unit>
<trans-unit id="TestForNaNCorrectlyTitle">
<source>Test for NaN correctly</source>
<target state="translated">正确测试 NaN</target>
<note />
</trans-unit>
<trans-unit id="TestForNaNCorrectlyDescription">
<source>This expression tests a value against Single.Nan or Double.Nan. Use Single.IsNan(Single) or Double.IsNan(Double) to test the value.</source>
<target state="translated">此表达式针对 Single.Nan 或 Double.Nan 测试某个值。使用 Single.IsNan(Single) 或 Double.IsNan(Double) 来测试值。</target>
<note />
</trans-unit>
<trans-unit id="TestForNaNCorrectlyMessage">
<source>Test for NaN correctly</source>
<target state="translated">正确测试 NaN</target>
<note />
</trans-unit>
<trans-unit id="AttributeStringLiteralsShouldParseCorrectlyTitle">
<source>Attribute string literals should parse correctly</source>
<target state="translated">特性字符串文本应正确分析</target>
<note />
</trans-unit>
<trans-unit id="AttributeStringLiteralsShouldParseCorrectlyDescription">
<source>The string literal parameter of an attribute does not parse correctly for a URL, a GUID, or a version.</source>
<target state="translated">特性的字符串文本参数未正确解析 URL、GUID 或版本。</target>
<note />
</trans-unit>
<trans-unit id="AttributeStringLiteralsShouldParseCorrectlyMessageDefault">
<source>In the constructor of '{0}', change the value of argument '{1}', which is currently "{2}", to something that can be correctly parsed as '{3}'.</source>
<target state="translated">在“{0}”的构造函数中,将参数“{1}”的当前值“{2}”更改为可正确解析为“{3}”的某个值。</target>
<note />
</trans-unit>
<trans-unit id="AttributeStringLiteralsShouldParseCorrectlyMessageEmpty">
<source>In the constructor of '{0}', change the value of argument '{1}', which is currently an empty string (""), to something that can be correctly parsed as '{2}'.</source>
<target state="translated">在“{0}”的构造函数中,将参数“{1}”的值(此值当前为空字符串(""))更改为可正确解析为“{2}”的某个值。</target>
<note />
</trans-unit>
<trans-unit id="AvoidZeroLengthArrayAllocationsTitle">
<source>Avoid zero-length array allocations.</source>
<target state="translated">避免长度为零的数组分配。</target>
<note />
</trans-unit>
<trans-unit id="AvoidZeroLengthArrayAllocationsMessage">
<source>Avoid unnecessary zero-length array allocations. Use {0} instead.</source>
<target state="translated">避免不必要的长度为零的数组分配。改用 {0}。</target>
<note />
</trans-unit>
<trans-unit id="DoNotUseEnumerableMethodsOnIndexableCollectionsInsteadUseTheCollectionDirectlyTitle">
<source>Do not use Enumerable methods on indexable collections. Instead use the collection directly</source>
<target state="translated">不要在可索引的集合上使用 Enumerable 方法。而是直接使用集合</target>
<note />
</trans-unit>
<trans-unit id="DoNotUseEnumerableMethodsOnIndexableCollectionsInsteadUseTheCollectionDirectlyDescription">
<source>This collection is directly indexable. Going through LINQ here causes unnecessary allocations and CPU work.</source>
<target state="translated">该集合是可直接索引的。在此处查看 LINQ 会导致不必要的分配和 CPU 工作。</target>
<note />
</trans-unit>
<trans-unit id="DoNotUseEnumerableMethodsOnIndexableCollectionsInsteadUseTheCollectionDirectlyMessage">
<source>Do not use Enumerable methods on indexable collections. Instead use the collection directly</source>
<target state="translated">不要在可索引的集合上使用 Enumerable 方法。而是直接使用集合</target>
<note />
</trans-unit>
<trans-unit id="SpecifyCultureInfoTitle">
<source>Specify CultureInfo</source>
<target state="translated">指定 CultureInfo</target>
<note />
</trans-unit>
<trans-unit id="SpecifyCultureInfoDescription">
<source>A method or constructor calls a member that has an overload that accepts a System.Globalization.CultureInfo parameter, and the method or constructor does not call the overload that takes the CultureInfo parameter. When a CultureInfo or System.IFormatProvider object is not supplied, the default value that is supplied by the overloaded member might not have the effect that you want in all locales. If the result will be displayed to the user, specify 'CultureInfo.CurrentCulture' as the 'CultureInfo' parameter. Otherwise, if the result will be stored and accessed by software, such as when it is persisted to disk or to a database, specify 'CultureInfo.InvariantCulture'.</source>
<target state="translated">某方法或构造函数调用的成员有一个接受 System.Globalization.CultureInfo 参数的重载,但该方法或构造函数没有调用接受 CultureInfo 参数的重载。如果未提供 CultureInfo 或 System.IFormatProvider 对象,则重载成员提供的默认值可能不会在所有区域设置中产生想要的效果。如果要向用户显示结果,请指定 "CultureInfo.CurrentCulture" 作为 "CultureInfo" 参数。或者,如果软件将存储和访问此结果(例如,当将此结果保留到磁盘或数据库中时),则指定 "CultureInfo.InvariantCulture"。</target>
<note />
</trans-unit>
<trans-unit id="SpecifyCultureInfoMessage">
<source>The behavior of '{0}' could vary based on the current user's locale settings. Replace this call in '{1}' with a call to '{2}'.</source>
<target state="translated">“{0}”的行为可能因当前用户的区域设置而异。请将“{1}”中的此调用替换为对“{2}”的调用。</target>
<note />
</trans-unit>
<trans-unit id="SpecifyIFormatProviderTitle">
<source>Specify IFormatProvider</source>
<target state="translated">指定 IFormatProvider</target>
<note />
</trans-unit>
<trans-unit id="SpecifyIFormatProviderDescription">
<source>A method or constructor calls one or more members that have overloads that accept a System.IFormatProvider parameter, and the method or constructor does not call the overload that takes the IFormatProvider parameter. When a System.Globalization.CultureInfo or IFormatProvider object is not supplied, the default value that is supplied by the overloaded member might not have the effect that you want in all locales. If the result will be based on the input from/output displayed to the user, specify 'CultureInfo.CurrentCulture' as the 'IFormatProvider'. Otherwise, if the result will be stored and accessed by software, such as when it is loaded from disk/database and when it is persisted to disk/database, specify 'CultureInfo.InvariantCulture'</source>
<target state="translated">某方法或构造函数调用的一个或多个成员具有接受 System.IFormatProvider 参数的重载,但该方法或构造函数没有调用接受 IFormatProvider 参数的重载。如果未提供 System.Globalization.CultureInfo 或 System.IFormatProvider 对象,则重载成员提供的默认值可能不会在所有区域设置中产生想要的效果。如果要基于输入/输出向用户显示结果,请指定 "CultureInfo.CurrentCulture" 作为 "IFormatProvider" 参数。或者,如果软件将存储和访问此结果(例如,从磁盘/数据库加载此结果以及将它保留到磁盘/数据库中时),则指定 "CultureInfo.InvariantCulture"</target>
<note />
</trans-unit>
<trans-unit id="SpecifyIFormatProviderMessageIFormatProviderAlternateString">
<source>The behavior of '{0}' could vary based on the current user's locale settings. Replace this call in '{1}' with a call to '{2}'.</source>
<target state="translated">“{0}”的行为可能因当前用户的区域设置而异。请将“{1}”中的此调用替换为对“{2}”的调用。</target>
<note />
</trans-unit>
<trans-unit id="SpecifyIFormatProviderMessageIFormatProviderAlternate">
<source>The behavior of '{0}' could vary based on the current user's locale settings. Replace this call in '{1}' with a call to '{2}'.</source>
<target state="translated">“{0}”的行为可能因当前用户的区域设置而异。请将“{1}”中的此调用替换为对“{2}”的调用。</target>
<note />
</trans-unit>
<trans-unit id="SpecifyIFormatProviderMessageUICultureString">
<source>'{0}' passes '{1}' as the 'IFormatProvider' parameter to '{2}'. This property returns a culture that is inappropriate for formatting methods.</source>
<target state="translated">“{0}”将“{1}”作为 "IFormatProvider" 参数传递给“{2}”。此属性返回一个区域性,但它不适合格式化方法。</target>
<note />
</trans-unit>
<trans-unit id="SpecifyIFormatProviderMessageUICulture">
<source>'{0}' passes '{1}' as the 'IFormatProvider' parameter to '{2}'. This property returns a culture that is inappropriate for formatting methods.</source>
<target state="translated">“{0}”将“{1}”作为 "IFormatProvider" 参数传递给“{2}”。此属性返回一个区域性,但它不适合格式化方法。</target>
<note />
</trans-unit>
<trans-unit id="SpecifyStringComparisonTitle">
<source>Specify StringComparison</source>
<target state="translated">指定 StringComparison</target>
<note />
</trans-unit>
<trans-unit id="SpecifyStringComparisonDescription">
<source>A string comparison operation uses a method overload that does not set a StringComparison parameter. If the result will be displayed to the user, such as when sorting a list of items for display in a list box, specify 'StringComparison.CurrentCulture' or 'StringComparison.CurrentCultureIgnoreCase' as the 'StringComparison' parameter. If comparing case-insensitive identifiers, such as file paths, environment variables, or registry keys and values, specify 'StringComparison.OrdinalIgnoreCase'. Otherwise, if comparing case-sensitive identifiers, specify 'StringComparison.Ordinal'.</source>
<target state="translated">字符串比较运算使用不设置 StringComparison 参数的方法重载。如果要向用户显示结果(例如,在对某个项列表进行排序以便在列表框中显示时),请指定 "StringComparison.CurrentCulture" 或 "StringComparison.CurrentCultureIgnoreCase" 作为 "StringComparison" 参数。如果比较不区分大小写的标识符(例如,文件路径、环境变量或注册表项和值),则指定 "StringComparison.OrdinalIgnoreCase"。或者,如果比较区分大小写的标识符,则指定 "StringComparison.Ordinal"。</target>
<note />
</trans-unit>
<trans-unit id="SpecifyStringComparisonMessage">
<source>The behavior of '{0}' could vary based on the current user's locale settings. Replace this call in '{1}' with a call to '{2}'.</source>
<target state="translated">“{0}”的行为可能因当前用户的区域设置而异。请将“{1}”中的此调用替换为对“{2}”的调用。</target>
<note />
</trans-unit>
<trans-unit id="NormalizeStringsToUppercaseTitle">
<source>Normalize strings to uppercase</source>
<target state="translated">将字符串规范化为大写</target>
<note />
</trans-unit>
<trans-unit id="NormalizeStringsToUppercaseDescription">
<source>Strings should be normalized to uppercase. A small group of characters cannot make a round trip when they are converted to lowercase. To make a round trip means to convert the characters from one locale to another locale that represents character data differently, and then to accurately retrieve the original characters from the converted characters.</source>
<target state="translated">字符串应规范化为大写。有少量字符在转换为小写后不能转换回来。往返转换是指将字符从一个区域设置转换为按其他方式表示字符数据的另一区域设置,然后准确地从转换后的字符中检索到原始字符。</target>
<note />
</trans-unit>
<trans-unit id="NormalizeStringsToUppercaseMessageToUpper">
<source>In method '{0}', replace the call to '{1}' with '{2}'.</source>
<target state="translated">在方法“{0}”中,将对“{1}”的调用替换为“{2}”。</target>
<note />
</trans-unit>
<trans-unit id="CallGCSuppressFinalizeCorrectlyTitle">
<source>Dispose methods should call SuppressFinalize</source>
<target state="translated">Dispose 方法应调用 SuppressFinalize</target>
<note />
</trans-unit>
<trans-unit id="CallGCSuppressFinalizeCorrectlyDescription">
<source>A method that is an implementation of Dispose does not call GC.SuppressFinalize; or a method that is not an implementation of Dispose calls GC.SuppressFinalize; or a method calls GC.SuppressFinalize and passes something other than this (Me in Visual?Basic).</source>
<target state="translated">表示 Dispose 实现的方法没有调用 GC.SuppressFinalize;或不表示 Dispose 实现的方法调用了 GC.SuppressFinalize;或方法调用了 GC.SuppressFinalize 并传递 this (在 Visual Basic 中是 Me)以外的某个值。</target>
<note />
</trans-unit>
<trans-unit id="CallGCSuppressFinalizeCorrectlyMessageNotCalledWithFinalizer">
<source>Change {0} to call {1}. This will prevent unnecessary finalization of the object once it has been disposed and it has fallen out of scope.</source>
<target state="translated">将 {0} 更改为调用 {1}。这样可以防止当对象已释放并超出范围时,对该对象进行不必要的终止。</target>
<note />
</trans-unit>
<trans-unit id="CallGCSuppressFinalizeCorrectlyMessageNotCalled">
<source>Change {0} to call {1}. This will prevent derived types that introduce a finalizer from needing to re-implement 'IDisposable' to call it.</source>
<target state="translated">将 {0} 更改为调用 {1}。这将使引入终结器的派生类型无需重新实现 "IDisposable" 即可调用它。</target>
<note />
</trans-unit>
<trans-unit id="CallGCSuppressFinalizeCorrectlyMessageNotPassedThis">
<source>{0} calls {1} on something other than itself. Change the call site to pass 'this' ('Me' in Visual Basic) instead.</source>
<target state="translated">{0} 对除自身以外的其他对象调用 {1}。请更改调用站点,改而传递 "this" (在 Visual Basic 中为 "Me")。</target>
<note />
</trans-unit>
<trans-unit id="CallGCSuppressFinalizeCorrectlyMessageOutsideDispose">
<source>{0} calls {1}, a method that is typically only called within an implementation of 'IDisposable.Dispose'. Refer to the IDisposable pattern for more information.</source>
<target state="translated">{0} 调用 {1},该方法通常只在 "IDisposable.Dispose" 实现内部调用。有关详细信息,请参见 IDisposable 模式。</target>
<note />
</trans-unit>
<trans-unit id="InstantiateArgumentExceptionsCorrectlyTitle">
<source>Instantiate argument exceptions correctly</source>
<target state="translated">正确实例化参数异常</target>
<note />
</trans-unit>
<trans-unit id="InstantiateArgumentExceptionsCorrectlyDescription">
<source>A call is made to the default (parameterless) constructor of an exception type that is or derives from ArgumentException, or an incorrect string argument is passed to a parameterized constructor of an exception type that is or derives from ArgumentException.</source>
<target state="translated">调用了 ArgumentException 异常类型或其派生异常类型的默认(无参数)构造函数,或将不正确的字符串参数传递给 ArgumentException. 异常类型或其派生异常类型的参数化构造函数。</target>
<note />
</trans-unit>
<trans-unit id="InstantiateArgumentExceptionsCorrectlyMessageNoArguments">
<source>Call the {0} constructor that contains a message and/or paramName parameter.</source>
<target state="translated">调用 {0} 构造函数,该函数包含 message 和/或 paramName 参数。</target>
<note />
</trans-unit>
<trans-unit id="InstantiateArgumentExceptionsCorrectlyMessageIncorrectMessage">
<source>Method {0} passes parameter name '{1}' as the {2} argument to a {3} constructor. Replace this argument with a descriptive message and pass the parameter name in the correct position.</source>
<target state="translated">方法 {0} 将参数名“{1}”作为变量 {2} 传递给构造函数 {3}。请将此参数替换为一则说明性消息并在正确的位置传递参数名。</target>
<note />
</trans-unit>
<trans-unit id="InstantiateArgumentExceptionsCorrectlyMessageIncorrectParameterName">
<source>Method {0} passes '{1}' as the {2} argument to a {3} constructor. Replace this argument with one of the method's parameter names. Note that the provided parameter name should have the exact casing as declared on the method.</source>
<target state="translated">方法 {0} 将“{1}”作为变量 {2} 传递给构造函数 {3}。请将此参数替换为该方法的某个参数名。请注意,所提供的参数名的大小写应与方法中声明的大小写完全一致。</target>
<note />
</trans-unit>
<trans-unit id="UseArrayEmpty">
<source>Use Array.Empty</source>
<target state="translated">使用 Array.Empty</target>
<note />
</trans-unit>
<trans-unit id="BinaryFormatterMethodUsedDescription">
<source>The method '{0}' is insecure when deserializing untrusted data. If you need to instead detect BinaryFormatter deserialization without a SerializationBinder set, then disable rule CA2300, and enable rules CA2301 and CA2302.</source>
<target state="translated">反序列化不受信任的数据时,方法“{0}”不安全。如果需要在未设置 SerializationBinder 的情况下改为检测 BinaryFormatter 反序列化,则请禁用 CA2300 规则,并启用 CA2301 和 CA2302 规则。</target>
<note />
</trans-unit>
<trans-unit id="BinaryFormatterMethodUsedMessage">
<source>The method '{0}' is insecure when deserializing untrusted data.</source>
<target state="translated">对不受信任的数据进行反序列化时,方法“{0}”不安全。</target>
<note />
</trans-unit>
<trans-unit id="BinaryFormatterMethodUsedTitle">
<source>Do not use insecure deserializer BinaryFormatter</source>
<target state="translated">请勿使用不安全的反序列化程序 BinaryFormatter</target>
<note />
</trans-unit>
<trans-unit id="DoNotDisableUsingServicePointManagerSecurityProtocolsMessage">
<source>Do not set Switch.System.ServiceModel.DisableUsingServicePointManagerSecurityProtocols to true. Setting this switch limits Windows Communication Framework (WCF) to using Transport Layer Security (TLS) 1.0, which is insecure and obsolete.</source>
<target state="translated">不要将 Switch.System.ServiceModel.DisableUsingServicePointManagerSecurityProtocols 设置为 true。设置此开关会将 Windows Communication Framework (WCF)限制为使用传输层安全性(TLS) 1.0,而该层不安全且已过时。</target>
<note />
</trans-unit>
<trans-unit id="DoNotDisableUsingServicePointManagerSecurityProtocolsTitle">
<source>Do not disable ServicePointManagerSecurityProtocols</source>
<target state="translated">不禁用 ServicePointManagerSecurityProtocols</target>
<note />
</trans-unit>
<trans-unit id="JavaScriptSerializerMaybeWithSimpleTypeResolverMessage">
<source>The method '{0}' is insecure when deserializing untrusted data with a JavaScriptSerializer initialized with a SimpleTypeResolver. Ensure that the JavaScriptSerializer is initialized without a JavaScriptTypeResolver specified, or initialized with a JavaScriptTypeResolver that limits the types of objects in the deserialized object graph.</source>
<target state="needs-review-translation">使用通过 SimpleTypeResolver 初始化的 JavaScriptSerializer 反序列化不可信数据时,{0} 方法不安全。请确保初始化 JavaScriptSerializer 但不指定 JavaScriptTypeResolver,或使用限制为反序列化对象图形中的对象类型的 JavaScriptTypeResolver 初始化该对象。</target>
<note />
</trans-unit>
<trans-unit id="JavaScriptSerializerMaybeWithSimpleTypeResolverTitle">
<source>Ensure JavaScriptSerializer is not initialized with SimpleTypeResolver before deserializing</source>
<target state="translated">请确保 JavaScriptSerializer 在反序列化之前未使用 SimpleTypeResolver 初始化</target>
<note />
</trans-unit>
<trans-unit id="JavaScriptSerializerWithSimpleTypeResolverMessage">
<source>The method '{0}' is insecure when deserializing untrusted data with a JavaScriptSerializer initialized with a SimpleTypeResolver. Initialize JavaScriptSerializer without a JavaScriptTypeResolver specified, or initialize with a JavaScriptTypeResolver that limits the types of objects in the deserialized object graph.</source>
<target state="needs-review-translation">使用通过 SimpleTypeResolver 初始化的 JavaScriptSerializer 反序列化不可信数据时,{0} 方法不安全。请初始化 JavaScriptSerializer 但不指定 JavaScriptTypeResolver,或使用限制为反序列化对象图形中的对象类型的 JavaScriptTypeResolver 初始化该对象。</target>
<note />
</trans-unit>
<trans-unit id="JavaScriptSerializerWithSimpleTypeResolverTitle">
<source>Do not deserialize with JavaScriptSerializer using a SimpleTypeResolver</source>
<target state="translated">请勿通过使用 SimpleTypeResolver 的 JavaScriptSerializer 进行反序列化</target>
<note />
</trans-unit>
<trans-unit id="JsonNetInsecureSettingsMessage">
<source>When deserializing untrusted input, allowing arbitrary types to be deserialized is insecure. When using JsonSerializerSettings, use TypeNameHandling.None, or for values other than None, restrict deserialized types with a SerializationBinder.</source>
<target state="new">When deserializing untrusted input, allowing arbitrary types to be deserialized is insecure. When using JsonSerializerSettings, use TypeNameHandling.None, or for values other than None, restrict deserialized types with a SerializationBinder.</target>
<note />
</trans-unit>
<trans-unit id="JsonNetInsecureSettingsTitle">
<source>Do not use insecure JsonSerializerSettings</source>
<target state="new">Do not use insecure JsonSerializerSettings</target>
<note />
</trans-unit>
<trans-unit id="JsonNetMaybeInsecureSettingsMessage">
<source>When deserializing untrusted input, allowing arbitrary types to be deserialized is insecure. When using JsonSerializerSettings, ensure TypeNameHandling.None is specified, or for values other than None, ensure a SerializationBinder is specified to restrict deserialized types.</source>
<target state="new">When deserializing untrusted input, allowing arbitrary types to be deserialized is insecure. When using JsonSerializerSettings, ensure TypeNameHandling.None is specified, or for values other than None, ensure a SerializationBinder is specified to restrict deserialized types.</target>
<note />
</trans-unit>
<trans-unit id="JsonNetMaybeInsecureSettingsTitle">
<source>Ensure that JsonSerializerSettings are secure</source>
<target state="new">Ensure that JsonSerializerSettings are secure</target>
<note />
</trans-unit>
<trans-unit id="JsonNetTypeNameHandlingDescription">
<source>Deserializing JSON when using a TypeNameHandling value other than None can be insecure. If you need to instead detect Json.NET deserialization when a SerializationBinder isn't specified, then disable rule CA2326, and enable rules CA2327, CA2328, CA2329, and CA2330.</source>
<target state="new">Deserializing JSON when using a TypeNameHandling value other than None can be insecure. If you need to instead detect Json.NET deserialization when a SerializationBinder isn't specified, then disable rule CA2326, and enable rules CA2327, CA2328, CA2329, and CA2330.</target>
<note />
</trans-unit>
<trans-unit id="JsonNetTypeNameHandlingMessage">
<source>Deserializing JSON when using a TypeNameHandling value other than None can be insecure.</source>
<target state="new">Deserializing JSON when using a TypeNameHandling value other than None can be insecure.</target>
<note />
</trans-unit>
<trans-unit id="JsonNetTypeNameHandlingTitle">
<source>Do not use TypeNameHandling values other than None</source>
<target state="new">Do not use TypeNameHandling values other than None</target>
<note />
</trans-unit>
<trans-unit id="LosFormatterMethodUsedMessage">