-
Notifications
You must be signed in to change notification settings - Fork 1.3k
/
Strings.resx
1879 lines (1868 loc) · 118 KB
/
Strings.resx
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"?>
<root>
<!--
Microsoft ResX Schema
Version 2.0
The primary goals of this format is to allow a simple XML format
that is mostly human readable. The generation and parsing of the
various data types are done through the TypeConverter classes
associated with the data types.
Example:
... ado.net/XML headers & schema ...
<resheader name="resmimetype">text/microsoft-resx</resheader>
<resheader name="version">2.0</resheader>
<resheader name="reader">System.Resources.ResXResourceReader, System.Windows.Forms, ...</resheader>
<resheader name="writer">System.Resources.ResXResourceWriter, System.Windows.Forms, ...</resheader>
<data name="Name1"><value>this is my long string</value><comment>this is a comment</comment></data>
<data name="Color1" type="System.Drawing.Color, System.Drawing">Blue</data>
<data name="Bitmap1" mimetype="application/x-microsoft.net.object.binary.base64">
<value>[base64 mime encoded serialized .NET Framework object]</value>
</data>
<data name="Icon1" type="System.Drawing.Icon, System.Drawing" mimetype="application/x-microsoft.net.object.bytearray.base64">
<value>[base64 mime encoded string representing a byte array form of the .NET Framework object]</value>
<comment>This is a comment</comment>
</data>
There are any number of "resheader" rows that contain simple
name/value pairs.
Each data row contains a name, and value. The row also contains a
type or mimetype. Type corresponds to a .NET class that support
text/value conversion through the TypeConverter architecture.
Classes that don't support this are serialized and stored with the
mimetype set.
The mimetype is used for serialized objects, and tells the
ResXResourceReader how to depersist the object. This is currently not
extensible. For a given mimetype the value must be set accordingly:
Note - application/x-microsoft.net.object.binary.base64 is the format
that the ResXResourceWriter will generate, however the reader can
read any of the formats listed below.
mimetype: application/x-microsoft.net.object.binary.base64
value : The object must be serialized with
: System.Runtime.Serialization.Formatters.Binary.BinaryFormatter
: and then encoded with base64 encoding.
mimetype: application/x-microsoft.net.object.soap.base64
value : The object must be serialized with
: System.Runtime.Serialization.Formatters.Soap.SoapFormatter
: and then encoded with base64 encoding.
mimetype: application/x-microsoft.net.object.bytearray.base64
value : The object must be serialized into a byte array
: using a System.ComponentModel.TypeConverter
: and then encoded with base64 encoding.
-->
<xsd:schema id="root" xmlns="" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:msdata="urn:schemas-microsoft-com:xml-msdata">
<xsd:import namespace="http://www.w3.org/XML/1998/namespace" />
<xsd:element name="root" msdata:IsDataSet="true">
<xsd:complexType>
<xsd:choice maxOccurs="unbounded">
<xsd:element name="metadata">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="value" type="xsd:string" minOccurs="0" />
</xsd:sequence>
<xsd:attribute name="name" use="required" type="xsd:string" />
<xsd:attribute name="type" type="xsd:string" />
<xsd:attribute name="mimetype" type="xsd:string" />
<xsd:attribute ref="xml:space" />
</xsd:complexType>
</xsd:element>
<xsd:element name="assembly">
<xsd:complexType>
<xsd:attribute name="alias" type="xsd:string" />
<xsd:attribute name="name" type="xsd:string" />
</xsd:complexType>
</xsd:element>
<xsd:element name="data">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="value" type="xsd:string" minOccurs="0" msdata:Ordinal="1" />
<xsd:element name="comment" type="xsd:string" minOccurs="0" msdata:Ordinal="2" />
</xsd:sequence>
<xsd:attribute name="name" type="xsd:string" use="required" msdata:Ordinal="1" />
<xsd:attribute name="type" type="xsd:string" msdata:Ordinal="3" />
<xsd:attribute name="mimetype" type="xsd:string" msdata:Ordinal="4" />
<xsd:attribute ref="xml:space" />
</xsd:complexType>
</xsd:element>
<xsd:element name="resheader">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="value" type="xsd:string" minOccurs="0" msdata:Ordinal="1" />
</xsd:sequence>
<xsd:attribute name="name" type="xsd:string" use="required" />
</xsd:complexType>
</xsd:element>
</xsd:choice>
</xsd:complexType>
</xsd:element>
</xsd:schema>
<resheader name="resmimetype">
<value>text/microsoft-resx</value>
</resheader>
<resheader name="version">
<value>2.0</value>
</resheader>
<resheader name="reader">
<value>System.Resources.ResXResourceReader, System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</value>
</resheader>
<resheader name="writer">
<value>System.Resources.ResXResourceWriter, System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</value>
</resheader>
<data name="AmbiguousTaskParameterError" xml:space="preserve">
<value>MSB4001: The "{0}" task has more than one parameter called "{1}".</value>
<comment>{StrBegin="MSB4001: "}UE: This message is shown when a task has more than one .NET property with the same name -- it's unclear which of
those properties the task wants to use as a parameter in project files.</comment>
</data>
<data name="AttributeTypeLoadError" xml:space="preserve">
<value>MSB4002: There was a failure retrieving the attributes for parameters in the "{0}" task. {1}</value>
<comment>{StrBegin="MSB4002: "}UE: This message is shown when the .NET attributes that a task's .NET properties are decorated with, cannot be
retrieved -- this is typically because the .NET classes that define the .NET attributes cannot be loaded because the assembly
they are defined in cannot be found, or the classes themselves cannot be found.</comment>
</data>
<data name="BadlyCasedSpecialTaskAttribute" xml:space="preserve">
<value>MSB4003: "{0}" is a reserved attribute of the <{1}> element, and must be spelled with the correct casing. This attribute cannot be used as a parameter to the "{2}" task.</value>
<comment>{StrBegin="MSB4003: "}UE: Tasks are not allowed to use incorrect case for reserved attributes on the task nodes e.g. "continueonerror"
instead of the "ContinueOnError".</comment>
</data>
<data name="BuildInProgress" xml:space="preserve">
<value>The operation cannot be completed because a build is already in progress.</value>
</data>
<data name="NoBuildInProgress" xml:space="preserve">
<value>The operation cannot be completed because BeginBuild has not yet been called.</value>
</data>
<data name="WaitingForEndOfBuild" xml:space="preserve">
<value>The operation cannot be completed because EndBuild has already been called but existing submissions have not yet completed.</value>
</data>
<data name="SubmissionAlreadyComplete" xml:space="preserve">
<value>The operation cannot be completed because the submission has already been executed.</value>
</data>
<data name="ShouldNotDisposeWhenBuildManagerActive" xml:space="preserve">
<value>Cannot dispose the build manager because it is not idle.</value>
</data>
<data name="BuildAbortedWithMessage" xml:space="preserve">
<value>MSB4197: Build was canceled. {0}</value>
<comment>{StrBegin="MSB4197: "} Error when the build stops suddenly for some reason. For example, because a child node died.</comment>
</data>
<data name="BuildFinishedFailure" xml:space="preserve">
<value>Build FAILED.</value>
</data>
<data name="BuildFinishedSuccess" xml:space="preserve">
<value>Build succeeded.</value>
</data>
<data name="BuildStartedWithTime" xml:space="preserve">
<value>Build started {0}.</value>
</data>
<data name="BuildTargetCompletely" xml:space="preserve">
<value>Building target "{0}" completely.</value>
<comment>{0} is the name of the target.</comment>
</data>
<data name="BuildTargetCompletelyNoInputsSpecified" xml:space="preserve">
<value>No input files were specified.</value>
</data>
<data name="BuildTargetCompletelyInputNewer" xml:space="preserve">
<value>Input file "{0}" is newer than output file "{1}".</value>
<comment>{0} and {1} are filenames on disk.</comment>
</data>
<data name="BuildTargetCompletelyOutputDoesntExist" xml:space="preserve">
<value>Output file "{0}" does not exist.</value>
<comment>{0} is a filename on disk.</comment>
</data>
<data name="BuildTargetCompletelyInputDoesntExist" xml:space="preserve">
<value>Input file "{0}" does not exist.</value>
<comment>{0} is a filename on disk.</comment>
</data>
<data name="BuildTargetPartially" xml:space="preserve">
<value>Building target "{0}" partially, because some output files are out of date with respect to their input files.</value>
<comment>{0} is the name of the target.</comment>
</data>
<data name="BuildTargetPartiallyInputNewer" xml:space="preserve">
<value>[{0}: Input={1}, Output={2}] Input file is newer than output file.</value>
<comment>{0} is the name of an MSBuild item. {1} and {2} are filenames on disk.</comment>
</data>
<data name="BuildTargetPartiallyOutputDoesntExist" xml:space="preserve">
<value>[{0}: Input={1}, Output={2}] Output file does not exist.</value>
<comment>{0} is the name of an MSBuild item. {1} and {2} are filenames on disk.</comment>
</data>
<data name="BuildTargetPartiallyInputDoesntExist" xml:space="preserve">
<value>[{0}: Input={1}, Output={2}] Input file does not exist.</value>
<comment>{0} is the name of an MSBuild item. {1} and {2} are filenames on disk.</comment>
</data>
<data name="CannotAccessKnownAttributes" xml:space="preserve">
<value>The attribute "{0}" is a known MSBuild attribute, and cannot be accessed using this method.</value>
</data>
<data name="CannotEvaluateItemMetadata" xml:space="preserve">
<value>MSB4023: Cannot evaluate the item metadata "%({0})". {1}</value>
<comment>{StrBegin="MSB4023: "}UE: This message is shown when the value of an item metadata cannot be computed for some reason e.g. trying to apply
%(RootDir) to an item-spec that's not a valid path, would result in this error.
LOCALIZATION: "{1}" is a localized message explaining the problem.</comment>
</data>
<data name="CannotExpandItemMetadata" xml:space="preserve">
<value>MSB4248: Cannot expand metadata in expression "{0}". {1}</value>
<comment>{StrBegin="MSB4248: "}UE: This message is shown when metadata cannot be expanded in an expression for some reason e.g. trying to apply
%(RootDir) to an item-spec that's not a valid path would result in this error.
LOCALIZATION: "{1}" is a localized message explaining the problem.</comment>
</data>
<data name="CouldNotFindMSBuildExe" xml:space="preserve">
<value>MSB4193: MSBuild.exe could not be launched as a child node as it could not be found at the location "{0}". If necessary, specify the correct location in the BuildParameters, or with the MSBUILD_EXE_PATH environment variable.</value>
<comment>{StrBegin="MSB4193: "}</comment>
</data>
<data name="CouldNotConnectToMSBuildExe" xml:space="preserve">
<value>MSB4218: Failed to successfully launch or connect to a child MSBuild.exe process. Verify that the MSBuild.exe "{0}" launches successfully, and that it is loading the same microsoft.build.dll that the launching process loaded. If the location seems incorrect, try specifying the correct location in the BuildParameters object, or with the MSBUILD_EXE_PATH environment variable.</value>
<comment>{StrBegin="MSB4218: "}</comment>
</data>
<data name="CannotModifyReservedItem" xml:space="preserve">
<value>MSB4117: The "{0}" item name is reserved, and cannot be used.</value>
<comment>{StrBegin="MSB4117: "}UE: This message is shown when the user tries to redefine one of the reserved MSBuild items e.g. @(Choose)</comment>
</data>
<data name="CannotModifyReservedItemMetadata" xml:space="preserve">
<value>MSB4118: The "{0}" item metadata name is reserved, and cannot be used.</value>
<comment>{StrBegin="MSB4118: "}UE: This message is shown when the user tries to redefine one of the reserved MSBuild item metadata names e.g. %(FullPath). Only MSBuild can set those.</comment>
</data>
<data name="CannotModifyReservedProperty" xml:space="preserve">
<value>MSB4004: The "{0}" property is reserved, and cannot be modified.</value>
<comment>{StrBegin="MSB4004: "}UE: This message is shown when the user tries to redefine one of the reserved MSBuild properties e.g. $(MSBuildProjectFile)</comment>
</data>
<data name="CannotPassMultipleItemsIntoScalarParameter" xml:space="preserve">
<value>MSB4094: "{0}" is an invalid value for the "{1}" parameter of the "{3}" task. Multiple items cannot be passed into a parameter of type "{2}".</value>
<comment>{StrBegin="MSB4094: "}
UE: This error is shown when a project tries to pass multiple items into a task parameter of type ITaskItem (singular).
</comment>
</data>
<data name="CannotPassMultipleItemsIntoScalarFunction" xml:space="preserve">
<value>MSB4115: The "{0}" function only accepts a scalar value, but its argument "{1}" evaluates to "{2}" which is not a scalar value.</value>
<comment>{StrBegin="MSB4115: "}
UE: This error is shown when a project tries to pass multiple items into a function in a conditional expression, that can only accept a scalar value (such as the "exists()" function).
</comment>
</data>
<data name="CannotReferenceItemMetadataWithoutItemName" xml:space="preserve">
<value>MSB4095: The item metadata %({0}) is being referenced without an item name. Specify the item name by using %(itemname.{0}).</value>
<comment>{StrBegin="MSB4095: "}</comment>
</data>
<data name="ChildElementsBelowRemoveNotAllowed" xml:space="preserve">
<value>MSB4162: <{0}> is not valid. Child elements are not allowed below a item remove element.</value>
<comment>{StrBegin="MSB4162: "}</comment>
</data>
<data name="ChildExitedPrematurely" xml:space="preserve">
<value>MSB4166: Child node "{0}" exited prematurely. Shutting down. Diagnostic information may be found in files in "{1}" and will be named MSBuild_*.failure.txt. This location can be changed by setting the MSBUILDDEBUGPATH environment variable to a different directory.{2}</value>
<comment>{StrBegin="MSB4166: "} {2} is exception text if any</comment>
</data>
<data name="ChooseMustContainWhen" xml:space="preserve">
<value>MSB4085: A <Choose> must contain at least one <When>.</value>
<comment>{StrBegin="MSB4085: "}</comment>
</data>
<data name="ChooseOverflow" xml:space="preserve">
<value>MSB4114: <Choose> elements cannot be nested more than {0} levels deep.</value>
<comment>{StrBegin="MSB4114: "}UE: This message appears if the project file contains unreasonably nested Choose elements.
LOCALIZATION: Do not localize "Choose" as it is an XML element name.</comment>
</data>
<data name="CircularDependency" xml:space="preserve">
<value>MSB4006: There is a circular dependency in the target dependency graph involving target "{0}".</value>
<comment>{StrBegin="MSB4006: "}UE: This message is shown when the build engine detects a target referenced in a circular manner -- a project cannot
request a target to build itself (perhaps via a chain of other targets).</comment>
</data>
<data name="CircularDependencyInTargetGraph" xml:space="preserve">
<value>MSB4006: There is a circular dependency in the target dependency graph involving target "{0}". Since "{1}" has "{2}" dependence on "{3}", the circular is "{4}".</value>
<comment>{StrBegin="MSB4006: "}UE: This message is shown when the build engine detects a target referenced in a circular manner -- a project cannot
request a target to build itself (perhaps via a chain of other targets).</comment>
</data>
<data name="ComparisonOnNonNumericExpression" xml:space="preserve">
<value>MSB4086: A numeric comparison was attempted on "{1}" that evaluates to "{2}" instead of a number, in condition "{0}".</value>
<comment>{StrBegin="MSB4086: "}</comment>
</data>
<data name="ConditionMaybeEvaluatedIncorrectly" xml:space="preserve">
<value>MSB4130: The condition "{0}" may have been evaluated incorrectly in an earlier version of MSBuild. Please verify that the order of the AND and OR clauses is written as intended. To avoid this warning, add parentheses to make the evaluation order explicit.</value>
<comment>{StrBegin="MSB4130: "}</comment>
</data>
<data name="ConditionNotBoolean" xml:space="preserve">
<value>MSB4087: Specified condition "{0}" does not evaluate to a boolean.</value>
<comment>{StrBegin="MSB4087: "}</comment>
</data>
<data name="ConditionNotBooleanDetail" xml:space="preserve">
<value>MSB4113: Specified condition "{0}" evaluates to "{1}" instead of a boolean.</value>
<comment>{StrBegin="MSB4113: "}</comment>
</data>
<data name="ConfigFileReadError" xml:space="preserve">
<value>MSB4136: Error reading the toolset information from the configuration file "{0}". {1}</value>
<comment>{StrBegin="MSB4136: "}</comment>
</data>
<data name="ConflictingValuesOfMSBuildToolsPath" xml:space="preserve">
<value>MSB4142: MSBuildToolsPath is not the same as MSBuildBinPath for the ToolsVersion "{0}" defined at "{1}". If both are present they must have the same value.</value>
<comment>{StrBegin="MSB4142: "}</comment>
</data>
<data name="DefaultTasksFileFailure" xml:space="preserve">
<value>MSB4009: The default tasks file could not be successfully loaded. {0}</value>
<comment>{StrBegin="MSB4009: "}UE: This message is shown when one of the default tasks file (*.tasks) located alongside the MSBuild binaries cannot
be opened/parsed. "{0}" contains a message explaining why. The filename itself is not part of the message but is provided
separately to loggers.
LOCALIZATION: "{0}" is a message from some FX method and is already localized.</comment>
</data>
<data name="DefaultTasksFileLoadFailureWarning" xml:space="preserve">
<value>MSB4010: The "{0}" files could not be successfully loaded from their expected location "{1}". Default tasks will not be available. {2}</value>
<comment>{StrBegin="MSB4010: "}UE: This message is shown when the default tasks files that are located alongside the MSBuild binaries cannot be
found, either because they don't exist, or because of lack of permissions. "{2}" contains a message explaining why.
LOCALIZATION: "{2}" is a message from some FX method and is already localized.</comment>
</data>
<data name="ImportIntroducesCircularity" xml:space="preserve">
<value>Importing the file "{0}" into the file "{1}" results in a circular dependency.</value>
<comment>
{0} is a file imported into the file "{1}" such that it results in a circular dependency. For e.g. if t1.targets imports
t2.targets and t2.targets tries to import t1.targets, then it results in a circular dependency.
</comment>
</data>
<data name="ChangeWave_InvalidFormat" xml:space="preserve">
<value>MSB4271: Environment variable MSBuildDisableFeaturesFromVersion is set to an invalid format. Enabling all change wave versions. Entered value: {0}. Current Change Waves: {1}.</value>
<comment>{StrBegin="MSB4271: "}UE: Value should be of the format: xx.yy</comment>
</data>
<data name="ChangeWave_OutOfRotation" xml:space="preserve">
<value>MSB4272: Environment variable MSBuildDisableFeaturesFromVersion is set to a version that is out of rotation. Defaulting to Change Wave version: {0}. Entered value: {1}. Current Change Waves: {2}.</value>
<comment>{StrBegin="MSB4272: "}</comment>
</data>
<data name="SearchPathsForMSBuildExtensionsPath" xml:space="preserve">
<value>Search paths being used for {0} are {1}</value>
</data>
<data name="TryingExtensionsPath" xml:space="preserve">
<value>Trying to import {0} using extensions path {1}</value>
</data>
<data name="OverrideTasksFileFailure" xml:space="preserve">
<value>MSB4194: The override tasks file could not be successfully loaded. {0}</value>
<comment>
{StrBegin="MSB4194: "}UE: This message is shown when one of the override tasks file (*.overridetasks) located alongside the MSBuild binaries cannot
be opened/parsed. "{0}" contains a message explaining why. The filename itself is not part of the message but is provided
separately to loggers.
LOCALIZATION: "{0}" is a message from some FX method and is already localized.
</comment>
</data>
<data name="OverrideTaskNotRootedPath" xml:space="preserve">
<value>The override tasks path "{0}" must not be a relative path and must exist on disk. Default tasks will not be overridden.</value>
<comment>
UE: This message is shown when the override tasks path in the registry or passed to the toolset is not a full path.
</comment>
</data>
<data name="OverrideTaskProblemWithPath" xml:space="preserve">
<value>A problem occurred loading the override tasks path "{0}". {1}</value>
<comment>
UE: This message is shown when the override tasks path in the registry or passed to the toolset is not a full path.
</comment>
</data>
<data name="OverrideTasksFileLoadFailureWarning" xml:space="preserve">
<value>MSB4196: The "{0}" files could not be successfully loaded from their expected location "{1}". Default tasks will not be overridden. {2}</value>
<comment>
{StrBegin="MSB4196: "}UE: This message is shown when the override tasks files that are located alongside the MSBuild binaries cannot be
found, either because they don't exist, or because of lack of permissions. "{2}" contains a message explaining why.
LOCALIZATION: "{2}" is a message from some FX method and is already localized.
</comment>
</data>
<data name="TasksPropertyBagError" xml:space="preserve">
<value>MSB4195: There was an error gathering properties for tasks file evaluation. {0}</value>
<comment>
{StrBegin="MSB4195: "}UE: This message is shown when the gathering of properties for the evaluation of override and defaults tasks has an exception. "{0"} will be the exception message</comment>
</data>
<data name="DefaultToolsVersionNotFound" xml:space="preserve">
<value>MSB4133: A default tools version "{0}" was specified, but its definition could not be found.</value>
<comment>{StrBegin="MSB4133: "}</comment>
</data>
<data name="DuplicateImport" xml:space="preserve">
<value>MSB4011: "{0}" cannot be imported again. It was already imported at "{1}". This is most likely a build authoring error. This subsequent import will be ignored. {2}</value>
<comment>{StrBegin="MSB4011: "}</comment>
</data>
<data name="UsedUninitializedProperty" xml:space="preserve">
<value>MSB4211: The property "{0}" is being set to a value for the first time, but it was already consumed at "{1}".</value>
<comment>{StrBegin="MSB4211: "}</comment>
</data>
<data name="SelfImport" xml:space="preserve">
<value>MSB4210: "{0}" is attempting to import itself, directly or indirectly. This is most likely a build authoring error. The import will be ignored.</value>
<comment>{StrBegin="MSB4210: "}</comment>
</data>
<data name="DuplicateProjectExtensions" xml:space="preserve">
<value>MSB4079: The <ProjectExtensions> element occurs more than once.</value>
<comment>{StrBegin="MSB4079: "}</comment>
</data>
<data name="EmbeddedItemVectorCannotBeItemized" xml:space="preserve">
<value>MSB4012: The expression "{0}" cannot be used in this context. Item lists cannot be concatenated with other strings where an item list is expected. Use a semicolon to separate multiple item lists.</value>
<comment>{StrBegin="MSB4012: "}UE: This message is shown when the user does not properly specify an item list when an item list is expected
e.g. "badprefix@(foo)badsuffix" instead of "prefix; @(foo); suffix"</comment>
</data>
<data name="EndOfInputTokenName" xml:space="preserve">
<value>end of input</value>
<comment>This is the name of the "EndOfInput" token. It is displayed in quotes as the
unexpected char or token when the end of a conditional was unexpectedly reached.</comment>
</data>
<data name="ErrorConvertedIntoWarning" xml:space="preserve">
<value>The previous error was converted to a warning because the task was called with ContinueOnError=true.</value>
</data>
<data name="ErrorCount" xml:space="preserve">
<value>{0} Error(s)</value>
</data>
<data name="ErrorCreatingToolset" xml:space="preserve">
<value>MSB4159: Error creating the toolset "{0}". {1}</value>
<comment>{StrBegin="MSB4159: "}</comment>
</data>
<data name="ErrorEvaluatingToolsetPropertyExpression" xml:space="preserve">
<value>MSB4146: Cannot evaluate the property expression "{0}" found at "{1}". {2}</value>
<comment>{StrBegin="MSB4146: "}</comment>
</data>
<data name="ErrorWarningMessageNotSupported" xml:space="preserve">
<value>The <{0}> tag is no longer supported as a child of the <Project> element. Place this tag within a target, and add the name of the target to the "InitialTargets" attribute of the <Project> element.</value>
</data>
<data name="EvaluationStarted" xml:space="preserve">
<value>Evaluation started ("{0}")</value>
</data>
<data name="EvaluationFinished" xml:space="preserve">
<value>Evaluation finished ("{0}")</value>
</data>
<data name="ExecutingTaskInTaskHost" xml:space="preserve">
<value>Launching task "{0}" from assembly "{1}" in an external task host with a runtime of "{2}" and a process architecture of "{3}".</value>
</data>
<data name="ExpressionDoesNotEvaluateToBoolean" xml:space="preserve">
<value>MSB4100: Expected "{0}" to evaluate to a boolean instead of "{1}", in condition "{2}".</value>
<comment>{StrBegin="MSB4100: "}</comment>
</data>
<data name="FailedToRetrieveTaskOutputs" xml:space="preserve">
<value>MSB4028: The "{0}" task's outputs could not be retrieved from the "{1}" parameter. {2}</value>
<comment>{StrBegin="MSB4028: "}</comment>
</data>
<data name="FatalBuildError" xml:space="preserve">
<value>MSB4014: The build stopped unexpectedly because of an internal failure.</value>
<comment>{StrBegin="MSB4014: "}UE: This message is shown when an unhandled exception terminates the build. The cause is most likely a programming
error in the build engine.</comment>
</data>
<data name="FatalErrorDuringLoggerShutdown" xml:space="preserve">
<value>MSB4015: The build stopped unexpectedly because the "{0}" logger failed unexpectedly during shutdown.</value>
<comment>{StrBegin="MSB4015: "}UE: This message is used for a special exception that is thrown when a logger fails while shutting down (most likely
because of a programming error in the logger). When a logger dies, we cannot proceed with the build, and we throw a special
exception to abort the build.</comment>
</data>
<data name="FatalErrorWhileInitializingLogger" xml:space="preserve">
<value>MSB4016: The build stopped unexpectedly because the "{0}" logger failed unexpectedly during initialization.</value>
<comment>{StrBegin="MSB4016: "}UE: This message is used for a special exception that is thrown when a logger fails while initializing itself (most
likely because of a programming error in the logger). When a logger dies, we cannot proceed with the build, and we throw a
special exception to abort the build.</comment>
</data>
<data name="FatalErrorWhileLogging" xml:space="preserve">
<value>MSB4017: The build stopped unexpectedly because of an unexpected logger failure.</value>
<comment>{StrBegin="MSB4017: "}UE: This message is used for a special exception that is thrown when a logger fails while logging an event (most
likely because of a programming error in the logger). When a logger dies, we cannot proceed with the build, and we throw a
special exception to abort the build.</comment>
</data>
<data name="FatalTaskError" xml:space="preserve">
<value>MSB4018: The "{0}" task failed unexpectedly.</value>
<comment>{StrBegin="MSB4018: "}UE: This message is shown when a task terminates because of an unhandled exception. The cause is most likely a
programming error in the task; however, it is also possible that the unhandled exception originated in the engine, and was
surfaced through the task when the task called into the engine.</comment>
</data>
<data name="FailedToReceiveTaskThreadStatus" xml:space="preserve">
<value>MSB4187: Failed to receive a response from the task thread in the timeout period "{0}" ms. Shutting down.</value>
<comment>{StrBegin="MSB4187: "}</comment>
</data>
<data name="IllFormedCondition" xml:space="preserve">
<value>MSB4088: Condition "{0}" is improperly constructed.</value>
<comment>{StrBegin="MSB4088: "}</comment>
</data>
<data name="IllFormedEqualsInCondition" xml:space="preserve">
<value>MSB4105: Found an unexpected character '{2}' at position {1} in condition "{0}". Did you intend to use "=="?</value>
<comment>{StrBegin="MSB4105: "}</comment>
</data>
<data name="IllFormedItemListCloseParenthesisInCondition" xml:space="preserve">
<value>MSB4106: Expected an item list at position {1} in condition "{0}". Did you forget the closing parenthesis?</value>
<comment>{StrBegin="MSB4106: "}</comment>
</data>
<data name="IllFormedItemListOpenParenthesisInCondition" xml:space="preserve">
<value>MSB4107: Expected an item list at position {1} in condition "{0}". Did you forget the opening parenthesis after the '@'? To use a literal '@', use '%40' instead.</value>
<comment>{StrBegin="MSB4107: "}</comment>
</data>
<data name="IllFormedItemListQuoteInCondition" xml:space="preserve">
<value>MSB4108: Expected an item list at position {1} in condition "{0}". Did you forget to close a quote inside the item list expression?</value>
<comment>{StrBegin="MSB4108: "}</comment>
</data>
<data name="IllFormedPropertyCloseParenthesisInCondition" xml:space="preserve">
<value>MSB4109: Expected a property at position {1} in condition "{0}". Did you forget the closing parenthesis?</value>
<comment>{StrBegin="MSB4109: "}</comment>
</data>
<data name="IllFormedPropertyOpenParenthesisInCondition" xml:space="preserve">
<value>MSB4110: Expected a property at position {1} in condition "{0}". Did you forget the opening parenthesis after the '$'? To use a literal '$', use '%24' instead.</value>
<comment>{StrBegin="MSB4110: "}</comment>
</data>
<data name="IllFormedPropertySpaceInCondition" xml:space="preserve">
<value>MSB4259: Unexpected space at position "{1}" of condition "{0}". Did you forget to remove a space?</value>
<comment>{StrBegin="MSB4259: "}</comment>
</data>
<data name="IllFormedQuotedStringInCondition" xml:space="preserve">
<value>MSB4101: Expected a closing quote after position {1} in condition "{0}".</value>
<comment>{StrBegin="MSB4101: "}</comment>
</data>
<data name="ImportedProjectNotFound" xml:space="preserve">
<value>MSB4019: The imported project "{0}" was not found. Confirm that the expression in the Import declaration "{1}" is correct, and that the file exists on disk.</value>
<comment>{StrBegin="MSB4019: "}LOCALIZATION: <Import> should not be localized.</comment>
</data>
<data name="ImportedProjectFromExtensionsPathNotFoundFromAppConfig" xml:space="preserve">
<value>MSB4226: The imported project "{0}" was not found. Also, tried to find "{1}" in the fallback search path(s) for {2} - {3} . These search paths are defined in "{4}". Confirm that the path in the <Import> declaration is correct, and that the file exists on disk in one of the search paths.</value>
<comment>{StrBegin="MSB4226: "}LOCALIZATION: <Import> should not be localized.</comment>
</data>
<data name="ImportedProjectFromExtensionsPathNotFound" xml:space="preserve">
<value>MSB4226: The imported project "{0}" was not found. Also, tried to find "{1}" in the fallback search path(s) for {2} - {3} . Confirm that the path in the <Import> declaration is correct, and that the file exists on disk in one of the search paths.</value>
<comment>{StrBegin="MSB4226: "}LOCALIZATION: <Import> should not be localized.</comment>
</data>
<data name="IncorrectNumberOfFunctionArguments" xml:space="preserve">
<value>MSB4089: Incorrect number of arguments to function in condition "{0}". Found {1} argument(s) when expecting {2}.</value>
<comment>{StrBegin="MSB4089: "}</comment>
</data>
<data name="InvalidAttributeValue" xml:space="preserve">
<value>MSB4020: The value "{0}" of the "{1}" attribute in element <{2}> is invalid.</value>
<comment>{StrBegin="MSB4020: "}UE: This is a generic message that is displayed when we find a project element with an incorrect value for one of its
attributes e.g. <Import Project=""> -- the value of Project should not be an empty string.</comment>
</data>
<data name="InvalidAttributeExclusive" xml:space="preserve">
<value>MSB4111: At most one of the include, remove, and update attributes may be specified for an item element.</value>
</data>
<data name="InvalidAttributeValueWithException" xml:space="preserve">
<value>MSB4102: The value "{0}" of the "{1}" attribute in element <{2}> is invalid. {3}</value>
<comment>{StrBegin="MSB4102: "}UE: This is a generic message that is displayed when we find a project element with an incorrect value for one of its
attributes. At the end of the message we show the exception text we got trying to use the value.</comment>
</data>
<data name="InvalidBinaryLoggerParameters" xml:space="preserve">
<value>MSB4234: Invalid binary logger parameter(s): "{0}". Expected: ProjectImports={{None,Embed,ZipFile}} and/or [LogFile=]filePath.binlog (the log file name or path, must have the ".binlog" extension).</value>
</data>
<data name="InvalidContinueOnErrorAttribute" xml:space="preserve">
<value>MSB4021: The "ContinueOnError" attribute of the "{0}" task is not valid. {1}</value>
<comment>{StrBegin="MSB4021: "}LOCALIZATION: "ContinueOnError" should not be localized. "{1}" is a message from another exception explaining the problem.</comment>
</data>
<data name="InvalidEvaluatedAttributeValue" xml:space="preserve">
<value>MSB4022: The result "{0}" of evaluating the value "{1}" of the "{2}" attribute in element <{3}> is not valid.</value>
<comment>{StrBegin="MSB4022: "}UE: This message is shown when the engine is checking the correctness of the value (after evaluating embedded
properties/items) assigned to an XML attribute of an XML element in the project file.</comment>
</data>
<data name="InvalidFileLoggerFile" xml:space="preserve">
<value>MSB4104: Failed to write to log file "{0}". {1}</value>
<comment>{StrBegin="MSB4104: "}UE: This is shown when the File Logger can't create or write to the file it was instructed to log to.</comment>
</data>
<data name="InvalidImportedProjectFile" xml:space="preserve">
<value>MSB4024: The imported project file "{0}" could not be loaded. {1}</value>
<comment>{StrBegin="MSB4024: "}UE: This message is shown when an imported project file cannot be loaded because of incorrect XML. The project
filename is not part of the message because it is provided separately to loggers.
LOCALIZATION: {0} is a localized message from the CLR/FX explaining why the project is invalid.</comment>
</data>
<data name="InvalidPropertyNameInToolset" xml:space="preserve">
<value>MSB4147: The property "{0}" at "{1}" is invalid. {2}</value>
<comment>{StrBegin="MSB4147: "}</comment>
</data>
<data name="InvalidProperty" xml:space="preserve">
<value>MSB4177: Invalid property. {0}</value>
<comment>{StrBegin="MSB4177: "}
UE: {0} is a localized message indicating what the problem was.</comment>
</data>
<data name="InvalidRegistryPropertyExpression" xml:space="preserve">
<value>MSB4143: The registry expression "{0}" cannot be evaluated. {1}</value>
<comment>{StrBegin="MSB4143: "}
UE: This message is shown when the user attempts to provide an expression like "$(Registry:HKEY_LOCAL_MACHINE\Software\Vendor\Tools@TaskLocation)"
LOCALIZATION: "{0}" is the expression that was bad. "{1}" is a message from an FX exception that describes why the expression is bad.
</comment>
</data>
<data name="InvalidFunctionPropertyExpression" xml:space="preserve">
<value>MSB4184: The expression "{0}" cannot be evaluated. {1}</value>
<comment>{StrBegin="MSB4184: "}
Double quotes as the expression will typically have single quotes in it.
UE: This message is shown when the user attempts to provide an expression like "$(SomeProperty.ToLower())" or "@(Foo->Bar())"
LOCALIZATION: "{0}" is the expression that was bad. "{1}" is a message from an FX exception that describes why the expression is bad.
</comment>
</data>
<data name="InvalidFunctionPropertyExpressionDetailMismatchedQuote" xml:space="preserve">
<value>The quotes were mismatched.</value>
<comment>This is a potential suffix to "InvalidFunctionPropertyExpression" so it has no error code.</comment>
</data>
<data name="InvalidFunctionPropertyExpressionDetailMismatchedParenthesis" xml:space="preserve">
<value>The parentheses were mismatched.</value>
<comment>This is a potential suffix to "InvalidFunctionPropertyExpression" so it has no error code.</comment>
</data>
<data name="InvalidFunctionPropertyExpressionDetailMismatchedSquareBrackets" xml:space="preserve">
<value>The square brackets were mismatched.</value>
<comment>This is a potential suffix to "InvalidFunctionPropertyExpression" so it has no error code.</comment>
</data>
<data name="InvalidFunctionMethodUnavailable" xml:space="preserve">
<value>MSB4185: The function "{0}" on type "{1}" is not available for execution as an MSBuild property function.</value>
<comment>
{StrBegin="MSB4185: "}
UE: This message is shown when the user attempts to provide an expression like "$([System.DateTime]::Now)", but the expression has not been enabled
LOCALIZATION: "{0}" is the static function name, "{1}" is the .NET Framework type name
</comment>
</data>
<data name="InvalidFunctionTypeUnavailable" xml:space="preserve">
<value>MSB4212: Invalid static method invocation syntax: "{0}". The type "{1}" is either not available for execution in an MSBuild property function or could not be found.</value>
<comment>
{StrBegin="MSB4212: "}
UE: This message is shown when the user attempts to provide an expression like "$([System.DateTime]::Now)", but the expression has not been enabled
LOCALIZATION: "{0}" is the function expression which is in error. "{1}" is the .NET Framework type name
</comment>
</data>
<data name="InvalidFunctionStaticMethodSyntax" xml:space="preserve">
<value>MSB4186: Invalid static method invocation syntax: "{0}". {1} Static method invocation should be of the form: $([FullTypeName]::Method()), e.g. $([System.IO.Path]::Combine(`a`, `b`)). Check that all parameters are defined, are of the correct type, and are specified in the right order.</value>
<comment>{StrBegin="MSB4186: "}
UE: This message is shown when the user attempts to call a static method on a type, but has used the incorrect syntax
LOCALIZATION: "{0}" is the function expression which is in error. "{1}" is a message from an FX exception that describes why the expression is bad.
</comment>
</data>
<data name="InvalidItemFunctionExpression" xml:space="preserve">
<value>MSB4198: The expression "{0}" cannot be evaluated on item "{1}". {2}</value>
<comment>
{StrBegin="MSB4198: "}
Double quotes as the expression will typically have single quotes in it.
UE: This message is shown when the user attempts to provide an expression like "@(SomeItem->DirectoryName())"
LOCALIZATION: "{0}" is the expression that was bad, "{1}" is the item or file that was being worked on. "{2}" is a message from an FX exception that describes why the expression is bad.
</comment>
</data>
<data name="InvalidItemFunctionSyntax" xml:space="preserve">
<value>MSB4199: Invalid transformation syntax "{0}". An item function was not found with that name and {1} parameters.</value>
<comment>
{StrBegin="MSB4199: "}
UE: This message is shown when the user attempts to call a transformation on an item, but has used the incorrect syntax
LOCALIZATION: "{0}" is the function which is in error
</comment>
</data>
<data name="UnknownItemFunction" xml:space="preserve">
<value>MSB4200: Unknown item transformation function "{0}".</value>
<comment>
{StrBegin="MSB4200: "}
UE: This message is shown when the user attempts to provide an expression like @(Item->SomeTransform()), but SomeTransform is unknown
LOCALIZATION: "{0}" is the function name
</comment>
</data>
<data name="InvalidTaskAttributeError" xml:space="preserve">
<value>MSB4026: The "{0}={1}" parameter for the "{2}" task is invalid.</value>
<comment>{StrBegin="MSB4026: "}UE: This message is displayed when a task has an invalid parameter that cannot be initialized.</comment>
</data>
<data name="InvalidTaskItemsInTaskOutputs" xml:space="preserve">
<value>MSB4027: The "{0}" task generated invalid items from the "{1}" output parameter. {2}</value>
<comment>{StrBegin="MSB4027: "}</comment>
</data>
<data name="InvalidTaskOutputSpecification" xml:space="preserve">
<value>MSB4029: The "{0}" task has an invalid output specification. The "TaskParameter" attribute is required, and either the "ItemName" or "PropertyName" attribute must be specified (but not both).</value>
<comment>{StrBegin="MSB4029: "}LOCALIZATION: "TaskParameter", "ItemName" and "PropertyName" should not be localized.</comment>
</data>
<data name="InvalidTaskParameterValueError" xml:space="preserve">
<value>MSB4030: "{0}" is an invalid value for the "{1}" parameter of the "{3}" task. The "{1}" parameter is of type "{2}".</value>
<comment>{StrBegin="MSB4030: "}UE: This error is shown when a type mis-match occurs between the value assigned to task parameter in the project file
and the type of the .NET property that corresponds to the task parameter. For example, if an int task parameter called "Count"
is assigned the value "x", this error would be displayed: <MyTask Count="x" /></comment>
</data>
<data name="InvalidToolsetValueInConfigFileValue" xml:space="preserve">
<value>MSB4137: Invalid value specified in the configuration file at "{0}". Property name or tools version name is an empty string.</value>
<comment>{StrBegin="MSB4137: "}</comment>
</data>
<data name="ItemDefinitionGroupNotLegalInsideTarget" xml:space="preserve">
<value>MSB4163: <ItemDefinitionGroup> is not allowed inside a target.</value>
<comment>{StrBegin="MSB4163: "}</comment>
</data>
<data name="ItemDoesNotContainValueForUnqualifiedMetadata" xml:space="preserve">
<value>MSB4096: The item "{0}" in item list "{1}" does not define a value for metadata "{2}". In order to use this metadata, either qualify it by specifying %({1}.{2}), or ensure that all items in this list define a value for this metadata.</value>
<comment>{StrBegin="MSB4096: "}</comment>
</data>
<data name="ItemListNotAllowedInThisConditional" xml:space="preserve">
<value>MSB4099: A reference to an item list at position {1} is not allowed in this condition "{0}".</value>
<comment>{StrBegin="MSB4099: "}</comment>
</data>
<data name="CustomMetadataNotAllowedInThisConditional" xml:space="preserve">
<value>MSB4191: The reference to custom metadata "{2}" at position {1} is not allowed in this condition "{0}".</value>
<comment>{StrBegin="MSB4191: "}</comment>
</data>
<data name="BuiltInMetadataNotAllowedInThisConditional" xml:space="preserve">
<value>MSB4190: The reference to the built-in metadata "{2}" at position {1} is not allowed in this condition "{0}".</value>
<comment>{StrBegin="MSB4190: "}</comment>
</data>
<data name="ItemSpecModifierCannotBeCustomMetadata" xml:space="preserve">
<value>MSB4033: "{0}" is a reserved item metadata, and cannot be redefined as a custom metadata on the item.</value>
<comment>{StrBegin="MSB4033: "}</comment>
</data>
<data name="InternalLoggerExceptionOnlyThrownByEngine" xml:space="preserve">
<value>An InternalLoggerException can only be thrown by the MSBuild engine. The public constructors of this class cannot be used to create an instance of the exception.</value>
<comment>UE: This message is shown when a user tries to instantiate a special exception called InternalLoggerException through the OM --
only the engine is allowed to create and throw this exception.
LOCALIZATION: "InternalLoggerException" and "MSBuild" should not be localized.</comment>
</data>
<data name="ItemListHeader" xml:space="preserve">
<value>Initial Items:</value>
</data>
<data name="EnvironmentHeader" xml:space="preserve">
<value>Environment at start of build:</value>
</data>
<data name="MetadataDefinitionCannotContainItemVectorExpression" xml:space="preserve">
<value>MSB4164: The value "{0}" of metadata "{1}" contains an item list expression. Item list expressions are not allowed on default metadata values.</value>
<comment>{StrBegin="MSB4164: "}</comment>
</data>
<data name="MissingRequiredAttribute" xml:space="preserve">
<value>MSB4035: The required attribute "{0}" is empty or missing from the element <{1}>.</value>
<comment>{StrBegin="MSB4035: "}UE: This message is shown when a user leaves off a required attribute from a project element
e.g. <UsingTask AssemblyName="foo"> -- this is missing the "TaskName" attribute.</comment>
</data>
<data name="IncludeRemoveOrUpdate" xml:space="preserve">
<value>MSB4232: Items that are outside Target elements must have one of the following operations: Include, Update, or Remove.</value>
<comment>{StrBegin="MSB4232: "} Target, Include, Update, and Remove should not be localized and their casing should not be changed</comment>
</data>
<data name="MissingTaskError" xml:space="preserve">
<value>MSB4036: The "{0}" task was not found. Check the following: 1.) The name of the task in the project file is the same as the name of the task class. 2.) The task class is "public" and implements the Microsoft.Build.Framework.ITask interface. 3.) The task is correctly declared with <UsingTask> in the project file, or in the *.tasks files located in the "{1}" directory.</value>
<comment>{StrBegin="MSB4036: "}LOCALIZATION: <UsingTask> and "*.tasks" should not be localized.</comment>
</data>
<data name="MSBuildToolsPathIsNotSpecified" xml:space="preserve">
<value>MSB4141: MSBuildToolsPath is not specified for the ToolsVersion "{0}" defined at "{1}", or the value specified evaluates to the empty string.</value>
<comment>{StrBegin="MSB4141: "}</comment>
</data>
<data name="MSBuildToolsPathNotSupportedInSubToolsets" xml:space="preserve">
<value>MSB4222: ToolsVersion "{0}", defined at "{1}", contains sub-toolset "{2}" which sets MSBuildBinPath or MSBuildToolsPath. This is not supported in sub-toolsets.</value>
</data>
<data name="MultipleDefinitionsForSameToolset" xml:space="preserve">
<value>MSB4144: Multiple definitions were found for the toolset "{0}". </value>
<comment>{StrBegin="MSB4144: "}</comment>
</data>
<data name="MultipleDefinitionsForSameExtensionsPathOS" xml:space="preserve">
<value>MSB4225: Toolset contains multiple definitions of searchPaths for the OS "{0}" at "{1}".</value>
<comment>{StrBegin="MSB4225: "}</comment>
</data>
<data name="MultipleDefinitionsForSameProperty" xml:space="preserve">
<value>MSB4145: Multiple definitions were found for the property "{0}".</value>
<comment>{StrBegin="MSB4145: "}</comment>
</data>
<data name="MultipleOtherwise" xml:space="preserve">
<value>MSB4082: Choose has more than one <Otherwise> element.</value>
<comment>{StrBegin="MSB4082: "}</comment>
</data>
<data name="NodeMustBeLastUnderElement" xml:space="preserve">
<value>MSB4038: The element <{0}> must be last under element <{1}>. Found element <{2}> instead.</value>
<comment>{StrBegin="MSB4038: "}</comment>
</data>
<data name="NonStringDataInRegistry" xml:space="preserve">
<value>MSB4138: Non-string data was specified at the registry location "{0}".</value>
<comment>{StrBegin="MSB4138: "}</comment>
</data>
<data name="NoRootProjectElement" xml:space="preserve">
<value>MSB4039: No "{0}" element was found in the project file.</value>
<comment>{StrBegin="MSB4039: "}</comment>
</data>
<data name="NoTargetSpecified" xml:space="preserve">
<value>MSB4040: There is no target in the project.</value>
<comment>{StrBegin="MSB4040: "}</comment>
</data>
<data name="NullLoggerNotAllowed" xml:space="preserve">
<value>A null entry was found in the collection of loggers.</value>
</data>
<data name="InvalidMaxNodeCount" xml:space="preserve">
<value>MaxNodeCount may only be assigned a value greater than zero.</value>
</data>
<data name="OverridingTarget" xml:space="preserve">
<value>Overriding target "{0}" in project "{1}" with target "{2}" from project "{3}".</value>
</data>
<data name="PerformanceLine" xml:space="preserve">
<value>{0} ms {1} {2} calls</value>
</data>
<data name="PerformanceReentrancyNote" xml:space="preserve">
<value>(* = timing was not recorded because of reentrancy)</value>
</data>
<data name="ProjectFileNotFound" xml:space="preserve">
<value>The project file "{0}" was not found.</value>
<comment>UE: This message is shown when the user calls into the OM to build a project that doesn't exist on disk.</comment>
</data>
<data name="ProjectFinishedFailure" xml:space="preserve">
<value>Done building project "{0}" -- FAILED.</value>
</data>
<data name="ProjectFinishedSuccess" xml:space="preserve">
<value>Done building project "{0}".</value>
</data>
<data name="ProjectFinishedPrefixWithTargetNamesMultiProc" xml:space="preserve">
<value>Done Building Project "{0}" ({1} target(s)).</value>
</data>
<data name="ProjectFinishedPrefixWithDefaultTargetsMultiProc" xml:space="preserve">
<value>Done Building Project "{0}" (default targets).</value>
</data>
<data name="ProjectFinishedPrefixWithTargetNamesMultiProcFailed" xml:space="preserve">
<value>Done Building Project "{0}" ({1} target(s)) -- FAILED.</value>
</data>
<data name="ProjectFinishedPrefixWithDefaultTargetsMultiProcFailed" xml:space="preserve">
<value>Done Building Project "{0}" (default targets) -- FAILED.</value>
</data>
<data name="ProjectMustBeInMSBuildXmlNamespace" xml:space="preserve">
<value>MSB4041: The default XML namespace of the project must be the MSBuild XML namespace or no namespace. If the project is authored in the MSBuild 2003 format, please add xmlns="{0}" to the <Project> element. If the project has been authored in the old 1.0 or 1.2 format, please convert it to MSBuild 2003 format.</value>
<comment>{StrBegin="MSB4041: "}UE: This is a Beta 1 message only.
LOCALIZATION: <Project>, "MSBuild" and "xmlns" should not be localized.</comment>
</data>
<data name="ProjectPerformanceSummary" xml:space="preserve">
<value>Project Performance Summary:</value>
</data>
<data name="ProjectStartedPrefixForNestedProjectWithTargetNames" xml:space="preserve">
<value>Project "{0}" is building "{1}" ({2} target(s)):</value>
</data>
<data name="ProjectStartedPrefixForNestedProjectWithDefaultTargets" xml:space="preserve">
<value>Project "{0}" is building "{1}" (default targets):</value>
</data>
<data name="ProjectStartedPrefixForTopLevelProjectWithTargetNames" xml:space="preserve">
<value>Project "{0}" ({1} target(s)):</value>
</data>
<data name="ProjectStartedPrefixForTopLevelProjectWithDefaultTargets" xml:space="preserve">
<value>Project "{0}" (default targets):</value>
</data>
<data name="ProjectTaskNameEmpty" xml:space="preserve">
<value>Task name cannot be empty.</value>
</data>
<data name="ProjectUpgradeNeeded" xml:space="preserve">
<value>MSB4075: The project file "{0}" must be opened in the Visual Studio IDE and converted to the latest version before it can be built by MSBuild.</value>
<comment>{StrBegin="MSB4075: "}</comment>
</data>
<data name="ProjectUpgradeNeededToVcxProj" xml:space="preserve">
<value>MSB4192: The project file "{0}" is in the ".vcproj" file format, which MSBuild no longer supports. Please convert the project by opening it in the Visual Studio IDE or running the conversion tool, or use MSBuild 3.5 or earlier to build it.</value>
<comment>{StrBegin="MSB4192: "} LOC: ".vcproj" should not be localized</comment>
</data>
<data name="PropertyListHeader" xml:space="preserve">
<value>Initial Properties:</value>
</data>
<data name="PropertyNameInRegistryHasZeroLength" xml:space="preserve">
<value>MSB4148: The name of a property stored under the registry key "{0}" has zero length.</value>
<comment>{StrBegin="MSB4148: "}</comment>
</data>
<data name="PropertyReassignment" xml:space="preserve">
<value>Property reassignment: $({0})="{1}" (previous value: "{2}") at {3}</value>
</data>
<data name="QualifiedMetadataInTransformNotAllowed" xml:space="preserve">
<value>MSB4043: The item metadata reference "{0}" is invalid because it is qualified with an item name. Item metadata referenced in transforms do not need to be qualified, because the item name is automatically deduced from the items being transformed. Change "{0}" to "%({1})".</value>
<comment>{StrBegin="MSB4043: "}UE: This message is shown when the user does something like this: @(foo->'%(foo.metadata)'). There is no need to specify
"foo.metadata", because "foo" is automatically deduced. In corollary, "bar.metadata" is not allowed either, where "bar" is a different
item list type.</comment>
</data>
<data name="RegistryReadError" xml:space="preserve">
<value>MSB4135: Error reading the toolset information from the registry location "{0}". {1}</value>
<comment>{StrBegin="MSB4135: "}</comment>
</data>
<data name="RequiredPropertyNotSetError" xml:space="preserve">
<value>MSB4044: The "{0}" task was not given a value for the required parameter "{1}".</value>
<comment>{StrBegin="MSB4044: "}UE: This message is shown when a task parameter designated as "required" is not set in the project file.</comment>
</data>
<data name="SecurityProjectBuildDisabled" xml:space="preserve">
<value>MSB4112: The targets in this project have been disabled by the host and therefore cannot be built at this time. This may have been done for security reasons. To enable the targets, the host must set Project.BuildEnabled to "true".</value>
<comment>{StrBegin="MSB4112: "}</comment>
</data>
<data name="SetAccessorNotAvailableOnTaskParameter" xml:space="preserve">
<value>MSB4093: The "{0}" parameter of the "{1}" task cannot be written to because it does not have a "set" accessor.</value>
<comment>{StrBegin="MSB4093: "}UE: This error is shown when a project tries to assign a value to a task parameter that does not have a "set"
accessor on the corresponding .NET property on the task class.</comment>
</data>
<data name="SkipTargetBecauseNoInputs" xml:space="preserve">
<value>Skipping target "{0}" because it has no inputs.</value>
</data>
<data name="SkipTargetBecauseNoInputsDetail" xml:space="preserve">
<value>Though the target has declared its inputs, the input specification only references empty properties and/or empty item lists.</value>
</data>
<data name="SkipTargetBecauseNoOutputs" xml:space="preserve">
<value>Skipping target "{0}" because it has no outputs.</value>
</data>
<data name="SkipTargetBecauseNoOutputsDetail" xml:space="preserve">
<value>Though the target has declared its outputs, the output specification only references empty properties and/or empty item lists.</value>
</data>
<data name="SkipTargetBecauseOutputsUpToDate" xml:space="preserve">
<value>Skipping target "{0}" because all output files are up-to-date with respect to the input files.</value>
</data>
<data name="SkipTargetUpToDateInputs" xml:space="preserve">
<value>Input files: {0}</value>
<comment>{0} is a semicolon-separated list of filenames.</comment>
</data>
<data name="SkipTargetUpToDateOutputs" xml:space="preserve">
<value>Output files: {0}</value>
<comment>{0} is a semicolon-separated list of filenames.</comment>
</data>
<data name="AspNetCompiler.TargetingHigherFrameworksDefaultsTo40" xml:space="preserve">
<value>{0}: Defaulting .NET Framework v{1} to the .NET Framework v4.0 version of aspnet_compiler.exe. To change the version of the tool used, please set the "ToolPath" parameter with the correct path to the tool.</value>
</data>
<data name="AspNetCompiler.InvalidTargetFrameworkMonikerNotDotNET" xml:space="preserve">
<value>MSB4203: {0}: Invalid TargetFrameworkMoniker {1}. The AspNetCompiler task only supports targeting the .NET Framework.</value>
<comment>{StrBegin="MSB4203: "}</comment>
</data>
<data name="AspNetCompiler.20NotInstalled" xml:space="preserve">
<value>MSB4205: The website project in this solution is targeting the v2.0 runtime, but it is not installed.</value>
<comment>{StrBegin="MSB4205: "}</comment>
</data>
<data name="AspNetCompiler.UnsupportedMSBuildVersion" xml:space="preserve">
<value>MSB4249: Unable to build website project "{0}". The ASP.NET compiler is only available on the .NET Framework version of MSBuild.</value>
<comment>{StrBegin="MSB4249: "}</comment>
</data>
<data name="AspNetCompiler.InvalidTargetFrameworkMonikerFromException" xml:space="preserve">
<value>MSB4204: {0}: Invalid TargetFrameworkMoniker {1}. {2}.</value>
<comment>{StrBegin="MSB4204: "}</comment>
</data>
<data name="OldWrapperGeneratedExplicitToolsVersion" xml:space="preserve">
<value>Using the MSBuild v3.5 solution wrapper generator because the tools version was set to {0}.</value>
</data>
<data name="OldWrapperGeneratedOldSolutionVersion" xml:space="preserve">
<value>Using the MSBuild v3.5 solution wrapper generator with a tools version of {0} because the solution file format was version {1} and no tools version was supplied.</value>
</data>
<data name="SolutionBuildingSolutionConfiguration" xml:space="preserve">
<value>Building solution configuration "{0}".</value>
<comment>UE: This is not an error, so doesn't need an error code.</comment>
</data>
<data name="SolutionCircularDependencyError" xml:space="preserve">
<value>MSB4160: A circular dependency involving project "{0}" has been detected.</value>
<comment>{StrBegin="MSB4160: "}</comment>
</data>
<data name="SolutionInvalidSolutionConfiguration" xml:space="preserve">
<value>MSB4126: The specified solution configuration "{0}" is invalid. Please specify a valid solution configuration using the Configuration and Platform properties (e.g. MSBuild.exe Solution.sln /p:Configuration=Debug /p:Platform="Any CPU") or leave those properties blank to use the default solution configuration.</value>
<comment>{StrBegin="MSB4126: "}UE: The solution filename is provided separately to loggers.</comment>
</data>
<data name="SolutionParseErrorReadingProject" xml:space="preserve">
<value>MSB4046: Error reading project file "{0}": {1}</value>
<comment>{StrBegin="MSB4046: "}</comment>
</data>
<data name="SolutionParseInvalidProjectFileName" xml:space="preserve">
<value>MSB4125: The project file name "{0}" is invalid. {1}</value>
<comment>{StrBegin="MSB4125: "}UE: The solution filename is provided separately to loggers.</comment>
</data>
<data name="SolutionParseProjectDepNotFoundError" xml:space="preserve">
<value>MSB4051: Project {0} is referencing a project with GUID {1}, but a project with this GUID was not found in the .SLN file.</value>
<comment>{StrBegin="MSB4051: "}UE: The solution filename is provided separately to loggers.</comment>
</data>
<data name="SolutionParseUnknownProjectType" xml:space="preserve">
<value>MSB4078: The project file "{0}" is not supported by MSBuild and cannot be built.</value>
<comment>{StrBegin="MSB4078: "}</comment>
</data>
<data name="SolutionParseUpgradeNeeded" xml:space="preserve">
<value>MSB4054: The solution file must be opened in the Visual Studio IDE and converted to the latest version before it can be built by MSBuild.</value>
<comment>{StrBegin="MSB4054: "}UE: The solution filename is provided separately to loggers.</comment>
</data>
<data name="SolutionProjectConfigurationMissing" xml:space="preserve">
<value>MSB4121: The project configuration for project "{0}" was not specified in the solution file for the solution configuration "{1}".</value>
<comment>{StrBegin="MSB4121: "}</comment>
</data>
<data name="SolutionProjectSkippedForBuilding" xml:space="preserve">
<value>The project "{0}" is not selected for building in solution configuration "{1}".</value>
<comment>
UE: This is not an error, so doesn't need an error code.
</comment>
</data>
<data name="SolutionScanProjectDependenciesFailed" xml:space="preserve">
<value>MSB4122: Scanning project dependencies for project "{0}" failed. {1}</value>
<comment>{StrBegin="MSB4122: "}</comment>
</data>
<data name="SolutionToolsVersionDoesNotSupportProjectToolsVersion" xml:space="preserve">
<value>MSB4149: The tools version "{0}" of the solution does not support building projects with a different tools version.</value>
<comment>{StrBegin="MSB4149: "}</comment>
</data>
<data name="SolutionVenusProjectNoClean" xml:space="preserve">
<value>Web projects do not support the "Clean" target. Continuing with remaining projects ...</value>
<comment>UE: This is not an error, so doesn't need an error code.
LOCALIZATION: Do not localize "Clean".</comment>
</data>
<data name="SolutionVenusProjectNoPublish" xml:space="preserve">
<value>Web projects do not support the "Publish" target. Continuing with remaining projects ...</value>
<comment>UE: This is not an error, so doesn't need an error code.
LOCALIZATION: Do not localize "Publish".</comment>
</data>
<data name="SolutionVenusProjectSkipped" xml:space="preserve">
<value>Skipping because the "$(AspNetConfiguration)" configuration is not supported for this web project. You can use the AspNetConfiguration property to override the configuration used for building web projects, by adding /p:AspNetConfiguration=<value> to the command line. Currently web projects only support Debug and Release configurations.</value>
<comment>
UE: This is not an error, so doesn't need an error code.
LOCALIZATION: Do NOT localize "AspNetConfiguration", "Debug", "Release".
</comment>
</data>
<data name="TargetAlreadyCompleteFailure" xml:space="preserve">
<value>Target "{0}" skipped. Previously built unsuccessfully.</value>
</data>
<data name="TargetAlreadyCompleteSuccess" xml:space="preserve">
<value>Target "{0}" skipped. Previously built successfully.</value>
</data>
<data name="TargetConditionHasInvalidMetadataReference" xml:space="preserve">
<value>MSB4116: The condition "{1}" on the "{0}" target has a reference to item metadata. References to item metadata are not allowed in target conditions unless they are part of an item transform.</value>
<comment>{StrBegin="MSB4116: "}</comment>
</data>
<data name="TargetDoesNotExist" xml:space="preserve">
<value>MSB4057: The target "{0}" does not exist in the project.</value>
<comment>{StrBegin="MSB4057: "}</comment>
</data>
<data name="TargetDoesNotExistBeforeTargetMessage" xml:space="preserve">
<value>The target "{0}" listed in a BeforeTargets attribute at "{1}" does not exist in the project, and will be ignored.</value>
</data>
<data name="TargetDoesNotExistAfterTargetMessage" xml:space="preserve">
<value>The target "{0}" listed in an AfterTargets attribute at "{1}" does not exist in the project, and will be ignored.</value>
</data>
<data name="TargetFinishedFailure" xml:space="preserve">
<value>Done building target "{0}" in project "{1}" -- FAILED.</value>
</data>
<data name="TargetFinishedSuccess" xml:space="preserve">
<value>Done building target "{0}" in project "{1}".</value>
</data>
<data name="TargetMessageWithId" xml:space="preserve">
<value>{0}: (TargetId:{1})</value>
</data>
<data name="TargetOutputItemsHeader" xml:space="preserve">
<value>Target output items:</value>
</data>
<data name="TargetOutputItem" xml:space="preserve">
<value> {0}</value>