/
Strings.en.xlf
2376 lines (2376 loc) · 170 KB
/
Strings.en.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="en" original="../Strings.resx">
<body>
<trans-unit id="AmbiguousTaskParameterError">
<source>MSB4001: The "{0}" task has more than one parameter called "{1}".</source>
<target state="new">MSB4001: The "{0}" task has more than one parameter called "{1}".</target>
<note>{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.</note>
</trans-unit>
<trans-unit id="AspNetCompiler.UnsupportedMSBuildVersion">
<source>MSB4249: Unable to build website project "{0}". The ASP.NET compiler is only available on the .NET Framework version of MSBuild.</source>
<target state="new">MSB4249: Unable to build website project "{0}". The ASP.NET compiler is only available on the .NET Framework version of MSBuild.</target>
<note>{StrBegin="MSB4249: "}</note>
</trans-unit>
<trans-unit id="AttributeTypeLoadError">
<source>MSB4002: There was a failure retrieving the attributes for parameters in the "{0}" task. {1}</source>
<target state="new">MSB4002: There was a failure retrieving the attributes for parameters in the "{0}" task. {1}</target>
<note>{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.</note>
</trans-unit>
<trans-unit id="BadlyCasedSpecialTaskAttribute">
<source>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.</source>
<target state="new">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.</target>
<note>{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".</note>
</trans-unit>
<trans-unit id="BuildInProgress">
<source>The operation cannot be completed because a build is already in progress.</source>
<target state="new">The operation cannot be completed because a build is already in progress.</target>
<note />
</trans-unit>
<trans-unit id="CacheMissesNotAllowedInIsolatedGraphBuilds">
<source>MSB4252: Project "{0}" with global properties
({1})
is building project "{2}" with global properties
({3})
with the ({4}) target(s) but the build result for the built project is not in the engine cache. In isolated builds this could mean one of the following:
- the reference was called with a target which is not specified in the ProjectReferenceTargets item in project "{0}"
- the reference was called with global properties that do not match the static graph inferred nodes
- the reference was not explicitly specified as a ProjectReference item in project "{0}"
</source>
<target state="new">MSB4252: Project "{0}" with global properties
({1})
is building project "{2}" with global properties
({3})
with the ({4}) target(s) but the build result for the built project is not in the engine cache. In isolated builds this could mean one of the following:
- the reference was called with a target which is not specified in the ProjectReferenceTargets item in project "{0}"
- the reference was called with global properties that do not match the static graph inferred nodes
- the reference was not explicitly specified as a ProjectReference item in project "{0}"
</target>
<note>
{StrBegin="MSB4252:"}
LOCALIZATION: Do not localize the following words: ProjectReference, ProjectReferenceTargets
</note>
</trans-unit>
<trans-unit id="CannotExpandItemMetadata">
<source>MSB4248: Cannot expand metadata in expression "{0}". {1}</source>
<target state="new">MSB4248: Cannot expand metadata in expression "{0}". {1}</target>
<note>{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.</note>
</trans-unit>
<trans-unit id="ChangeWave_InvalidFormat">
<source>Environment variable MSBUILDDISABLEFEATURESFROMVERSION is set to an invalid format. Enabling all change wave versions. Entered value: {0}.</source>
<target state="new">Environment variable MSBUILDDISABLEFEATURESFROMVERSION is set to an invalid format. Enabling all change wave versions. Entered value: {0}.</target>
<note>
Value should be of the format: xx.yy
</note>
</trans-unit>
<trans-unit id="ChangeWave_OutOfRotation">
<source>Environment variable MSBUILDDISABLEFEATURESFROMVERSION is set to a version that is out of rotation. Defaulting to Change Wave version: {0}. Entered value: {1}.</source>
<target state="new">Environment variable MSBUILDDISABLEFEATURESFROMVERSION is set to a version that is out of rotation. Defaulting to Change Wave version: {0}. Entered value: {1}.</target>
<note>
Refer to https://github.com/dotnet/msbuild/tree/master/documentation/wiki/ChangeWaves.md to see what the current Change Waves are.
</note>
</trans-unit>
<trans-unit id="CircularDependencyInProjectGraph">
<source>MSB4251: There is a circular dependency involving the following projects: {0}</source>
<target state="new">MSB4251: There is a circular dependency involving the following projects: {0}</target>
<note>
{StrBegin="MSB4251:"} This message is shown when a graph build detects a target referenced in a circular manner -- a project cannot
request a target to build itself (perhaps via a chain of other targets)
</note>
</trans-unit>
<trans-unit id="EmptyOutputCacheFile">
<source>MSB4257: The specified output result cache file is empty.</source>
<target state="new">MSB4257: The specified output result cache file is empty.</target>
<note />
</trans-unit>
<trans-unit id="EnvironmentVariableRead">
<source>Read environment variable "{0}"</source>
<target state="new">Read environment variable "{0}"</target>
<note />
</trans-unit>
<trans-unit id="ErrorReadingCacheFile">
<source>MSB4256: Reading input result cache files from path "{0}" encountered an error: {1}</source>
<target state="new">MSB4256: Reading input result cache files from path "{0}" encountered an error: {1}</target>
<note />
</trans-unit>
<trans-unit id="ErrorWritingCacheFile">
<source>MSB4258: Writing output result cache file in path "{0}" encountered an error: {1}</source>
<target state="new">MSB4258: Writing output result cache file in path "{0}" encountered an error: {1}</target>
<note />
</trans-unit>
<trans-unit id="IllFormedPropertySpaceInCondition">
<source>MSB4259: Unexpected space at position "{1}" of condition "{0}". Did you forget to remove a space?</source>
<target state="new">MSB4259: Unexpected space at position "{1}" of condition "{0}". Did you forget to remove a space?</target>
<note>{StrBegin="MSB4259: "}</note>
</trans-unit>
<trans-unit id="InputCacheFilesDoNotExist">
<source>MSB4255: The following input result cache files do not exist: "{0}"</source>
<target state="new">MSB4255: The following input result cache files do not exist: "{0}"</target>
<note />
</trans-unit>
<trans-unit id="InvalidVersionFormat">
<source>Version string was not in a correct format.</source>
<target state="new">Version string was not in a correct format.</target>
<note />
</trans-unit>
<trans-unit id="IsolatedContextDoesNotSupportFileSystem">
<source>"EvaluationContext objects created with SharingPolicy.Isolated do not support being passed an MSBuildFileSystemBase file system."</source>
<target state="new">"EvaluationContext objects created with SharingPolicy.Isolated do not support being passed an MSBuildFileSystemBase file system."</target>
<note />
</trans-unit>
<trans-unit id="LogLoggerVerbosity">
<source>Logging verbosity is set to: {0}.</source>
<target state="new">Logging verbosity is set to: {0}.</target>
<note>
LOCALIZATION: {0} is an enum value of LoggerVerbosity.
</note>
</trans-unit>
<trans-unit id="LogTaskInputs.Truncated">
<source>The parameters have been truncated beyond this point. To view all parameters, clear the MSBUILDTRUNCATETASKINPUTLOGGING environment variable.</source>
<target state="new">The parameters have been truncated beyond this point. To view all parameters, clear the MSBUILDTRUNCATETASKINPUTLOGGING environment variable.</target>
<note />
</trans-unit>
<trans-unit id="MetaprojectGenerated">
<source>Metaproject "{0}" generated.</source>
<target state="new">Metaproject "{0}" generated.</target>
<note />
</trans-unit>
<trans-unit id="NoBuildInProgress">
<source>The operation cannot be completed because BeginBuild has not yet been called.</source>
<target state="new">The operation cannot be completed because BeginBuild has not yet been called.</target>
<note />
</trans-unit>
<trans-unit id="NuGetAssemblyNotFound">
<source>A required NuGet assembly was not found. Expected Path: {0}</source>
<target state="new">A required NuGet assembly was not found. Expected Path: {0}</target>
<note />
</trans-unit>
<trans-unit id="NullReferenceFromProjectInstanceFactory">
<source>MSB4253: A null reference was returned from a user-provided ProjectInstanceFactoryFunc callback. This is not allowed.</source>
<target state="new">MSB4253: A null reference was returned from a user-provided ProjectInstanceFactoryFunc callback. This is not allowed.</target>
<note>
{StrBegin="MSB4253: "}
LOCALIZATION: Do not localize the following words: ProjectInstanceFactoryFunc.
</note>
</trans-unit>
<trans-unit id="OM_MatchOnMetadataIsRestrictedToOnlyOneReferencedItem">
<source>Only one item type may be referenced when removing with MatchOnMetadata.</source>
<target state="new">Only one item type may be referenced when removing with MatchOnMetadata.</target>
<note />
</trans-unit>
<trans-unit id="OM_MatchOnMetadataOnlyApplicableToRemoveItems">
<source>MatchOnMetadata only applies to Remove operations on items.</source>
<target state="new">MatchOnMetadata only applies to Remove operations on items.</target>
<note />
</trans-unit>
<trans-unit id="OM_MatchOnMetadataOptionsOnlyApplicableToItemsWithMatchOnMetadata">
<source>MatchOnMetadataOptions is valid only when removing items using MatchOnMetadata.</source>
<target state="new">MatchOnMetadataOptions is valid only when removing items using MatchOnMetadata.</target>
<note />
</trans-unit>
<trans-unit id="OM_NoMatchOnMetadataOutsideTargets">
<source>MatchOnMetadata cannot be used outside of a <Target>.</source>
<target state="new">MatchOnMetadata cannot be used outside of a <Target>.</target>
<note />
</trans-unit>
<trans-unit id="OM_TargetNameNullOrEmpty">
<source>Method {0} cannot be called with a collection containing null or empty target names.</source>
<target state="new">Method {0} cannot be called with a collection containing null or empty target names.</target>
<note />
</trans-unit>
<trans-unit id="ProjectGraphDoesNotSupportProjectReferenceWithToolset">
<source>MSB4250: ProjectGraph does not support ProjectReference items with the ToolsVersion metadata set. Found ProjectReference "{0}" with ToolsVersion in file "{1}"</source>
<target state="new">MSB4250: ProjectGraph does not support ProjectReference items with the ToolsVersion metadata set. Found ProjectReference "{0}" with ToolsVersion in file "{1}"</target>
<note>
{StrBegin="MSB4250: "}
LOCALIZATION: Do not localize the following words: ProjectGraph, ProjectReference, ToolsVersion.
</note>
</trans-unit>
<trans-unit id="PropertyAssignment">
<source>Property initial value: $({0})="{1}" Source: {2}</source>
<target state="new">Property initial value: $({0})="{1}" Source: {2}</target>
<note />
</trans-unit>
<trans-unit id="SkippedConstraintsOnRequest">
<source>MSB4260: Project "{0}" skipped graph isolation constraints on referenced project "{1}"</source>
<target state="new">MSB4260: Project "{0}" skipped graph isolation constraints on referenced project "{1}"</target>
<note>
LOCALIZATION: {0} and {1} are file paths
</note>
</trans-unit>
<trans-unit id="StaticGraphAcceptsSingleSolutionEntryPoint">
<source>MSB4261: Multiple entry points with solutions detected: {0}. If static graph is loaded from a solution, that that solution must be the only entry point.</source>
<target state="new">MSB4261: Multiple entry points with solutions detected: {0}. If static graph is loaded from a solution, that that solution must be the only entry point.</target>
<note>
LOCALIZATION: {0} is a semicolon delimited list of files
</note>
</trans-unit>
<trans-unit id="StaticGraphConstructionMetrics">
<source>"Static graph loaded in {0} seconds: {1} nodes, {2} edges"</source>
<target state="new">"Static graph loaded in {0} seconds: {1} nodes, {2} edges"</target>
<note />
</trans-unit>
<trans-unit id="StaticGraphDoesNotSupportSlnReferences">
<source>MSB4263: Project "{0}" has a reference to solution file "{1}". Referencing solutions is not supported in static graph.
</source>
<target state="new">MSB4263: Project "{0}" has a reference to solution file "{1}". Referencing solutions is not supported in static graph.
</target>
<note>
LOCALIZATION: {0} and {1} are file paths
</note>
</trans-unit>
<trans-unit id="StaticGraphSolutionLoaderEncounteredSolutionWarningsAndErrors">
<source>MSB4262: Solution file "{0}" contains the following warnings and errors:
Warnings: {1}
Errors: {2}
</source>
<target state="new">MSB4262: Solution file "{0}" contains the following warnings and errors:
Warnings: {1}
Errors: {2}
</target>
<note>
LOCALIZATION: {0} is a file, {1} and {2} are semicolon delimited lists of messages
</note>
</trans-unit>
<trans-unit id="TaskReturnedFalseButDidNotLogError">
<source>MSB4181: The "{0}" task returned false but did not log an error.</source>
<target state="new">MSB4181: The "{0}" task returned false but did not log an error.</target>
<note>{StrBegin="MSB4181: "}</note>
</trans-unit>
<trans-unit id="UndeclaredMSBuildTasksNotAllowedInIsolatedGraphBuilds">
<source>MSB4254: The MSBuild task is building project(s) "{0}" which are not specified in the ProjectReference item. In isolated builds this probably means that the references are not explicitly specified as a ProjectReference item in "{1}"</source>
<target state="new">MSB4254: The MSBuild task is building project(s) "{0}" which are not specified in the ProjectReference item. In isolated builds this probably means that the references are not explicitly specified as a ProjectReference item in "{1}"</target>
<note>
{StrBegin="MSB4254:"}
LOCALIZATION: Do not localize the following words: ProjectReference, MSBuild, task.
</note>
</trans-unit>
<trans-unit id="UninitializedPropertyRead">
<source>Read uninitialized property "{0}"</source>
<target state="new">Read uninitialized property "{0}"</target>
<note />
</trans-unit>
<trans-unit id="UsingInputCaches">
<source>Using input build results caches: {0}</source>
<target state="new">Using input build results caches: {0}</target>
<note>
LOCALIZATION: {0} is a list of semicolon separated file paths
</note>
</trans-unit>
<trans-unit id="WaitingForEndOfBuild">
<source>The operation cannot be completed because EndBuild has already been called but existing submissions have not yet completed.</source>
<target state="new">The operation cannot be completed because EndBuild has already been called but existing submissions have not yet completed.</target>
<note />
</trans-unit>
<trans-unit id="SubmissionAlreadyComplete">
<source>The operation cannot be completed because the submission has already been executed.</source>
<target state="new">The operation cannot be completed because the submission has already been executed.</target>
<note />
</trans-unit>
<trans-unit id="ShouldNotDisposeWhenBuildManagerActive">
<source>Cannot dispose the build manager because it is not idle.</source>
<target state="new">Cannot dispose the build manager because it is not idle.</target>
<note />
</trans-unit>
<trans-unit id="BuildAbortedWithMessage">
<source>MSB4197: Build was canceled. {0}</source>
<target state="new">MSB4197: Build was canceled. {0}</target>
<note>{StrBegin="MSB4197: "} Error when the build stops suddenly for some reason. For example, because a child node died.</note>
</trans-unit>
<trans-unit id="BuildFinishedFailure">
<source>Build FAILED.</source>
<target state="new">Build FAILED.</target>
<note />
</trans-unit>
<trans-unit id="BuildFinishedSuccess">
<source>Build succeeded.</source>
<target state="new">Build succeeded.</target>
<note />
</trans-unit>
<trans-unit id="BuildStartedWithTime">
<source>Build started {0}.</source>
<target state="new">Build started {0}.</target>
<note />
</trans-unit>
<trans-unit id="BuildTargetCompletely">
<source>Building target "{0}" completely.</source>
<target state="new">Building target "{0}" completely.</target>
<note>{0} is the name of the target.</note>
</trans-unit>
<trans-unit id="BuildTargetCompletelyNoInputsSpecified">
<source>No input files were specified.</source>
<target state="new">No input files were specified.</target>
<note />
</trans-unit>
<trans-unit id="BuildTargetCompletelyInputNewer">
<source>Input file "{0}" is newer than output file "{1}".</source>
<target state="new">Input file "{0}" is newer than output file "{1}".</target>
<note>{0} and {1} are filenames on disk.</note>
</trans-unit>
<trans-unit id="BuildTargetCompletelyOutputDoesntExist">
<source>Output file "{0}" does not exist.</source>
<target state="new">Output file "{0}" does not exist.</target>
<note>{0} is a filename on disk.</note>
</trans-unit>
<trans-unit id="BuildTargetCompletelyInputDoesntExist">
<source>Input file "{0}" does not exist.</source>
<target state="new">Input file "{0}" does not exist.</target>
<note>{0} is a filename on disk.</note>
</trans-unit>
<trans-unit id="BuildTargetPartially">
<source>Building target "{0}" partially, because some output files are out of date with respect to their input files.</source>
<target state="new">Building target "{0}" partially, because some output files are out of date with respect to their input files.</target>
<note>{0} is the name of the target.</note>
</trans-unit>
<trans-unit id="BuildTargetPartiallyInputNewer">
<source>[{0}: Input={1}, Output={2}] Input file is newer than output file.</source>
<target state="new">[{0}: Input={1}, Output={2}] Input file is newer than output file.</target>
<note>{0} is the name of an MSBuild item. {1} and {2} are filenames on disk.</note>
</trans-unit>
<trans-unit id="BuildTargetPartiallyOutputDoesntExist">
<source>[{0}: Input={1}, Output={2}] Output file does not exist.</source>
<target state="new">[{0}: Input={1}, Output={2}] Output file does not exist.</target>
<note>{0} is the name of an MSBuild item. {1} and {2} are filenames on disk.</note>
</trans-unit>
<trans-unit id="BuildTargetPartiallyInputDoesntExist">
<source>[{0}: Input={1}, Output={2}] Input file does not exist.</source>
<target state="new">[{0}: Input={1}, Output={2}] Input file does not exist.</target>
<note>{0} is the name of an MSBuild item. {1} and {2} are filenames on disk.</note>
</trans-unit>
<trans-unit id="CannotAccessKnownAttributes">
<source>The attribute "{0}" is a known MSBuild attribute, and cannot be accessed using this method.</source>
<target state="new">The attribute "{0}" is a known MSBuild attribute, and cannot be accessed using this method.</target>
<note />
</trans-unit>
<trans-unit id="CannotEvaluateItemMetadata">
<source>MSB4023: Cannot evaluate the item metadata "%({0})". {1}</source>
<target state="new">MSB4023: Cannot evaluate the item metadata "%({0})". {1}</target>
<note>{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.</note>
</trans-unit>
<trans-unit id="CouldNotFindMSBuildExe">
<source>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.</source>
<target state="new">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.</target>
<note>{StrBegin="MSB4193: "}</note>
</trans-unit>
<trans-unit id="CouldNotConnectToMSBuildExe">
<source>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.</source>
<target state="new">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.</target>
<note>{StrBegin="MSB4218: "}</note>
</trans-unit>
<trans-unit id="CannotModifyReservedItem">
<source>MSB4117: The "{0}" item name is reserved, and cannot be used.</source>
<target state="new">MSB4117: The "{0}" item name is reserved, and cannot be used.</target>
<note>{StrBegin="MSB4117: "}UE: This message is shown when the user tries to redefine one of the reserved MSBuild items e.g. @(Choose)</note>
</trans-unit>
<trans-unit id="CannotModifyReservedItemMetadata">
<source>MSB4118: The "{0}" item metadata name is reserved, and cannot be used.</source>
<target state="new">MSB4118: The "{0}" item metadata name is reserved, and cannot be used.</target>
<note>{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.</note>
</trans-unit>
<trans-unit id="CannotModifyReservedProperty">
<source>MSB4004: The "{0}" property is reserved, and cannot be modified.</source>
<target state="new">MSB4004: The "{0}" property is reserved, and cannot be modified.</target>
<note>{StrBegin="MSB4004: "}UE: This message is shown when the user tries to redefine one of the reserved MSBuild properties e.g. $(MSBuildProjectFile)</note>
</trans-unit>
<trans-unit id="CannotPassMultipleItemsIntoScalarParameter">
<source>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}".</source>
<target state="new">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}".</target>
<note>{StrBegin="MSB4094: "}
UE: This error is shown when a project tries to pass multiple items into a task parameter of type ITaskItem (singular).
</note>
</trans-unit>
<trans-unit id="CannotPassMultipleItemsIntoScalarFunction">
<source>MSB4115: The "{0}" function only accepts a scalar value, but its argument "{1}" evaluates to "{2}" which is not a scalar value.</source>
<target state="new">MSB4115: The "{0}" function only accepts a scalar value, but its argument "{1}" evaluates to "{2}" which is not a scalar value.</target>
<note>{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).
</note>
</trans-unit>
<trans-unit id="CannotReferenceItemMetadataWithoutItemName">
<source>MSB4095: The item metadata %({0}) is being referenced without an item name. Specify the item name by using %(itemname.{0}).</source>
<target state="new">MSB4095: The item metadata %({0}) is being referenced without an item name. Specify the item name by using %(itemname.{0}).</target>
<note>{StrBegin="MSB4095: "}</note>
</trans-unit>
<trans-unit id="ChildElementsBelowRemoveNotAllowed">
<source>MSB4162: <{0}> is not valid. Child elements are not allowed below a item remove element.</source>
<target state="new">MSB4162: <{0}> is not valid. Child elements are not allowed below a item remove element.</target>
<note>{StrBegin="MSB4162: "}</note>
</trans-unit>
<trans-unit id="ChildExitedPrematurely">
<source>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}</source>
<target state="new">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}</target>
<note>{StrBegin="MSB4166: "} {2} is exception text if any</note>
</trans-unit>
<trans-unit id="ChooseMustContainWhen">
<source>MSB4085: A <Choose> must contain at least one <When>.</source>
<target state="new">MSB4085: A <Choose> must contain at least one <When>.</target>
<note>{StrBegin="MSB4085: "}</note>
</trans-unit>
<trans-unit id="ChooseOverflow">
<source>MSB4114: <Choose> elements cannot be nested more than {0} levels deep.</source>
<target state="new">MSB4114: <Choose> elements cannot be nested more than {0} levels deep.</target>
<note>{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.</note>
</trans-unit>
<trans-unit id="CircularDependency">
<source>MSB4006: There is a circular dependency in the target dependency graph involving target "{0}".</source>
<target state="new">MSB4006: There is a circular dependency in the target dependency graph involving target "{0}".</target>
<note>{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).</note>
</trans-unit>
<trans-unit id="ComparisonOnNonNumericExpression">
<source>MSB4086: A numeric comparison was attempted on "{1}" that evaluates to "{2}" instead of a number, in condition "{0}".</source>
<target state="new">MSB4086: A numeric comparison was attempted on "{1}" that evaluates to "{2}" instead of a number, in condition "{0}".</target>
<note>{StrBegin="MSB4086: "}</note>
</trans-unit>
<trans-unit id="ConditionMaybeEvaluatedIncorrectly">
<source>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.</source>
<target state="new">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.</target>
<note>{StrBegin="MSB4130: "}</note>
</trans-unit>
<trans-unit id="ConditionNotBoolean">
<source>MSB4087: Specified condition "{0}" does not evaluate to a boolean.</source>
<target state="new">MSB4087: Specified condition "{0}" does not evaluate to a boolean.</target>
<note>{StrBegin="MSB4087: "}</note>
</trans-unit>
<trans-unit id="ConditionNotBooleanDetail">
<source>MSB4113: Specified condition "{0}" evaluates to "{1}" instead of a boolean.</source>
<target state="new">MSB4113: Specified condition "{0}" evaluates to "{1}" instead of a boolean.</target>
<note>{StrBegin="MSB4113: "}</note>
</trans-unit>
<trans-unit id="ConfigFileReadError">
<source>MSB4136: Error reading the toolset information from the configuration file "{0}". {1}</source>
<target state="new">MSB4136: Error reading the toolset information from the configuration file "{0}". {1}</target>
<note>{StrBegin="MSB4136: "}</note>
</trans-unit>
<trans-unit id="ConflictingValuesOfMSBuildToolsPath">
<source>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.</source>
<target state="new">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.</target>
<note>{StrBegin="MSB4142: "}</note>
</trans-unit>
<trans-unit id="DefaultTasksFileFailure">
<source>MSB4009: The default tasks file could not be successfully loaded. {0}</source>
<target state="new">MSB4009: The default tasks file could not be successfully loaded. {0}</target>
<note>{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.</note>
</trans-unit>
<trans-unit id="DefaultTasksFileLoadFailureWarning">
<source>MSB4010: The "{0}" files could not be successfully loaded from their expected location "{1}". Default tasks will not be available. {2}</source>
<target state="new">MSB4010: The "{0}" files could not be successfully loaded from their expected location "{1}". Default tasks will not be available. {2}</target>
<note>{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.</note>
</trans-unit>
<trans-unit id="ImportIntroducesCircularity">
<source>Importing the file "{0}" into the file "{1}" results in a circular dependency.</source>
<target state="new">Importing the file "{0}" into the file "{1}" results in a circular dependency.</target>
<note>
{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.
</note>
</trans-unit>
<trans-unit id="SearchPathsForMSBuildExtensionsPath">
<source>Search paths being used for {0} are {1}</source>
<target state="new">Search paths being used for {0} are {1}</target>
<note />
</trans-unit>
<trans-unit id="TryingExtensionsPath">
<source>Trying to import {0} using extensions path {1}</source>
<target state="new">Trying to import {0} using extensions path {1}</target>
<note />
</trans-unit>
<trans-unit id="OverrideTasksFileFailure">
<source>MSB4194: The override tasks file could not be successfully loaded. {0}</source>
<target state="new">MSB4194: The override tasks file could not be successfully loaded. {0}</target>
<note>
{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.
</note>
</trans-unit>
<trans-unit id="OverrideTaskNotRootedPath">
<source>The override tasks path "{0}" must not be a relative path and must exist on disk. Default tasks will not be overridden.</source>
<target state="new">The override tasks path "{0}" must not be a relative path and must exist on disk. Default tasks will not be overridden.</target>
<note>
UE: This message is shown when the override tasks path in the registry or passed to the toolset is not a full path.
</note>
</trans-unit>
<trans-unit id="OverrideTaskProblemWithPath">
<source>A problem occurred loading the override tasks path "{0}". {1}</source>
<target state="new">A problem occurred loading the override tasks path "{0}". {1}</target>
<note>
UE: This message is shown when the override tasks path in the registry or passed to the toolset is not a full path.
</note>
</trans-unit>
<trans-unit id="OverrideTasksFileLoadFailureWarning">
<source>MSB4196: The "{0}" files could not be successfully loaded from their expected location "{1}". Default tasks will not be overridden. {2}</source>
<target state="new">MSB4196: The "{0}" files could not be successfully loaded from their expected location "{1}". Default tasks will not be overridden. {2}</target>
<note>
{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.
</note>
</trans-unit>
<trans-unit id="TasksPropertyBagError">
<source>MSB4195: There was an error gathering properties for tasks file evaluation. {0}</source>
<target state="new">MSB4195: There was an error gathering properties for tasks file evaluation. {0}</target>
<note>
{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</note>
</trans-unit>
<trans-unit id="DefaultToolsVersionNotFound">
<source>MSB4133: A default tools version "{0}" was specified, but its definition could not be found.</source>
<target state="new">MSB4133: A default tools version "{0}" was specified, but its definition could not be found.</target>
<note>{StrBegin="MSB4133: "}</note>
</trans-unit>
<trans-unit id="DuplicateImport">
<source>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}</source>
<target state="new">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}</target>
<note>{StrBegin="MSB4011: "}</note>
</trans-unit>
<trans-unit id="UsedUninitializedProperty">
<source>MSB4211: The property "{0}" is being set to a value for the first time, but it was already consumed at "{1}".</source>
<target state="new">MSB4211: The property "{0}" is being set to a value for the first time, but it was already consumed at "{1}".</target>
<note>{StrBegin="MSB4211: "}</note>
</trans-unit>
<trans-unit id="SelfImport">
<source>MSB4210: "{0}" is attempting to import itself, directly or indirectly. This is most likely a build authoring error. The import will be ignored.</source>
<target state="new">MSB4210: "{0}" is attempting to import itself, directly or indirectly. This is most likely a build authoring error. The import will be ignored.</target>
<note>{StrBegin="MSB4210: "}</note>
</trans-unit>
<trans-unit id="DuplicateProjectExtensions">
<source>MSB4079: The <ProjectExtensions> element occurs more than once.</source>
<target state="new">MSB4079: The <ProjectExtensions> element occurs more than once.</target>
<note>{StrBegin="MSB4079: "}</note>
</trans-unit>
<trans-unit id="EmbeddedItemVectorCannotBeItemized">
<source>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.</source>
<target state="new">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.</target>
<note>{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"</note>
</trans-unit>
<trans-unit id="EndOfInputTokenName">
<source>end of input</source>
<target state="new">end of input</target>
<note>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.</note>
</trans-unit>
<trans-unit id="ErrorConvertedIntoWarning">
<source>The previous error was converted to a warning because the task was called with ContinueOnError=true.</source>
<target state="new">The previous error was converted to a warning because the task was called with ContinueOnError=true.</target>
<note />
</trans-unit>
<trans-unit id="ErrorCount">
<source>{0} Error(s)</source>
<target state="new">{0} Error(s)</target>
<note />
</trans-unit>
<trans-unit id="ErrorCreatingToolset">
<source>MSB4159: Error creating the toolset "{0}". {1}</source>
<target state="new">MSB4159: Error creating the toolset "{0}". {1}</target>
<note>{StrBegin="MSB4159: "}</note>
</trans-unit>
<trans-unit id="ErrorEvaluatingToolsetPropertyExpression">
<source>MSB4146: Cannot evaluate the property expression "{0}" found at "{1}". {2}</source>
<target state="new">MSB4146: Cannot evaluate the property expression "{0}" found at "{1}". {2}</target>
<note>{StrBegin="MSB4146: "}</note>
</trans-unit>
<trans-unit id="ErrorWarningMessageNotSupported">
<source>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.</source>
<target state="new">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.</target>
<note />
</trans-unit>
<trans-unit id="EvaluationStarted">
<source>Evaluation started ("{0}")</source>
<target state="new">Evaluation started ("{0}")</target>
<note />
</trans-unit>
<trans-unit id="EvaluationFinished">
<source>Evaluation finished ("{0}")</source>
<target state="new">Evaluation finished ("{0}")</target>
<note />
</trans-unit>
<trans-unit id="ExecutingTaskInTaskHost">
<source>Launching task "{0}" from assembly "{1}" in an external task host with a runtime of "{2}" and a process architecture of "{3}".</source>
<target state="new">Launching task "{0}" from assembly "{1}" in an external task host with a runtime of "{2}" and a process architecture of "{3}".</target>
<note />
</trans-unit>
<trans-unit id="ExpressionDoesNotEvaluateToBoolean">
<source>MSB4100: Expected "{0}" to evaluate to a boolean instead of "{1}", in condition "{2}".</source>
<target state="new">MSB4100: Expected "{0}" to evaluate to a boolean instead of "{1}", in condition "{2}".</target>
<note>{StrBegin="MSB4100: "}</note>
</trans-unit>
<trans-unit id="FailedToRetrieveTaskOutputs">
<source>MSB4028: The "{0}" task's outputs could not be retrieved from the "{1}" parameter. {2}</source>
<target state="new">MSB4028: The "{0}" task's outputs could not be retrieved from the "{1}" parameter. {2}</target>
<note>{StrBegin="MSB4028: "}</note>
</trans-unit>
<trans-unit id="FatalBuildError">
<source>MSB4014: The build stopped unexpectedly because of an internal failure.</source>
<target state="new">MSB4014: The build stopped unexpectedly because of an internal failure.</target>
<note>{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.</note>
</trans-unit>
<trans-unit id="FatalErrorDuringLoggerShutdown">
<source>MSB4015: The build stopped unexpectedly because the "{0}" logger failed unexpectedly during shutdown.</source>
<target state="new">MSB4015: The build stopped unexpectedly because the "{0}" logger failed unexpectedly during shutdown.</target>
<note>{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.</note>
</trans-unit>
<trans-unit id="FatalErrorWhileInitializingLogger">
<source>MSB4016: The build stopped unexpectedly because the "{0}" logger failed unexpectedly during initialization.</source>
<target state="new">MSB4016: The build stopped unexpectedly because the "{0}" logger failed unexpectedly during initialization.</target>
<note>{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.</note>
</trans-unit>
<trans-unit id="FatalErrorWhileLogging">
<source>MSB4017: The build stopped unexpectedly because of an unexpected logger failure.</source>
<target state="new">MSB4017: The build stopped unexpectedly because of an unexpected logger failure.</target>
<note>{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.</note>
</trans-unit>
<trans-unit id="FatalTaskError">
<source>MSB4018: The "{0}" task failed unexpectedly.</source>
<target state="new">MSB4018: The "{0}" task failed unexpectedly.</target>
<note>{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.</note>
</trans-unit>
<trans-unit id="FailedToReceiveTaskThreadStatus">
<source>MSB4187: Failed to receive a response from the task thread in the timeout period "{0}" ms. Shutting down.</source>
<target state="new">MSB4187: Failed to receive a response from the task thread in the timeout period "{0}" ms. Shutting down.</target>
<note>{StrBegin="MSB4187: "}</note>
</trans-unit>
<trans-unit id="IllFormedCondition">
<source>MSB4088: Condition "{0}" is improperly constructed.</source>
<target state="new">MSB4088: Condition "{0}" is improperly constructed.</target>
<note>{StrBegin="MSB4088: "}</note>
</trans-unit>
<trans-unit id="IllFormedEqualsInCondition">
<source>MSB4105: Found an unexpected character '{2}' at position {1} in condition "{0}". Did you intend to use "=="?</source>
<target state="new">MSB4105: Found an unexpected character '{2}' at position {1} in condition "{0}". Did you intend to use "=="?</target>
<note>{StrBegin="MSB4105: "}</note>
</trans-unit>
<trans-unit id="IllFormedItemListCloseParenthesisInCondition">
<source>MSB4106: Expected an item list at position {1} in condition "{0}". Did you forget the closing parenthesis?</source>
<target state="new">MSB4106: Expected an item list at position {1} in condition "{0}". Did you forget the closing parenthesis?</target>
<note>{StrBegin="MSB4106: "}</note>
</trans-unit>
<trans-unit id="IllFormedItemListOpenParenthesisInCondition">
<source>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.</source>
<target state="new">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.</target>
<note>{StrBegin="MSB4107: "}</note>
</trans-unit>
<trans-unit id="IllFormedItemListQuoteInCondition">
<source>MSB4108: Expected an item list at position {1} in condition "{0}". Did you forget to close a quote inside the item list expression?</source>
<target state="new">MSB4108: Expected an item list at position {1} in condition "{0}". Did you forget to close a quote inside the item list expression?</target>
<note>{StrBegin="MSB4108: "}</note>
</trans-unit>
<trans-unit id="IllFormedPropertyCloseParenthesisInCondition">
<source>MSB4109: Expected a property at position {1} in condition "{0}". Did you forget the closing parenthesis?</source>
<target state="new">MSB4109: Expected a property at position {1} in condition "{0}". Did you forget the closing parenthesis?</target>
<note>{StrBegin="MSB4109: "}</note>
</trans-unit>
<trans-unit id="IllFormedPropertyOpenParenthesisInCondition">
<source>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.</source>
<target state="new">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.</target>
<note>{StrBegin="MSB4110: "}</note>
</trans-unit>
<trans-unit id="IllFormedQuotedStringInCondition">
<source>MSB4101: Expected a closing quote after position {1} in condition "{0}".</source>
<target state="new">MSB4101: Expected a closing quote after position {1} in condition "{0}".</target>
<note>{StrBegin="MSB4101: "}</note>
</trans-unit>
<trans-unit id="ImportedProjectNotFound">
<source>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.</source>
<target state="new">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.</target>
<note>{StrBegin="MSB4019: "}LOCALIZATION: <Import> should not be localized.</note>
</trans-unit>
<trans-unit id="ImportedProjectFromExtensionsPathNotFoundFromAppConfig">
<source>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.</source>
<target state="new">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.</target>
<note>{StrBegin="MSB4226: "}LOCALIZATION: <Import> should not be localized.</note>
</trans-unit>
<trans-unit id="ImportedProjectFromExtensionsPathNotFound">
<source>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.</source>
<target state="new">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.</target>
<note>{StrBegin="MSB4226: "}LOCALIZATION: <Import> should not be localized.</note>
</trans-unit>
<trans-unit id="IncorrectNumberOfFunctionArguments">
<source>MSB4089: Incorrect number of arguments to function in condition "{0}". Found {1} argument(s) when expecting {2}.</source>
<target state="new">MSB4089: Incorrect number of arguments to function in condition "{0}". Found {1} argument(s) when expecting {2}.</target>
<note>{StrBegin="MSB4089: "}</note>
</trans-unit>
<trans-unit id="InvalidAttributeValue">
<source>MSB4020: The value "{0}" of the "{1}" attribute in element <{2}> is invalid.</source>
<target state="new">MSB4020: The value "{0}" of the "{1}" attribute in element <{2}> is invalid.</target>
<note>{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.</note>
</trans-unit>
<trans-unit id="InvalidAttributeExclusive">
<source>MSB4111: At most one of the include, remove, and update attributes may be specified for an item element.</source>
<target state="new">MSB4111: At most one of the include, remove, and update attributes may be specified for an item element.</target>
<note />
</trans-unit>
<trans-unit id="InvalidAttributeValueWithException">
<source>MSB4102: The value "{0}" of the "{1}" attribute in element <{2}> is invalid. {3}</source>
<target state="new">MSB4102: The value "{0}" of the "{1}" attribute in element <{2}> is invalid. {3}</target>
<note>{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.</note>
</trans-unit>
<trans-unit id="InvalidBinaryLoggerParameters">
<source>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).</source>
<target state="new">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).</target>
<note />
</trans-unit>
<trans-unit id="InvalidContinueOnErrorAttribute">
<source>MSB4021: The "ContinueOnError" attribute of the "{0}" task is not valid. {1}</source>
<target state="new">MSB4021: The "ContinueOnError" attribute of the "{0}" task is not valid. {1}</target>
<note>{StrBegin="MSB4021: "}LOCALIZATION: "ContinueOnError" should not be localized. "{1}" is a message from another exception explaining the problem.</note>
</trans-unit>
<trans-unit id="InvalidEvaluatedAttributeValue">
<source>MSB4022: The result "{0}" of evaluating the value "{1}" of the "{2}" attribute in element <{3}> is not valid.</source>
<target state="new">MSB4022: The result "{0}" of evaluating the value "{1}" of the "{2}" attribute in element <{3}> is not valid.</target>
<note>{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.</note>
</trans-unit>
<trans-unit id="InvalidFileLoggerFile">
<source>MSB4104: Failed to write to log file "{0}". {1}</source>
<target state="new">MSB4104: Failed to write to log file "{0}". {1}</target>
<note>{StrBegin="MSB4104: "}UE: This is shown when the File Logger can't create or write to the file it was instructed to log to.</note>
</trans-unit>
<trans-unit id="InvalidImportedProjectFile">
<source>MSB4024: The imported project file "{0}" could not be loaded. {1}</source>
<target state="new">MSB4024: The imported project file "{0}" could not be loaded. {1}</target>
<note>{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.</note>
</trans-unit>
<trans-unit id="InvalidPropertyNameInToolset">
<source>MSB4147: The property "{0}" at "{1}" is invalid. {2}</source>
<target state="new">MSB4147: The property "{0}" at "{1}" is invalid. {2}</target>
<note>{StrBegin="MSB4147: "}</note>
</trans-unit>
<trans-unit id="InvalidProperty">
<source>MSB4177: Invalid property. {0}</source>
<target state="new">MSB4177: Invalid property. {0}</target>
<note>{StrBegin="MSB4177: "}
UE: {0} is a localized message indicating what the problem was.</note>
</trans-unit>
<trans-unit id="InvalidRegistryPropertyExpression">
<source>MSB4143: The registry expression "{0}" cannot be evaluated. {1}</source>
<target state="new">MSB4143: The registry expression "{0}" cannot be evaluated. {1}</target>
<note>{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.
</note>
</trans-unit>
<trans-unit id="InvalidFunctionPropertyExpression">
<source>MSB4184: The expression "{0}" cannot be evaluated. {1}</source>
<target state="new">MSB4184: The expression "{0}" cannot be evaluated. {1}</target>
<note>{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.
</note>
</trans-unit>
<trans-unit id="InvalidFunctionPropertyExpressionDetailMismatchedQuote">
<source>The quotes were mismatched.</source>
<target state="new">The quotes were mismatched.</target>
<note>This is a potential suffix to "InvalidFunctionPropertyExpression" so it has no error code.</note>
</trans-unit>
<trans-unit id="InvalidFunctionPropertyExpressionDetailMismatchedParenthesis">
<source>The parentheses were mismatched.</source>
<target state="new">The parentheses were mismatched.</target>
<note>This is a potential suffix to "InvalidFunctionPropertyExpression" so it has no error code.</note>
</trans-unit>
<trans-unit id="InvalidFunctionPropertyExpressionDetailMismatchedSquareBrackets">
<source>The square brackets were mismatched.</source>
<target state="new">The square brackets were mismatched.</target>
<note>This is a potential suffix to "InvalidFunctionPropertyExpression" so it has no error code.</note>
</trans-unit>
<trans-unit id="InvalidFunctionMethodUnavailable">
<source>MSB4185: The function "{0}" on type "{1}" is not available for execution as an MSBuild property function.</source>
<target state="new">MSB4185: The function "{0}" on type "{1}" is not available for execution as an MSBuild property function.</target>
<note>
{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
</note>
</trans-unit>
<trans-unit id="InvalidFunctionTypeUnavailable">
<source>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.</source>
<target state="new">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.</target>
<note>
{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
</note>
</trans-unit>
<trans-unit id="InvalidFunctionStaticMethodSyntax">
<source>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.</source>
<target state="new">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.</target>
<note>{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.
</note>
</trans-unit>
<trans-unit id="InvalidItemFunctionExpression">
<source>MSB4198: The expression "{0}" cannot be evaluated on item "{1}". {2}</source>
<target state="new">MSB4198: The expression "{0}" cannot be evaluated on item "{1}". {2}</target>
<note>
{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.
</note>
</trans-unit>
<trans-unit id="InvalidItemFunctionSyntax">
<source>MSB4199: Invalid transformation syntax "{0}". An item function was not found with that name and {1} parameters.</source>
<target state="new">MSB4199: Invalid transformation syntax "{0}". An item function was not found with that name and {1} parameters.</target>
<note>
{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
</note>
</trans-unit>
<trans-unit id="UnknownItemFunction">
<source>MSB4200: Unknown item transformation function "{0}".</source>
<target state="new">MSB4200: Unknown item transformation function "{0}".</target>
<note>
{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
</note>
</trans-unit>
<trans-unit id="InvalidTaskAttributeError">
<source>MSB4026: The "{0}={1}" parameter for the "{2}" task is invalid.</source>
<target state="new">MSB4026: The "{0}={1}" parameter for the "{2}" task is invalid.</target>
<note>{StrBegin="MSB4026: "}UE: This message is displayed when a task has an invalid parameter that cannot be initialized.</note>
</trans-unit>
<trans-unit id="InvalidTaskItemsInTaskOutputs">
<source>MSB4027: The "{0}" task generated invalid items from the "{1}" output parameter. {2}</source>
<target state="new">MSB4027: The "{0}" task generated invalid items from the "{1}" output parameter. {2}</target>
<note>{StrBegin="MSB4027: "}</note>
</trans-unit>
<trans-unit id="InvalidTaskOutputSpecification">
<source>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).</source>
<target state="new">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).</target>
<note>{StrBegin="MSB4029: "}LOCALIZATION: "TaskParameter", "ItemName" and "PropertyName" should not be localized.</note>
</trans-unit>
<trans-unit id="InvalidTaskParameterValueError">
<source>MSB4030: "{0}" is an invalid value for the "{1}" parameter of the "{3}" task. The "{1}" parameter is of type "{2}".</source>
<target state="new">MSB4030: "{0}" is an invalid value for the "{1}" parameter of the "{3}" task. The "{1}" parameter is of type "{2}".</target>
<note>{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" /></note>
</trans-unit>
<trans-unit id="InvalidToolsetValueInConfigFileValue">
<source>MSB4137: Invalid value specified in the configuration file at "{0}". Property name or tools version name is an empty string.</source>
<target state="new">MSB4137: Invalid value specified in the configuration file at "{0}". Property name or tools version name is an empty string.</target>
<note>{StrBegin="MSB4137: "}</note>
</trans-unit>
<trans-unit id="ItemDefinitionGroupNotLegalInsideTarget">
<source>MSB4163: <ItemDefinitionGroup> is not allowed inside a target.</source>
<target state="new">MSB4163: <ItemDefinitionGroup> is not allowed inside a target.</target>
<note>{StrBegin="MSB4163: "}</note>
</trans-unit>
<trans-unit id="ItemDoesNotContainValueForUnqualifiedMetadata">
<source>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.</source>
<target state="new">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.</target>
<note>{StrBegin="MSB4096: "}</note>
</trans-unit>
<trans-unit id="ItemListNotAllowedInThisConditional">
<source>MSB4099: A reference to an item list at position {1} is not allowed in this condition "{0}".</source>
<target state="new">MSB4099: A reference to an item list at position {1} is not allowed in this condition "{0}".</target>
<note>{StrBegin="MSB4099: "}</note>
</trans-unit>
<trans-unit id="CustomMetadataNotAllowedInThisConditional">
<source>MSB4191: The reference to custom metadata "{2}" at position {1} is not allowed in this condition "{0}".</source>
<target state="new">MSB4191: The reference to custom metadata "{2}" at position {1} is not allowed in this condition "{0}".</target>
<note>{StrBegin="MSB4191: "}</note>
</trans-unit>
<trans-unit id="BuiltInMetadataNotAllowedInThisConditional">
<source>MSB4190: The reference to the built-in metadata "{2}" at position {1} is not allowed in this condition "{0}".</source>
<target state="new">MSB4190: The reference to the built-in metadata "{2}" at position {1} is not allowed in this condition "{0}".</target>
<note>{StrBegin="MSB4190: "}</note>
</trans-unit>
<trans-unit id="ItemSpecModifierCannotBeCustomMetadata">
<source>MSB4033: "{0}" is a reserved item metadata, and cannot be redefined as a custom metadata on the item.</source>
<target state="new">MSB4033: "{0}" is a reserved item metadata, and cannot be redefined as a custom metadata on the item.</target>
<note>{StrBegin="MSB4033: "}</note>
</trans-unit>
<trans-unit id="InternalLoggerExceptionOnlyThrownByEngine">
<source>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.</source>
<target state="new">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.</target>
<note>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.</note>
</trans-unit>
<trans-unit id="ItemListHeader">
<source>Initial Items:</source>
<target state="new">Initial Items:</target>
<note />
</trans-unit>
<trans-unit id="EnvironmentHeader">
<source>Environment at start of build:</source>
<target state="new">Environment at start of build:</target>
<note />
</trans-unit>
<trans-unit id="MetadataDefinitionCannotContainItemVectorExpression">
<source>MSB4164: The value "{0}" of metadata "{1}" contains an item list expression. Item list expressions are not allowed on default metadata values.</source>
<target state="new">MSB4164: The value "{0}" of metadata "{1}" contains an item list expression. Item list expressions are not allowed on default metadata values.</target>
<note>{StrBegin="MSB4164: "}</note>
</trans-unit>
<trans-unit id="MissingRequiredAttribute">
<source>MSB4035: The required attribute "{0}" is empty or missing from the element <{1}>.</source>
<target state="new">MSB4035: The required attribute "{0}" is empty or missing from the element <{1}>.</target>
<note>{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.</note>
</trans-unit>
<trans-unit id="IncludeRemoveOrUpdate">
<source>MSB4232: Items that are outside Target elements must have one of the following operations: Include, Update, or Remove.</source>
<target state="new">MSB4232: Items that are outside Target elements must have one of the following operations: Include, Update, or Remove.</target>
<note>{StrBegin="MSB4232: "} Target, Include, Update, and Remove should not be localized and their casing should not be changed</note>
</trans-unit>
<trans-unit id="MissingTaskError">
<source>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.</source>
<target state="new">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.</target>
<note>{StrBegin="MSB4036: "}LOCALIZATION: <UsingTask> and "*.tasks" should not be localized.</note>
</trans-unit>
<trans-unit id="MSBuildToolsPathIsNotSpecified">
<source>MSB4141: MSBuildToolsPath is not specified for the ToolsVersion "{0}" defined at "{1}", or the value specified evaluates to the empty string.</source>
<target state="new">MSB4141: MSBuildToolsPath is not specified for the ToolsVersion "{0}" defined at "{1}", or the value specified evaluates to the empty string.</target>
<note>{StrBegin="MSB4141: "}</note>
</trans-unit>
<trans-unit id="MSBuildToolsPathNotSupportedInSubToolsets">
<source>MSB4222: ToolsVersion "{0}", defined at "{1}", contains sub-toolset "{2}" which sets MSBuildBinPath or MSBuildToolsPath. This is not supported in sub-toolsets.</source>
<target state="new">MSB4222: ToolsVersion "{0}", defined at "{1}", contains sub-toolset "{2}" which sets MSBuildBinPath or MSBuildToolsPath. This is not supported in sub-toolsets.</target>
<note />
</trans-unit>
<trans-unit id="MultipleDefinitionsForSameToolset">
<source>MSB4144: Multiple definitions were found for the toolset "{0}". </source>
<target state="new">MSB4144: Multiple definitions were found for the toolset "{0}". </target>
<note>{StrBegin="MSB4144: "}</note>
</trans-unit>
<trans-unit id="MultipleDefinitionsForSameExtensionsPathOS">
<source>MSB4225: Toolset contains multiple definitions of searchPaths for the OS "{0}" at "{1}".</source>
<target state="new">MSB4225: Toolset contains multiple definitions of searchPaths for the OS "{0}" at "{1}".</target>
<note>{StrBegin="MSB4225: "}</note>
</trans-unit>
<trans-unit id="MultipleDefinitionsForSameProperty">
<source>MSB4145: Multiple definitions were found for the property "{0}".</source>
<target state="new">MSB4145: Multiple definitions were found for the property "{0}".</target>
<note>{StrBegin="MSB4145: "}</note>
</trans-unit>
<trans-unit id="MultipleOtherwise">
<source>MSB4082: Choose has more than one <Otherwise> element.</source>
<target state="new">MSB4082: Choose has more than one <Otherwise> element.</target>
<note>{StrBegin="MSB4082: "}</note>
</trans-unit>
<trans-unit id="NodeMustBeLastUnderElement">
<source>MSB4038: The element <{0}> must be last under element <{1}>. Found element <{2}> instead.</source>
<target state="new">MSB4038: The element <{0}> must be last under element <{1}>. Found element <{2}> instead.</target>
<note>{StrBegin="MSB4038: "}</note>
</trans-unit>
<trans-unit id="NonStringDataInRegistry">
<source>MSB4138: Non-string data was specified at the registry location "{0}".</source>
<target state="new">MSB4138: Non-string data was specified at the registry location "{0}".</target>
<note>{StrBegin="MSB4138: "}</note>
</trans-unit>
<trans-unit id="NoRootProjectElement">
<source>MSB4039: No "{0}" element was found in the project file.</source>
<target state="new">MSB4039: No "{0}" element was found in the project file.</target>
<note>{StrBegin="MSB4039: "}</note>
</trans-unit>
<trans-unit id="NoTargetSpecified">
<source>MSB4040: There is no target in the project.</source>