-
Notifications
You must be signed in to change notification settings - Fork 1.3k
/
Strings.en.xlf
1517 lines (1489 loc) · 94.2 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="AmbiguousProjectError">
<source>MSBUILD : error MSB1011: Specify which project or solution file to use because this folder contains more than one project or solution file.</source>
<target state="new">MSBUILD : error MSB1011: Specify which project or solution file to use because this folder contains more than one project or solution file.</target>
<note>{StrBegin="MSBUILD : error MSB1011: "}UE: If no project or solution file is explicitly specified on the MSBuild.exe command-line, then the engine searches for a
project or solution file in the current directory by looking for *.*PROJ and *.SLN. If more than one file is found that matches this wildcard, we
fire this error.
LOCALIZATION: The prefix "MSBUILD : error MSBxxxx:" should not be localized.</note>
</trans-unit>
<trans-unit id="AmbiguousProjectDirectoryError">
<source>MSBUILD : error MSB1050: Specify which project or solution file to use because the folder "{0}" contains more than one project or solution file.</source>
<target state="new">MSBUILD : error MSB1050: Specify which project or solution file to use because the folder "{0}" contains more than one project or solution file.</target>
<note>
{StrBegin="MSBUILD : error MSB1050: "}UE: If no project or solution file is explicitly specified on the MSBuild.exe command-line, then the engine searches for a
project or solution file in the current directory by looking for *.*PROJ and *.SLN. If more than one file is found that matches this wildcard, we
fire this error.
LOCALIZATION: The prefix "MSB1050 : error MSBxxxx:" should not be localized.
</note>
</trans-unit>
<trans-unit id="ConfigurationFailurePrefixNoErrorCode">
<source>MSBUILD : Configuration error {0}: {1}</source>
<target state="new">MSBUILD : Configuration error {0}: {1}</target>
<note>{SubString="Configuration"}UE: This prefixes any error from reading the toolset definitions in msbuild.exe.config or the registry.
There's no error code because one was included in the error message.
LOCALIZATION: The word "Configuration" should be localized, the words "MSBuild" and "error" should NOT be localized.
</note>
</trans-unit>
<trans-unit id="CannotAutoDisableAutoResponseFile">
<source>MSBUILD : error MSB1027: The -noAutoResponse switch cannot be specified in the MSBuild.rsp auto-response file, nor in any response file that is referenced by the auto-response file.</source>
<target state="new">MSBUILD : error MSB1027: The -noAutoResponse switch cannot be specified in the MSBuild.rsp auto-response file, nor in any response file that is referenced by the auto-response file.</target>
<note>{StrBegin="MSBUILD : error MSB1027: "}LOCALIZATION: The prefix "MSBUILD : error MSBxxxx:", "-noAutoResponse" and "MSBuild.rsp" should not be localized.</note>
</trans-unit>
<trans-unit id="CopyrightMessage">
<source>Microsoft (R) Build Engine version {0} for {1}
Copyright (C) Microsoft Corporation. All rights reserved.
</source>
<target state="new">Microsoft (R) Build Engine version {0} for {1}
Copyright (C) Microsoft Corporation. All rights reserved.
</target>
<note>LOCALIZATION: {0} contains the DLL version number. {1} contains the name of a runtime, like ".NET Framework", ".NET Core", or "Mono"</note>
</trans-unit>
<trans-unit id="DuplicateProjectSwitchError">
<source>MSBUILD : error MSB1008: Only one project can be specified.</source>
<target state="new">MSBUILD : error MSB1008: Only one project can be specified.</target>
<note>{StrBegin="MSBUILD : error MSB1008: "}UE: This happens if the user does something like "msbuild.exe myapp.proj myapp2.proj". This is not allowed.
MSBuild.exe will only build a single project. The help topic may link to an article about how to author an MSBuild project
that itself launches MSBuild on a number of other projects.
LOCALIZATION: The prefix "MSBUILD : error MSBxxxx:" should not be localized.</note>
</trans-unit>
<trans-unit id="FatalError">
<source>MSBUILD : error MSB1025: An internal failure occurred while running MSBuild.</source>
<target state="new">MSBUILD : error MSB1025: An internal failure occurred while running MSBuild.</target>
<note>{StrBegin="MSBUILD : error MSB1025: "}UE: This message is shown when the application has to terminate either because of a bug in the code, or because some
FX/CLR method threw an unexpected exception.
LOCALIZATION: The prefix "MSBUILD : error MSBxxxx:" and "MSBuild" should not be localized.</note>
</trans-unit>
<trans-unit id="HelpMessage_1_Syntax">
<source>Syntax: MSBuild.exe [options] [project file | directory]
</source>
<target state="new">Syntax: MSBuild.exe [options] [project file | directory]
</target>
<note>
LOCALIZATION: The following should not be localized:
1) "MSBuild", "MSBuild.exe" and "MSBuild.rsp"
2) the string "proj" that describes the extension we look for
3) all switch names and their short forms e.g. -property, or -p
4) all verbosity levels and their short forms e.g. quiet, or q
LOCALIZATION: None of the lines should be longer than a standard width console window, eg 80 chars.
</note>
</trans-unit>
<trans-unit id="HelpMessage_2_Description">
<source>Description: Builds the specified targets in the project file. If
a project file is not specified, MSBuild searches the
current working directory for a file that has a file
extension that ends in "proj" and uses that file. If
a directory is specified, MSBuild searches that
directory for a project file.
</source>
<target state="new">Description: Builds the specified targets in the project file. If
a project file is not specified, MSBuild searches the
current working directory for a file that has a file
extension that ends in "proj" and uses that file. If
a directory is specified, MSBuild searches that
directory for a project file.
</target>
<note>
LOCALIZATION: The following should not be localized:
1) "MSBuild", "MSBuild.exe" and "MSBuild.rsp"
2) the string "proj" that describes the extension we look for
3) all switch names and their short forms e.g. -property, or -p
4) all verbosity levels and their short forms e.g. quiet, or q
LOCALIZATION: None of the lines should be longer than a standard width console window, eg 80 chars.
</note>
</trans-unit>
<trans-unit id="HelpMessage_34_InteractiveSwitch">
<source> -interactive[:True|False]
Indicates that actions in the build are allowed to
interact with the user. Do not use this argument
in an automated scenario where interactivity is
not expected.
Specifying -interactive is the same as specifying
-interactive:true. Use the parameter to override a
value that comes from a response file.
</source>
<target state="new"> -interactive[:True|False]
Indicates that actions in the build are allowed to
interact with the user. Do not use this argument
in an automated scenario where interactivity is
not expected.
Specifying -interactive is the same as specifying
-interactive:true. Use the parameter to override a
value that comes from a response file.
</target>
<note>
LOCALIZATION: "-interactive" should not be localized.
LOCALIZATION: None of the lines should be longer than a standard width console window, eg 80 chars.
</note>
</trans-unit>
<trans-unit id="HelpMessage_35_IsolateProjectsSwitch">
<source> -isolateProjects[:True|False]
Causes MSBuild to build each project in isolation.
This is a more restrictive mode of MSBuild as it requires
that the project graph be statically discoverable at
evaluation time, but can improve scheduling and reduce
memory overhead when building a large set of projects.
</source>
<target state="new"> -isolateProjects[:True|False]
Causes MSBuild to build each project in isolation.
This is a more restrictive mode of MSBuild as it requires
that the project graph be statically discoverable at
evaluation time, but can improve scheduling and reduce
memory overhead when building a large set of projects.
</target>
<note>
LOCALIZATION: "MSBuild" should not be localized.
LOCALIZATION: "-isolateProjects" should not be localized.
LOCALIZATION: None of the lines should be longer than a standard width console window, eg 80 chars.</note>
</trans-unit>
<trans-unit id="HelpMessage_3_SwitchesHeader">
<source>Switches: Note that you can specify switches using both
"-switch" and "/switch".
</source>
<target state="new">Switches: Note that you can specify switches using both
"-switch" and "/switch".
</target>
<note>
LOCALIZATION: The following should not be localized:
1) "MSBuild", "MSBuild.exe" and "MSBuild.rsp"
2) the string "proj" that describes the extension we look for
3) all switch names and their short forms e.g. -property, or -p
4) all verbosity levels and their short forms e.g. quiet, or q
LOCALIZATION: None of the lines should be longer than a standard width console window, eg 80 chars.
</note>
</trans-unit>
<trans-unit id="HelpMessage_4_HelpSwitch">
<source> -help Display this usage message. (Short form: -? or -h)
</source>
<target state="new"> -help Display this usage message. (Short form: -? or -h)
</target>
<note>
LOCALIZATION: The following should not be localized:
1) "MSBuild", "MSBuild.exe" and "MSBuild.rsp"
2) the string "proj" that describes the extension we look for
3) all switch names and their short forms e.g. -property, or -p
4) all verbosity levels and their short forms e.g. quiet, or q
LOCALIZATION: None of the lines should be longer than a standard width console window, eg 80 chars.
</note>
</trans-unit>
<trans-unit id="HelpMessage_5_NoLogoSwitch">
<source> -noLogo Do not display the startup banner and copyright message.
</source>
<target state="new"> -noLogo Do not display the startup banner and copyright message.
</target>
<note>
LOCALIZATION: The following should not be localized:
1) "MSBuild", "MSBuild.exe" and "MSBuild.rsp"
2) the string "proj" that describes the extension we look for
3) all switch names and their short forms e.g. -property, or -p
4) all verbosity levels and their short forms e.g. quiet, or q
LOCALIZATION: None of the lines should be longer than a standard width console window, eg 80 chars.
</note>
</trans-unit>
<trans-unit id="HelpMessage_6_VersionSwitch">
<source> -version Display version information only. (Short form: -ver)
</source>
<target state="new"> -version Display version information only. (Short form: -ver)
</target>
<note>
LOCALIZATION: The following should not be localized:
1) "MSBuild", "MSBuild.exe" and "MSBuild.rsp"
2) the string "proj" that describes the extension we look for
3) all switch names and their short forms e.g. -property, or -p
4) all verbosity levels and their short forms e.g. quiet, or q
LOCALIZATION: None of the lines should be longer than a standard width console window, eg 80 chars.
</note>
</trans-unit>
<trans-unit id="HelpMessage_7_ResponseFile">
<source> @<file> Insert command-line settings from a text file. To specify
multiple response files, specify each response file
separately.
Any response files named "msbuild.rsp" are automatically
consumed from the following locations:
(1) the directory of msbuild.exe
(2) the directory of the first project or solution built
</source>
<target state="new"> @<file> Insert command-line settings from a text file. To specify
multiple response files, specify each response file
separately.
Any response files named "msbuild.rsp" are automatically
consumed from the following locations:
(1) the directory of msbuild.exe
(2) the directory of the first project or solution built
</target>
<note>
LOCALIZATION: The following should not be localized:
1) "MSBuild", "MSBuild.exe" and "MSBuild.rsp"
2) the string "proj" that describes the extension we look for
3) all switch names and their short forms e.g. -property, or -p
4) all verbosity levels and their short forms e.g. quiet, or q
LOCALIZATION: None of the lines should be longer than a standard width console window, eg 80 chars.
</note>
</trans-unit>
<trans-unit id="HelpMessage_8_NoAutoResponseSwitch">
<source> -noAutoResponse Do not auto-include any MSBuild.rsp files. (Short form:
-noAutoRsp)
</source>
<target state="new"> -noAutoResponse Do not auto-include any MSBuild.rsp files. (Short form:
-noAutoRsp)
</target>
<note>
LOCALIZATION: The following should not be localized:
1) "MSBuild", "MSBuild.exe" and "MSBuild.rsp"
2) the string "proj" that describes the extension we look for
3) all switch names and their short forms e.g. -property, or -p
4) all verbosity levels and their short forms e.g. quiet, or q
LOCALIZATION: None of the lines should be longer than a standard width console window, eg 80 chars.
</note>
</trans-unit>
<trans-unit id="HelpMessage_9_TargetSwitch">
<source> -target:<targets> Build these targets in this project. Use a semicolon or a
comma to separate multiple targets, or specify each
target separately. (Short form: -t)
Example:
-target:Resources;Compile
</source>
<target state="new"> -target:<targets> Build these targets in this project. Use a semicolon or a
comma to separate multiple targets, or specify each
target separately. (Short form: -t)
Example:
-target:Resources;Compile
</target>
<note>
LOCALIZATION: The following should not be localized:
1) "MSBuild", "MSBuild.exe" and "MSBuild.rsp"
2) the string "proj" that describes the extension we look for
3) all switch names and their short forms e.g. -property, or -p
4) all verbosity levels and their short forms e.g. quiet, or q
LOCALIZATION: None of the lines should be longer than a standard width console window, eg 80 chars.
</note>
</trans-unit>
<trans-unit id="HelpMessage_10_PropertySwitch">
<source> -property:<n>=<v> Set or override these project-level properties. <n> is
the property name, and <v> is the property value. Use a
semicolon or a comma to separate multiple properties, or
specify each property separately. (Short form: -p)
Example:
-property:WarningLevel=2;OutDir=bin\Debug\
</source>
<target state="new"> -property:<n>=<v> Set or override these project-level properties. <n> is
the property name, and <v> is the property value. Use a
semicolon or a comma to separate multiple properties, or
specify each property separately. (Short form: -p)
Example:
-property:WarningLevel=2;OutDir=bin\Debug\
</target>
<note>
LOCALIZATION: The following should not be localized:
1) "MSBuild", "MSBuild.exe" and "MSBuild.rsp"
2) the string "proj" that describes the extension we look for
3) all switch names and their short forms e.g. -property, or -p
4) all verbosity levels and their short forms e.g. quiet, or q
LOCALIZATION: None of the lines should be longer than a standard width console window, eg 80 chars.
</note>
</trans-unit>
<trans-unit id="HelpMessage_11_LoggerSwitch">
<source> -logger:<logger> Use this logger to log events from MSBuild. To specify
multiple loggers, specify each logger separately.
The <logger> syntax is:
[<logger class>,]<logger assembly>[;<logger parameters>]
The <logger class> syntax is:
[<partial or full namespace>.]<logger class name>
The <logger assembly> syntax is:
{<assembly name>[,<strong name>] | <assembly file>}
The <logger parameters> are optional, and are passed
to the logger exactly as you typed them. (Short form: -l)
Examples:
-logger:XMLLogger,MyLogger,Version=1.0.2,Culture=neutral
-logger:XMLLogger,C:\Loggers\MyLogger.dll;OutputAsHTML
</source>
<target state="new"> -logger:<logger> Use this logger to log events from MSBuild. To specify
multiple loggers, specify each logger separately.
The <logger> syntax is:
[<logger class>,]<logger assembly>[;<logger parameters>]
The <logger class> syntax is:
[<partial or full namespace>.]<logger class name>
The <logger assembly> syntax is:
{<assembly name>[,<strong name>] | <assembly file>}
The <logger parameters> are optional, and are passed
to the logger exactly as you typed them. (Short form: -l)
Examples:
-logger:XMLLogger,MyLogger,Version=1.0.2,Culture=neutral
-logger:XMLLogger,C:\Loggers\MyLogger.dll;OutputAsHTML
</target>
<note>
LOCALIZATION: The following should not be localized:
1) "MSBuild", "MSBuild.exe" and "MSBuild.rsp"
2) the string "proj" that describes the extension we look for
3) all switch names and their short forms e.g. -property, or -p
4) all verbosity levels and their short forms e.g. quiet, or q
LOCALIZATION: None of the lines should be longer than a standard width console window, eg 80 chars.
</note>
</trans-unit>
<trans-unit id="HelpMessage_12_VerbositySwitch">
<source> -verbosity:<level> Display this amount of information in the event log.
The available verbosity levels are: q[uiet], m[inimal],
n[ormal], d[etailed], and diag[nostic]. (Short form: -v)
Example:
-verbosity:quiet
</source>
<target state="new"> -verbosity:<level> Display this amount of information in the event log.
The available verbosity levels are: q[uiet], m[inimal],
n[ormal], d[etailed], and diag[nostic]. (Short form: -v)
Example:
-verbosity:quiet
</target>
<note>
LOCALIZATION: The following should not be localized:
1) "MSBuild", "MSBuild.exe" and "MSBuild.rsp"
2) the string "proj" that describes the extension we look for
3) all switch names and their short forms e.g. -property, or -p
4) all verbosity levels and their short forms e.g. quiet, or q
LOCALIZATION: None of the lines should be longer than a standard width console window, eg 80 chars.
</note>
</trans-unit>
<trans-unit id="HelpMessage_13_ConsoleLoggerParametersSwitch">
<source> -consoleLoggerParameters:<parameters>
Parameters to console logger. (Short form: -clp)
The available parameters are:
PerformanceSummary--Show time spent in tasks, targets
and projects.
Summary--Show error and warning summary at the end.
NoSummary--Don't show error and warning summary at the
end.
ErrorsOnly--Show only errors.
WarningsOnly--Show only warnings.
NoItemAndPropertyList--Don't show list of items and
properties at the start of each project build.
ShowCommandLine--Show TaskCommandLineEvent messages
ShowTimestamp--Display the Timestamp as a prefix to any
message.
ShowEventId--Show eventId for started events, finished
events, and messages
ForceNoAlign--Does not align the text to the size of
the console buffer
DisableConsoleColor--Use the default console colors
for all logging messages.
DisableMPLogging-- Disable the multiprocessor
logging style of output when running in
non-multiprocessor mode.
EnableMPLogging--Enable the multiprocessor logging
style even when running in non-multiprocessor
mode. This logging style is on by default.
ForceConsoleColor--Use ANSI console colors even if
console does not support it
Verbosity--overrides the -verbosity setting for this
logger.
Example:
-consoleLoggerParameters:PerformanceSummary;NoSummary;
Verbosity=minimal
</source>
<target state="new"> -consoleLoggerParameters:<parameters>
Parameters to console logger. (Short form: -clp)
The available parameters are:
PerformanceSummary--Show time spent in tasks, targets
and projects.
Summary--Show error and warning summary at the end.
NoSummary--Don't show error and warning summary at the
end.
ErrorsOnly--Show only errors.
WarningsOnly--Show only warnings.
NoItemAndPropertyList--Don't show list of items and
properties at the start of each project build.
ShowCommandLine--Show TaskCommandLineEvent messages
ShowTimestamp--Display the Timestamp as a prefix to any
message.
ShowEventId--Show eventId for started events, finished
events, and messages
ForceNoAlign--Does not align the text to the size of
the console buffer
DisableConsoleColor--Use the default console colors
for all logging messages.
DisableMPLogging-- Disable the multiprocessor
logging style of output when running in
non-multiprocessor mode.
EnableMPLogging--Enable the multiprocessor logging
style even when running in non-multiprocessor
mode. This logging style is on by default.
ForceConsoleColor--Use ANSI console colors even if
console does not support it
Verbosity--overrides the -verbosity setting for this
logger.
Example:
-consoleLoggerParameters:PerformanceSummary;NoSummary;
Verbosity=minimal
</target>
<note>
LOCALIZATION: The following should not be localized:
1) "MSBuild", "MSBuild.exe" and "MSBuild.rsp"
2) the string "proj" that describes the extension we look for
3) all switch names and their short forms e.g. -property, or -p
4) all verbosity levels and their short forms e.g. quiet, or q
LOCALIZATION: None of the lines should be longer than a standard width console window, eg 80 chars.
</note>
</trans-unit>
<trans-unit id="HelpMessage_14_NoConsoleLoggerSwitch">
<source> -noConsoleLogger Disable the default console logger and do not log events
to the console. (Short form: -noConLog)
</source>
<target state="new"> -noConsoleLogger Disable the default console logger and do not log events
to the console. (Short form: -noConLog)
</target>
<note>
LOCALIZATION: The following should not be localized:
1) "MSBuild", "MSBuild.exe" and "MSBuild.rsp"
2) the string "proj" that describes the extension we look for
3) all switch names and their short forms e.g. -property, or -p
4) all verbosity levels and their short forms e.g. quiet, or q
LOCALIZATION: None of the lines should be longer than a standard width console window, eg 80 chars.
</note>
</trans-unit>
<trans-unit id="HelpMessage_15_ValidateSwitch">
<source> -validate Validate the project against the default schema. (Short
form: -val)
-validate:<schema> Validate the project against the specified schema. (Short
form: -val)
Example:
-validate:MyExtendedBuildSchema.xsd
</source>
<target state="new"> -validate Validate the project against the default schema. (Short
form: -val)
-validate:<schema> Validate the project against the specified schema. (Short
form: -val)
Example:
-validate:MyExtendedBuildSchema.xsd
</target>
<note>
LOCALIZATION: The following should not be localized:
1) "MSBuild", "MSBuild.exe" and "MSBuild.rsp"
2) the string "proj" that describes the extension we look for
3) all switch names and their short forms e.g. -property, or -p
4) all verbosity levels and their short forms e.g. quiet, or q
LOCALIZATION: None of the lines should be longer than a standard width console window, eg 80 chars.
</note>
</trans-unit>
<trans-unit id="HelpMessage_17_MaximumCPUSwitch">
<source> -maxCpuCount[:n] Specifies the maximum number of concurrent processes to
build with. If the switch is not used, the default
value used is 1. If the switch is used without a value
MSBuild will use up to the number of processors on the
computer. (Short form: -m[:n])
</source>
<target state="new"> -maxCpuCount[:n] Specifies the maximum number of concurrent processes to
build with. If the switch is not used, the default
value used is 1. If the switch is used without a value
MSBuild will use up to the number of processors on the
computer. (Short form: -m[:n])
</target>
<note>
LOCALIZATION: "maxCpuCount" should not be localized.
LOCALIZATION: None of the lines should be longer than a standard width console window, eg 80 chars.
</note>
</trans-unit>
<trans-unit id="HelpMessage_16_Examples">
<source>Examples:
MSBuild MyApp.sln -t:Rebuild -p:Configuration=Release
MSBuild MyApp.csproj -t:Clean
-p:Configuration=Debug;TargetFrameworkVersion=v3.5
</source>
<target state="new">Examples:
MSBuild MyApp.sln -t:Rebuild -p:Configuration=Release
MSBuild MyApp.csproj -t:Clean
-p:Configuration=Debug;TargetFrameworkVersion=v3.5
</target>
<note>
LOCALIZATION: The following should not be localized:
1) "MSBuild", "MSBuild.exe" and "MSBuild.rsp"
2) the string "proj" that describes the extension we look for
3) all switch names and their short forms e.g. -property, or -p
4) all verbosity levels and their short forms e.g. quiet, or q
LOCALIZATION: None of the lines should be longer than a standard width console window, eg 80 chars.
</note>
</trans-unit>
<trans-unit id="HelpPrompt">
<source>For switch syntax, type "MSBuild -help"</source>
<target state="new">For switch syntax, type "MSBuild -help"</target>
<note>UE: this message is shown when the user makes a syntax error on the command-line for a switch.
LOCALIZATION: "MSBuild -help" should not be localized.</note>
</trans-unit>
<trans-unit id="HelpMessage_18_DistributedLoggerSwitch">
<source> -distributedLogger:<central logger>*<forwarding logger>
Use this logger to log events from MSBuild, attaching a
different logger instance to each node. To specify
multiple loggers, specify each logger separately.
(Short form -dl)
The <logger> syntax is:
[<logger class>,]<logger assembly>[;<logger parameters>]
The <logger class> syntax is:
[<partial or full namespace>.]<logger class name>
The <logger assembly> syntax is:
{<assembly name>[,<strong name>] | <assembly file>}
The <logger parameters> are optional, and are passed
to the logger exactly as you typed them. (Short form: -l)
Examples:
-dl:XMLLogger,MyLogger,Version=1.0.2,Culture=neutral
-dl:MyLogger,C:\My.dll*ForwardingLogger,C:\Logger.dll
</source>
<target state="new"> -distributedLogger:<central logger>*<forwarding logger>
Use this logger to log events from MSBuild, attaching a
different logger instance to each node. To specify
multiple loggers, specify each logger separately.
(Short form -dl)
The <logger> syntax is:
[<logger class>,]<logger assembly>[;<logger parameters>]
The <logger class> syntax is:
[<partial or full namespace>.]<logger class name>
The <logger assembly> syntax is:
{<assembly name>[,<strong name>] | <assembly file>}
The <logger parameters> are optional, and are passed
to the logger exactly as you typed them. (Short form: -l)
Examples:
-dl:XMLLogger,MyLogger,Version=1.0.2,Culture=neutral
-dl:MyLogger,C:\My.dll*ForwardingLogger,C:\Logger.dll
</target>
<note>
LOCALIZATION: The following should not be localized:
1) "MSBuild", "MSBuild.exe" and "MSBuild.rsp"
2) the string "proj" that describes the extension we look for
3) all switch names and their short forms e.g. -property, or -p
4) all verbosity levels and their short forms e.g. quiet, or q
LOCALIZATION: None of the lines should be longer than a standard width console window, eg chars.
</note>
</trans-unit>
<trans-unit id="HelpMessage_19_IgnoreProjectExtensionsSwitch">
<source> -ignoreProjectExtensions:<extensions>
List of extensions to ignore when determining which
project file to build. Use a semicolon or a comma
to separate multiple extensions.
(Short form: -ignore)
Example:
-ignoreProjectExtensions:.sln
</source>
<target state="new"> -ignoreProjectExtensions:<extensions>
List of extensions to ignore when determining which
project file to build. Use a semicolon or a comma
to separate multiple extensions.
(Short form: -ignore)
Example:
-ignoreProjectExtensions:.sln
</target>
<note>
LOCALIZATION: The following should not be localized:
1) "MSBuild", "MSBuild.exe" and "MSBuild.rsp"
2) the string "proj" that describes the extension we look for
3) all switch names and their short forms e.g. -property, or -p
4) all verbosity levels and their short forms e.g. quiet, or q
LOCALIZATION: None of the lines should be longer than a standard width console window, eg 80 chars.
</note>
</trans-unit>
<trans-unit id="HelpMessage_23_ToolsVersionSwitch">
<source> -toolsVersion:<version>
The version of the MSBuild Toolset (tasks, targets, etc.)
to use during build. This version will override the
versions specified by individual projects. (Short form:
-tv)
Example:
-toolsVersion:3.5
</source>
<target state="new"> -toolsVersion:<version>
The version of the MSBuild Toolset (tasks, targets, etc.)
to use during build. This version will override the
versions specified by individual projects. (Short form:
-tv)
Example:
-toolsVersion:3.5
</target>
<note>
LOCALIZATION: The following should not be localized:
1) "MSBuild", "MSBuild.exe" and "MSBuild.rsp"
2) the string "proj" that describes the extension we look for
3) all switch names and their short forms e.g. -property, or -p
4) all verbosity levels and their short forms e.g. quiet, or q
LOCALIZATION: None of the lines should be longer than a standard width console window, eg 80 chars.
</note>
</trans-unit>
<trans-unit id="HelpMessage_20_FileLoggerSwitch">
<source> -fileLogger[n] Logs the build output to a file. By default
the file is in the current directory and named
"msbuild[n].log". Events from all nodes are combined into
a single log. The location of the file and other
parameters for the fileLogger can be specified through
the addition of the "-fileLoggerParameters[n]" switch.
"n" if present can be a digit from 1-9, allowing up to
10 file loggers to be attached. (Short form: -fl[n])
</source>
<target state="new"> -fileLogger[n] Logs the build output to a file. By default
the file is in the current directory and named
"msbuild[n].log". Events from all nodes are combined into
a single log. The location of the file and other
parameters for the fileLogger can be specified through
the addition of the "-fileLoggerParameters[n]" switch.
"n" if present can be a digit from 1-9, allowing up to
10 file loggers to be attached. (Short form: -fl[n])
</target>
<note>
LOCALIZATION: The following should not be localized:
1) "MSBuild", "MSBuild.exe" and "MSBuild.rsp"
2) the string "proj" that describes the extension we look for
3) all switch names and their short forms e.g. -property, or -p
4) all verbosity levels and their short forms e.g. quiet, or q
LOCALIZATION: None of the lines should be longer than a standard width console window, eg 80 chars.
</note>
</trans-unit>
<trans-unit id="HelpMessage_21_DistributedFileLoggerSwitch">
<source> -distributedFileLogger
Logs the build output to multiple log files, one log file
per MSBuild node. The initial location for these files is
the current directory. By default the files are called
"MSBuild<nodeid>.log". The location of the files and
other parameters for the fileLogger can be specified
with the addition of the "-fileLoggerParameters" switch.
If a log file name is set through the fileLoggerParameters
switch the distributed logger will use the fileName as a
template and append the node id to this fileName to
create a log file for each node.
</source>
<target state="new"> -distributedFileLogger
Logs the build output to multiple log files, one log file
per MSBuild node. The initial location for these files is
the current directory. By default the files are called
"MSBuild<nodeid>.log". The location of the files and
other parameters for the fileLogger can be specified
with the addition of the "-fileLoggerParameters" switch.
If a log file name is set through the fileLoggerParameters
switch the distributed logger will use the fileName as a
template and append the node id to this fileName to
create a log file for each node.
</target>
<note>
LOCALIZATION: The following should not be localized:
1) "MSBuild", "MSBuild.exe" and "MSBuild.rsp"
2) the string "proj" that describes the extension we look for
3) all switch names and their short forms e.g. -property, or -p
4) all verbosity levels and their short forms e.g. quiet, or q
LOCALIZATION: None of the lines should be longer than a standard width console window, eg 80 chars.
</note>
</trans-unit>
<trans-unit id="HelpMessage_22_FileLoggerParametersSwitch">
<source> -fileLoggerParameters[n]:<parameters>
Provides any extra parameters for file loggers.
The presence of this switch implies the
corresponding -fileLogger[n] switch.
"n" if present can be a digit from 1-9.
-fileLoggerParameters is also used by any distributed
file logger, see description of -distributedFileLogger.
(Short form: -flp[n])
The same parameters listed for the console logger are
available. Some additional available parameters are:
LogFile--path to the log file into which the
build log will be written.
Append--determines if the build log will be appended
to or overwrite the log file. Setting the
switch appends the build log to the log file;
Not setting the switch overwrites the
contents of an existing log file.
The default is not to append to the log file.
Encoding--specifies the encoding for the file,
for example, UTF-8, Unicode, or ASCII
Default verbosity is Detailed.
Examples:
-fileLoggerParameters:LogFile=MyLog.log;Append;
Verbosity=diagnostic;Encoding=UTF-8
-flp:Summary;Verbosity=minimal;LogFile=msbuild.sum
-flp1:warningsonly;logfile=msbuild.wrn
-flp2:errorsonly;logfile=msbuild.err
</source>
<target state="new"> -fileLoggerParameters[n]:<parameters>
Provides any extra parameters for file loggers.
The presence of this switch implies the
corresponding -fileLogger[n] switch.
"n" if present can be a digit from 1-9.
-fileLoggerParameters is also used by any distributed
file logger, see description of -distributedFileLogger.
(Short form: -flp[n])
The same parameters listed for the console logger are
available. Some additional available parameters are:
LogFile--path to the log file into which the
build log will be written.
Append--determines if the build log will be appended
to or overwrite the log file. Setting the
switch appends the build log to the log file;
Not setting the switch overwrites the
contents of an existing log file.
The default is not to append to the log file.
Encoding--specifies the encoding for the file,
for example, UTF-8, Unicode, or ASCII
Default verbosity is Detailed.
Examples:
-fileLoggerParameters:LogFile=MyLog.log;Append;
Verbosity=diagnostic;Encoding=UTF-8
-flp:Summary;Verbosity=minimal;LogFile=msbuild.sum
-flp1:warningsonly;logfile=msbuild.wrn
-flp2:errorsonly;logfile=msbuild.err
</target>
<note>
LOCALIZATION: The following should not be localized:
1) "MSBuild", "MSBuild.exe" and "MSBuild.rsp"
2) the string "proj" that describes the extension we look for
3) all switch names and their short forms e.g. -property, or -p
4) all verbosity levels and their short forms e.g. quiet, or q
LOCALIZATION: None of the lines should be longer than a standard width console window, eg 80 chars.
</note>
</trans-unit>
<trans-unit id="HelpMessage_24_NodeReuse">
<source> -nodeReuse:<parameters>
Enables or Disables the reuse of MSBuild nodes.
The parameters are:
True --Nodes will remain after the build completes
and will be reused by subsequent builds (default)
False--Nodes will not remain after the build completes
(Short form: -nr)
Example:
-nr:true
</source>
<target state="new"> -nodeReuse:<parameters>
Enables or Disables the reuse of MSBuild nodes.
The parameters are:
True --Nodes will remain after the build completes
and will be reused by subsequent builds (default)
False--Nodes will not remain after the build completes
(Short form: -nr)
Example:
-nr:true
</target>
<note />
</trans-unit>
<trans-unit id="HelpMessage_25_PreprocessSwitch">
<source> -preprocess[:file]
Creates a single, aggregated project file by
inlining all the files that would be imported during a
build, with their boundaries marked. This can be
useful for figuring out what files are being imported
and from where, and what they will contribute to
the build. By default the output is written to
the console window. If the path to an output file
is provided that will be used instead.
(Short form: -pp)
Example:
-pp:out.txt
</source>
<target state="new"> -preprocess[:file]
Creates a single, aggregated project file by
inlining all the files that would be imported during a
build, with their boundaries marked. This can be
useful for figuring out what files are being imported
and from where, and what they will contribute to
the build. By default the output is written to
the console window. If the path to an output file
is provided that will be used instead.
(Short form: -pp)
Example:
-pp:out.txt
</target>
<note />
</trans-unit>
<trans-unit id="HelpMessage_26_DetailedSummarySwitch">
<source> -detailedSummary
Shows detailed information at the end of the build
about the configurations built and how they were
scheduled to nodes.
(Short form: -ds)
</source>
<target state="new"> -detailedSummary
Shows detailed information at the end of the build
about the configurations built and how they were
scheduled to nodes.
(Short form: -ds)
</target>
<note />
</trans-unit>
<trans-unit id="HelpMessage_28_WarnAsErrorSwitch">
<source> -warnAsError[:code[;code2]]
List of warning codes to treats as errors. Use a semicolon
or a comma to separate multiple warning codes. To treat all
warnings as errors use the switch with no values.
(Short form: -err[:c;[c2]])
Example:
-warnAsError:MSB4130
When a warning is treated as an error the target will
continue to execute as if it was a warning but the overall
build will fail.
</source>
<target state="new"> -warnAsError[:code[;code2]]
List of warning codes to treats as errors. Use a semicolon
or a comma to separate multiple warning codes. To treat all
warnings as errors use the switch with no values.
(Short form: -err[:c;[c2]])
Example:
-warnAsError:MSB4130
When a warning is treated as an error the target will
continue to execute as if it was a warning but the overall
build will fail.
</target>
<note>
LOCALIZATION: "-warnAsError" and "-err" should not be localized.
LOCALIZATION: None of the lines should be longer than a standard width console window, eg 80 chars.
</note>
</trans-unit>
<trans-unit id="HelpMessage_29_WarnAsMessageSwitch">
<source> -warnAsMessage[:code[;code2]]
List of warning codes to treats as low importance
messages. Use a semicolon or a comma to separate
multiple warning codes.
(Short form: -noWarn[:c;[c2]])
Example:
-warnAsMessage:MSB3026
</source>
<target state="new"> -warnAsMessage[:code[;code2]]
List of warning codes to treats as low importance
messages. Use a semicolon or a comma to separate
multiple warning codes.
(Short form: -noWarn[:c;[c2]])
Example:
-warnAsMessage:MSB3026
</target>
<note>
LOCALIZATION: "-warnAsMessage" and "-noWarn" should not be localized.
LOCALIZATION: None of the lines should be longer than a standard width console window, eg 80 chars.
</note>
</trans-unit>
<trans-unit id="HelpMessage_30_BinaryLoggerSwitch">
<source> -binaryLogger[:[LogFile=]output.binlog[;ProjectImports={None,Embed,ZipFile}]]
Serializes all build events to a compressed binary file.
By default the file is in the current directory and named
"msbuild.binlog". The binary log is a detailed description
of the build process that can later be used to reconstruct
text logs and used by other analysis tools. A binary log
is usually 10-20x smaller than the most detailed text
diagnostic-level log, but it contains more information.
(Short form: -bl)
The binary logger by default collects the source text of
project files, including all imported projects and target
files encountered during the build. The optional
ProjectImports switch controls this behavior:
ProjectImports=None - Don't collect the project
imports.
ProjectImports=Embed - Embed project imports in the
log file.
ProjectImports=ZipFile - Save project files to
output.projectimports.zip
where output is the same name
as the binary log file name.
The default setting for ProjectImports is Embed.
Note: the logger does not collect non-MSBuild source files
such as .cs, .cpp etc.
A .binlog file can be "played back" by passing it to
msbuild.exe as an argument instead of a project/solution.
Other loggers will receive the information contained
in the log file as if the original build was happening.
You can read more about the binary log and its usages at:
https://github.com/Microsoft/msbuild/wiki/Binary-Log
Examples:
-bl
-bl:output.binlog
-bl:output.binlog;ProjectImports=None
-bl:output.binlog;ProjectImports=ZipFile
-bl:..\..\custom.binlog
-binaryLogger
</source>
<target state="new"> -binaryLogger[:[LogFile=]output.binlog[;ProjectImports={None,Embed,ZipFile}]]
Serializes all build events to a compressed binary file.
By default the file is in the current directory and named
"msbuild.binlog". The binary log is a detailed description
of the build process that can later be used to reconstruct
text logs and used by other analysis tools. A binary log
is usually 10-20x smaller than the most detailed text
diagnostic-level log, but it contains more information.
(Short form: -bl)
The binary logger by default collects the source text of
project files, including all imported projects and target
files encountered during the build. The optional
ProjectImports switch controls this behavior:
ProjectImports=None - Don't collect the project
imports.
ProjectImports=Embed - Embed project imports in the
log file.
ProjectImports=ZipFile - Save project files to
output.projectimports.zip
where output is the same name
as the binary log file name.
The default setting for ProjectImports is Embed.
Note: the logger does not collect non-MSBuild source files
such as .cs, .cpp etc.
A .binlog file can be "played back" by passing it to
msbuild.exe as an argument instead of a project/solution.
Other loggers will receive the information contained
in the log file as if the original build was happening.
You can read more about the binary log and its usages at:
https://github.com/Microsoft/msbuild/wiki/Binary-Log
Examples:
-bl
-bl:output.binlog
-bl:output.binlog;ProjectImports=None
-bl:output.binlog;ProjectImports=ZipFile
-bl:..\..\custom.binlog
-binaryLogger
</target>
<note>
LOCALIZATION: The following should not be localized:
1) "msbuild"
2) the string "binlog" that describes the file extension
3) all switch names and their short forms e.g. -bl and -binaryLogger
LOCALIZATION: None of the lines should be longer than a standard width console window, eg 80 chars.
</note>
</trans-unit>
<trans-unit id="HelpMessage_31_RestoreSwitch">
<source> -restore[:True|False]
Runs a target named Restore prior to building
other targets and ensures the build for these
targets uses the latest restored build logic.
This is useful when your project tree requires
packages to be restored before it can be built.
Specifying -restore is the same as specifying
-restore:True. Use the parameter to override
a value that comes from a response file.
(Short form: -r)
</source>
<target state="new"> -restore[:True|False]
Runs a target named Restore prior to building
other targets and ensures the build for these
targets uses the latest restored build logic.
This is useful when your project tree requires
packages to be restored before it can be built.
Specifying -restore is the same as specifying
-restore:True. Use the parameter to override
a value that comes from a response file.
(Short form: -r)
</target>
<note>
LOCALIZATION: "-restore" and "-r" should not be localized.
LOCALIZATION: None of the lines should be longer than a standard width console window, eg 80 chars.
</note>
</trans-unit>
<trans-unit id="InvalidConfigurationFile">
<source>MSBUILD : Configuration error MSB1043: The application could not start. {0}</source>
<target state="new">MSBUILD : Configuration error MSB1043: The application could not start. {0}</target>
<note>
{StrBegin="MSBUILD : Configuration error MSB1043: "}
UE: This error is shown when the msbuild.exe.config file had invalid content.
LOCALIZATION: The prefix "MSBUILD : Configuration error MSBxxxx:" should not be localized.