-
Notifications
You must be signed in to change notification settings - Fork 457
/
MicrosoftNetCoreAnalyzersResources.zh-Hant.xlf
1707 lines (1707 loc) · 142 KB
/
MicrosoftNetCoreAnalyzersResources.zh-Hant.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-Hant" 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 值呼叫 TolmmutableCollection</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/Invoke</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/Invokes 方法 '{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">將布林值 PInvoke 引數標記為 MarshalAs</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">將 MarshalAsAttribute 新增至 P/Invoke {1} 的參數 {0}。若相對應的非受控參數為 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">將 MarshalAsAttribute 新增至 P/Invoke {0} 的傳回型別。若相對應的非受控傳回型別為 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 屬性會通知 ResourceManager 用於顯示組件之中性文化特性 (Culture) 資源的語言。如此可改善載入第一項源的查閱效能,且可減少您的工作集。</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">新增可序列化屬性</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">請使用建議的處置模式,確認會在所有路徑上,處置由 '{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">請使用建議的處置模式,確認會在所有例外狀況路徑上,處置由 '{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">在 '{0}' 所建立的物件上,於所有參考 System.IDisposable.Dispose 的項目前呼叫它,超出範圍。</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">將 GetObjectData 的實作加入類型 {0}。</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} 的序列化建構函式 (sealed 類型) 宣告為 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} 的序列化建構函式 (unsealed 類型) 宣告為 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">若要通用語言執行階段將其辨識為可序列化,即使類型透過實作 ISerializable 介面使用自訂序列化常式,也必須使用 SerializableAttribute 屬性來標示類型。</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">將 'private void OnDeserialized(StreamingContext)' 方法加入類型 {0},並為它加上 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">將 'private void OnDeserializing(StreamingContext)' 方法加入類型 {0},並為它加上 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} 會以 'StringComparison' 參數形式將 '{1}' 傳遞給 {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} 會以 'StringComparison' 參數形式將 '{1}' 傳遞給 {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">使用 String.Length 屬性或 String.IsNullOrEmpty 方法來比較字串的速度,大幅快過於使用 Equals。</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' 方法測試空白字串,而非使用相等檢查。</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">請勿在接收損毀狀態例外狀況的程式碼中,撰寫一般的 catch 處理常式。</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 的格式化引數,並未包含與每個物件引數相對應的格式項目,反之亦然。</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}' 的建構函式中,將目前為 "{2}" 的引數值 '{1}',變更為可正確剖析成 '{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}' 的行為可能會因目前使用者的地區設定而異。以呼叫 '{2}' 來取代 '{1}' 中的此呼叫。</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 或 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}' 的行為可能會因目前使用者的地區設定而異。以呼叫 '{2}' 來取代 '{1}' 中的此呼叫。</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}' 的行為可能會因目前使用者的地區設定而異。以呼叫 '{2}' 來取代 '{1}' 中的此呼叫。</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}'。此屬性會傳回不適合格式化方法的文化特性 (Culture)。</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}'。此屬性會傳回不適合格式化方法的文化特性 (Culture)。</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}' 的行為可能會因目前使用者的地區設定而異。以呼叫 '{2}' 來取代 '{1}' 中的此呼叫。</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}' 中,以 '{2}' 取代對 '{1}' 的呼叫。</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">請呼叫包含 message 及 (或) paramName 參數的 {0} 建構函式。</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}' 不安全。如果您需要改為偵測 BinaryFormatter 還原序列化,而不想要設定 SerializationBinder,則請停用規則 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}' 會不安全。請在未指定 JavaScriptTypeResolver 的情況下將 JavaScriptSerializer 初始化,或以在還原序列化物件圖形中限制該物件類型的 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">