This repository was archived by the owner on Jul 16, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathbuild.settings.props
1107 lines (1002 loc) · 47.1 KB
/
build.settings.props
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"?>
<Project
DefaultTargets="Run"
ToolsVersion="14.0"
xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
<!-- Overrides for the build configuration -->
<PropertyGroup>
<!-- A flag that indicates whether or not the build output of the VS projects is redirected to the $(DirBuildBinPlatformConfig) directory. -->
<!-- <RedirectBuildOutputToSingleFolder>false</RedirectBuildOutputToSingleFolder> -->
<!-- The build configuration (debug / release / ...) that will be used to run all the unit tests and the static verification on -->
<TestConfiguration>Release</TestConfiguration>
<!-- The build configuration (debug / release / ..) that will be used to create the binaries that should be deployed -->
<ProductionConfiguration>Deploy</ProductionConfiguration>
<!-- The platform for which the binaries will be build -->
<!-- <Platform>Any CPU</Platform> -->
<!-- <PlatformWithoutSpaces>$(Platform.Replace(" ",""))</PlatformWithoutSpaces> -->
</PropertyGroup>
<!--
**** BUILD STEPS ****
-->
<PropertyGroup>
<!-- Indicate if an error in the pre-step actions should fail the build -->
<!-- <FailBuildOnPreStepFailure>false</FailBuildOnPreStepFailure> -->
<!-- Indicate if an error in the post-step actions should fail the build -->
<!-- <FailBuildOnPostStepFailure>false</FailBuildOnPostStepFailure> -->
<!-- Indicate if an error in the pre-step actions should immediately stop the build -->
<!-- <StopBuildOnPreStepFailure>false</StopBuildOnPreStepFailure> -->
<!-- Indicate if an error in the post-step actions should immediately stop the build -->
<!-- <StopBuildOnPostStepFailure>false</StopBuildOnPostStepFailure> -->
</PropertyGroup>
<!--
A list of all additional scripts and their targets that should be executed before each of the selected build steps. Globally defined
pre-steps will be executed prior to the presteps of the individual steps.
The metadata to the script that is about to be executed is passed to each pre-step under the following properties:
- StepDescription : The full description of the step to be executed.
- StepId : The ID of the step. In general the name of the property that references the step file.
- StepName : The name of the step.
- StepPath : The full path to the script file for the step.
Additionally all the standard properties as seen below and the properties for the given build step are passed in.
-->
<ItemGroup>
<!--
<BuildPreStepsToExecute Include="">
<Properties>
</Properties>
</BuildPreStepsToExecute>
-->
</ItemGroup>
<!--
A list of all additional scripts and their targets that should be executed after each of the selected build steps. Globally defined
post-steps will be executed after the poststeps of the individual steps.
The metadata to the script that is about to be executed is passed to each pre-step under the following properties:
- StepDescription : The full description of the step to be executed.
- StepId : The ID of the step. In general the name of the property that references the step file.
- StepName : The name of the step.
- StepPath : The full path to the script file for the step.
Additionally all the standard properties as seen below and the properties for the given build step are passed in.
-->
<ItemGroup>
<!--
<BuildPostStepsToExecute Include="">
<Properties>
</Properties>
</BuildPostStepsToExecute>
-->
</ItemGroup>
<!--
The following ItemGroup defines which steps are taken during the build process. The order of the items in the item group
determines in which order the build steps are executed.
Each build step can define the following items:
- Properties - The semi-colon separated set of properties that should be passed to the script.
Properties are written as 'key=value'.
- Groups - All the groups that a given step belongs to. The user can elect to only run build steps for a given group.
- PreSteps - A semi-colon separated list of all additional scripts and their targets that should be executed before
the selected build step.
- PostSteps - A semi-colon separated list of all additional scripts and their targets that should be executed after
the selected build step.
The metadata to the script that is about to be executed is passed to each pre-step under the following properties:
- StepDescription : The full description of the step to be executed.
- StepId : The ID of the step. In general the name of the property that references the step file.
- StepName : The name of the step.
- StepPath : The full path to the script file for the step.
Additionally all the standard properties as seen below and the properties for the given build step are passed in.
The following build steps are by default provided through the given properties:
$(BuildStepsPrepareWorkspace) - Clears the existing build artifacts from the workspace and creates the required directories. Clearing the
existing build artifacts is only executed if the $(ShouldClean) property is set to 'true'.
$(BuildStepsBuildTargetsAssembly) - Builds Visual Studio projects that contain MsBuild Tasks. Separate from building the standard Visual Studio
solutions so that it is possible to build MsBuild tasks that will be used in the build process.
$(BuildStepsGenerateTargetsFile) - Generates a targets file for use with an MsBuild tasks assembly.
$(BuildStepsPrepareRestoreNuGet) - Restores the NuGet packages as specified in the '$(DirWorkspace)\packages.config' file. Additionally
also restores the NuGet packages as specified in the nBuildKit specific 'packages.config' files.
$(BuildStepsPrepareVcsBranch) - When building from a GIT repository on Jenkins ensures that the current checkout has the same branch
name as the remote tracking branch.
$(BuildStepsPrepareVcsInfo) - Stores the Version Control System (VCS) information in a file for later use.
Currently supported version control systems is GIT
$(BuildStepsPrepareGetIssueIds) - Gets the issue IDs from the commits on the current branch and stores them in a temp file for later use.
$(BuildStepsPrepareVcsMerge) - Merges the current changes to the designated target branches (specified by @(BranchMergeTarget)).
$(BuildStepsPrepareGetVersion) - Gathers version information and stores it in a temporary file for use by the rest of the build process.
Currently supported methods of gathering version information are using (in order):
- The version defined by a custom MsBuild task which is defined in a file of which the path is stored
in the 'VersionScriptPath' property. The task should output:
- VersionMajor
- VersionMinor
- VersionPatch
- VersionBuild
- VersionPreRelease
- VersionSemantic
- VersionSemanticFull
- VersionSemanticNuget
- The version stored in an 'version.xml' file which contains an MsBuild property group with
the properties:
- BuildNumber
- VersionMajor
- VersionMinor
- VersionPatch
- VersionBuild
- VersionPreRelease
- The GitVersion tool (https://github.com/ParticularLabs/GitVersion)
- The GitHubFlowVersion tool (https://github.com/JakeGinnivan/GitHubFlowVersion)
$(BuildStepsPrepareTagVcs) - Tags the current commit with the version number. Currently supported version control systems are TFS and GIT.
$(BuildStepsPrepareReleaseNotes) - Gathers the release notes and stores them for later use during the build process. Release notes
are retrieved with the GitReleaseNotes tool (https://github.com/GitTools/GitReleaseNotes) which
currently allows gathering release notes from GitHub, Jira and YouTrack
$(BuildStepsPrepareRestoreNpm) - Restores all the NPM packages for the project.
$(BuildStepsPrepareRestoreBower) - Restores all the Bower packages for the project.
$(BuildStepsPrepareCopyNuGet) - Copies one or more files from a NuGet package.
$(BuildStepsPrepareCopyFiles) - Copies one or more files from the file system.
$(BuildStepsPrepareAssemblyInfo) - Updates all existing AssemblyInfo.cs and AssemblyInfo.vb files with the version numbers, company information,
copyright information and optionally build time and build information.
$(BuildStepsPrepareGenerateFiles) - Generates one or more files from a set of template files.
$(BuildStepsPrepareGenerateLicenses) - Generates an XML file containing the licenses for all the NuGet packages in use for the current build.
$(BuildStepsAnalyzeSourceCcm) - Analyzes the source code files with CCM.
$(BuildStepsAnalyzeSourceSouceMonitor) - Analyzes the source code files with SourceMonitor.
$(BuildStepsBuildVisualStudioSolution) - Builds the binaries from a given Visual Studio solution.
$(BuildStepsUnitTestNUnit) - Executes the unit tests with NUnit and measures code coverage with OpenCover.
$(BuildStepsUnitTestMsTest) - Executes the unit tests with MsTest and measures code coverage with OpenCover.
$(BuildStepsUnitTestVsTest) - Executes the unit tests with VsTest and measures code coverage.
$(BuildStepsAnalyzeXml) - Analyzes one or more XML files based on the provided XSD.
$(BuildStepsAnalyzeBinariesFxCop) - Analyzes the binary files with FxCop.
$(BuildStepsBuildILMerge) - Performs one or more IL merge operations.
$(BuildStepsBuildWyam) - Builds the documentation in the `doc` folder with Wyam.
$(BuildStepsPackNuGet) - Generates the NuGet packages.
$(BuildStepsPackZip) - Generates one or more ZIP archives.
Additional build steps can be defined by providing the path to the MsBuild script that should be executed
for that step, e.g. adding a build step that points to the 'c:\stuff\MyCoolScript.msbuild' will execute
that script.
Any properties defined by the 'Properties' section are pushed up.
Custom build steps may chose to add metadata to the 'AvailableStepMetadata' ItemGroup. This ItemGroup contains metadata describing
all known steps.
-->
<ItemGroup>
<BuildStepsToExecute Include="$(BuildStepsPrepareWorkspace)">
<Properties>
</Properties>
<Groups>
clean;
prepare;
prepare.clean;
</Groups>
<PreSteps>
</PreSteps>
<PostSteps>
</PostSteps>
</BuildStepsToExecute>
<!--
<BuildStepsToExecute Include="$(BuildStepsBuildTargetsAssembly)">
<Properties>
</Properties>
<Groups>
prepare;
prepare.bootstrap;
</Groups>
<PreSteps>
</PreSteps>
<PostSteps>
</PostSteps>
</BuildStepsToExecute>
<BuildStepsToExecute Include="$(BuildStepsGenerateTargetsFile)">
<Properties>
</Properties>
<Groups>
prepare;
prepare.bootstrap;
</Groups>
<PreSteps>
</PreSteps>
<PostSteps>
</PostSteps>
</BuildStepsToExecute>
-->
<BuildStepsToExecute Include="$(BuildStepsPrepareRestoreNuGet)">
<Properties>
</Properties>
<Groups>
prepare;
prepare.restore;
prepare.restore.nuget;
</Groups>
<PreSteps>
</PreSteps>
<PostSteps>
</PostSteps>
</BuildStepsToExecute>
<!--
The following steps need to be executed on the original branch (i.e. the branch we are interested in
building.
-->
<BuildStepsToExecute Include="$(BuildStepsPrepareVcsBranch)">
<Properties>
</Properties>
<Groups>
prepare;
prepare.buildserver;
prepare.buildserver.vcssetbranch;
prepare.vcs;
prepare.vcs.vcssetbranch;
</Groups>
<PreSteps>
</PreSteps>
<PostSteps>
</PostSteps>
</BuildStepsToExecute>
<BuildStepsToExecute Include="$(BuildStepsPrepareVcsInfo)">
<Properties>
</Properties>
<Groups>
prepare;
prepare.get;
prepare.get.vcsinfo;
</Groups>
<PreSteps>
</PreSteps>
<PostSteps>
</PostSteps>
</BuildStepsToExecute>
<BuildStepsToExecute Include="$(BuildStepsPrepareGetIssueIds)">
<Properties>
</Properties>
<Groups>
prepare;
prepare.get;
prepare.get.issueids;
</Groups>
<PreSteps>
</PreSteps>
<PostSteps>
</PostSteps>
</BuildStepsToExecute>
<!--
This step potentially changes the local branch we are building. If one or more merge targets have been
specified then this step will merge to all merge targets and leave the current branch as the last branch
we merged to.
-->
<BuildStepsToExecute Include="$(BuildStepsPrepareVcsMerge)">
<Properties>
</Properties>
<Groups>
prepare;
prepare.buildserver;
prepare.buildserver.merge;
prepare.vcs;
prepare.vcs.merge;
</Groups>
<PreSteps>
</PreSteps>
<PostSteps>
</PostSteps>
</BuildStepsToExecute>
<!--
All steps from here on may be executed on a different branch than the orginal branch we we started the
build on because we might have done some merging.
-->
<BuildStepsToExecute Include="$(BuildStepsPrepareGetVersion)">
<Properties>
</Properties>
<Groups>
prepare;
prepare.get;
prepare.get.version;
</Groups>
<PreSteps>
</PreSteps>
<PostSteps>
</PostSteps>
</BuildStepsToExecute>
<BuildStepsToExecute
Condition=" '$(IsGitFlow)' == 'true' AND ('$(IsReleaseBranch)' == 'true' OR '$(IsHotfixBranch)' == 'true') "
Include="$(BuildStepsPrepareTagVcs)">
<Properties>
</Properties>
<Groups>
prepare;
prepare.buildserver;
prepare.buildserver.tag;
prepare.vcs;
prepare.vcs.tag;
</Groups>
<PreSteps>
</PreSteps>
<PostSteps>
</PostSteps>
</BuildStepsToExecute>
<BuildStepsToExecute Include="$(BuildStepsPrepareReleaseNotes)">
<Properties>
</Properties>
<Groups>
prepare;
prepare.get;
prepare.get.releasenotes;
</Groups>
<PreSteps>
</PreSteps>
<PostSteps>
</PostSteps>
</BuildStepsToExecute>
<!--
<BuildStepsToExecute Include="$(BuildStepsPrepareRestoreNpm)">
<Properties>
</Properties>
<Groups>
prepare;
prepare.restore;
prepare.restore.npm;
</Groups>
<PreSteps>
</PreSteps>
<PostSteps>
</PostSteps>
</BuildStepsToExecute>
<BuildStepsToExecute Include="$(BuildStepsPrepareRestoreBower)">
<Properties>
</Properties>
<Groups>
prepare;
prepare.restore;
prepare.restore.bower;
</Groups>
<PreSteps>
</PreSteps>
<PostSteps>
</PostSteps>
</BuildStepsToExecute>
-->
<BuildStepsToExecute Include="$(BuildStepsPrepareCopyNuGet)">
<Properties>
</Properties>
<Groups>
prepare;
prepare.copy;
prepare.copy.nuget;
</Groups>
<PreSteps>
</PreSteps>
<PostSteps>
</PostSteps>
</BuildStepsToExecute>
<BuildStepsToExecute Include="$(BuildStepsPrepareCopyFiles)">
<Properties>
</Properties>
<Groups>
prepare;
prepare.copy;
prepare.copy.files;
</Groups>
<PreSteps>
</PreSteps>
<PostSteps>
</PostSteps>
</BuildStepsToExecute>
<BuildStepsToExecute Include="$(BuildStepsPrepareAssemblyInfo)">
<Properties>
</Properties>
<Groups>
prepare;
prepare.generate;
prepare.generate.assemblyinfo;
</Groups>
<PreSteps>
</PreSteps>
<PostSteps>
</PostSteps>
</BuildStepsToExecute>
<!--
<BuildStepsToExecute Include="$(BuildStepsPrepareGenerateLicenses)">
<Properties>
</Properties>
<Groups>
prepare;
prepare.generate;
prepare.generate.licenses;
</Groups>
<PreSteps>
</PreSteps>
<PostSteps>
</PostSteps>
</BuildStepsToExecute>
-->
<BuildStepsToExecute Include="$(BuildStepsPrepareGenerateFiles)">
<Properties>
</Properties>
<Groups>
prepare;
prepare.generate;
prepare.generate.files;
</Groups>
<PreSteps>
</PreSteps>
<PostSteps>
</PostSteps>
</BuildStepsToExecute>
<BuildStepsToExecute Include="$(BuildStepsBuildVisualStudioSolution)">
<Properties>
</Properties>
<Groups>
build;
build.visualstudio;
</Groups>
<PreSteps>
</PreSteps>
<PostSteps>
</PostSteps>
</BuildStepsToExecute>
<BuildStepsToExecute Include="$(BuildStepsUnitTestNUnit)">
<Properties>
Configuration=$(TestConfiguration);
Platform=$(Platform)
</Properties>
<Groups>
test;
test.unittest;
test.unittest.nunit;
</Groups>
<PreSteps>
</PreSteps>
<PostSteps>
</PostSteps>
</BuildStepsToExecute>
<!--
<BuildStepsToExecute Include="$(BuildStepsUnitTestMsTest)">
<Properties>
Configuration=$(TestConfiguration);
Platform=$(Platform)
</Properties>
<Groups>
test;
test.unittest;
test.unittest.mstest;
</Groups>
<PreSteps>
</PreSteps>
<PostSteps>
</PostSteps>
</BuildStepsToExecute>
<BuildStepsToExecute Include="$(BuildStepsUnitTestVsTest)">
<Properties>
Configuration=$(TestConfiguration);
Platform=$(Platform)
</Properties>
<Groups>
test;
test.unittest;
test.unittest.vstest;
</Groups>
<PreSteps>
</PreSteps>
<PostSteps>
</PostSteps>
</BuildStepsToExecute>
-->
<!--
<BuildStepsToExecute Include="$(BuildStepsAnalyzeXml)">
<Properties>
Configuration=$(TestConfiguration);
Platform=$(Platform)
</Properties>
<Groups>
test;
test.analyze;
test.analyze.xml;
</Groups>
<PreSteps>
</PreSteps>
<PostSteps>
</PostSteps>
</BuildStepsToExecute>
-->
<BuildStepsToExecute Include="$(BuildStepsAnalyzeBinariesFxCop)">
<Properties>
Configuration=$(TestConfiguration);
Platform=$(Platform)
</Properties>
<Groups>
test;
test.analyze;
test.analyze.fxcop;
</Groups>
<PreSteps>
</PreSteps>
<PostSteps>
</PostSteps>
</BuildStepsToExecute>
<!--
<BuildStepsToExecute Include="$(BuildStepsBuildILMerge)">
<Properties>
Configuration=$(ProductionConfiguration);
Platform=$(Platform)
</Properties>
<Groups>
build;
build.ilmerge;
</Groups>
<PreSteps>
</PreSteps>
<PostSteps>
</PostSteps>
</BuildStepsToExecute>
-->
<BuildStepsToExecute Include="$(BuildStepsBuildWyam)">
<Properties>
Configuration=$(ProductionConfiguration);
Platform=$(Platform)
</Properties>
<Groups>
build;
build.doc;
build.doc.wyam;
</Groups>
<PreSteps>
</PreSteps>
<PostSteps>
</PostSteps>
</BuildStepsToExecute>
<BuildStepsToExecute Include="$(BuildStepsPackNuGet)">
<Properties>
Configuration=$(ProductionConfiguration);
Platform=$(Platform)
</Properties>
<Groups>
package;
package.nuget;
</Groups>
<PreSteps>
</PreSteps>
<PostSteps>
</PostSteps>
</BuildStepsToExecute>
<BuildStepsToExecute Include="$(BuildStepsPackZip)">
<Properties>
Configuration=$(ProductionConfiguration);
Platform=$(Platform)
</Properties>
<Groups>
package;
package.zip;
</Groups>
<PreSteps>
</PreSteps>
<PostSteps>
</PostSteps>
</BuildStepsToExecute>
</ItemGroup>
<!--
Define the scripts that should be executed when any one of the build steps fails.
Steps can be defined by providing the path to the MsBuild script that should be executed
for that step, e.g. adding a build step that points to the 'c:\stuff\MyCoolScript.msbuild' will execute
that script.
Any properties defined by the 'Properties' section are pushed up.
-->
<ItemGroup>
<!--
<BuildFailureStepsToExecute Include="">
<Properties>
</Properties>
<Groups>
</Groups>
</BuildFailureStepsToExecute>
-->
</ItemGroup>
<!--
The following item group stores metadata describing the custom build steps that are executed in the build process.
By providing this metadata it is possible for pre- and post-step actions to more clearly determine which step
they were attached to.
-->
<ItemGroup>
<!--
<AvailableStepMetadata Include="$([System.IO.Path]::GetFileName('$(DirWorkspace)\my.build.step.msbuild'))">
<Description>
The description for my cool build step
</Description>
<Id></Id>
<Name>My build step</Name>
<Path>$(DirWorkspace)\my.build.step.msbuild</Path>
</AvailableStepMetadata>
-->
</ItemGroup>
<!--
**** PREPARE - WORKSPACE ****
-->
<!--
The list of all files that should be deleted prior to starting the build process.
If the deletion process fails the build will continue and a warning will be printed.
-->
<ItemGroup>
<!--
<FilesToDelete Include="" />
-->
</ItemGroup>
<!--
The list of all directories that should be deleted prior to starting the build process.
Deleting the directories will also delete all the files contained in these directories.
If the deletion process fails the build will continue and a warning will be printed.
-->
<ItemGroup>
<!--
<DirectoriesToDelete Include="" />
-->
</ItemGroup>
<!--
**** PREPARE - COPY FILES ****
-->
<!--
Files that should be copied, either from the file system or from a NuGet package.
-->
<ItemGroup>
<!--
<FilesToCopy Include="">
<Destination></Destination>
</FilesToCopy>
-->
</ItemGroup>
<ItemGroup>
<!--
<NuGetFilesToCopy Include="My.Cool.NuGet.Package">
<Include>**/*.*</Include>
<Destinations>$(DirBuildTemp)</Destinations>
</NuGetFilesToCopy>
-->
</ItemGroup>
<!--
**** PREPARE - UPDATE ASSEMBLY INFO FILES ****
-->
<!--
The list of all assembly info files that should be updated with version and copyright information.
For additional information see the ShouldGenerateAssemblyXXXX properties below.
-->
<ItemGroup>
<!--
<AssemblyInfoFilesToUpdate
Condition=" '$(DirSrc)' != '' "
Include="$(DirSrc)\**\AssemblyInfo.cs" />
<AssemblyInfoFilesToUpdate
Condition=" '$(DirSrc)' != '' "
Include="$(DirSrc)\**\AssemblyInfo.vb" />
-->
</ItemGroup>
<!--
**** PREPARE - GENERATE FILES ****
-->
<!--
The list of all files that should be generated and their template files.
The template file may contain zero or more template parameters as indicated at the top of this
file. By default template parameters must be enclosed in '${}'. By providing a value for
'Expression' it is possible to use a custom regular expression to search for elements to replace,
e.g. $TOKEN$. Note that elements in the regular expession might need to be converted in a suitable
format because XML doesn't like < and > and MsBuild doesn't like $ (%24), * (%2A), ? (%3F).
Only the 'Template' value is required.
Additional parameters can be provided through the 'TemplateTokens' ItemGroup below.
-->
<ItemGroup>
<!--
<BuildFilesToGenerate
Include="$(DirDoc)\Nuclei.Diagnostics.Documentation\docfx.json">
<Template>$(DirDoc)\Nuclei.Diagnostics.Documentation\template.docfx.json</Template>
<Encoding>UTF-8</Encoding>
</BuildFilesToGenerate>
-->
</ItemGroup>
<!--
**** VISUAL STUDIO BUILD ****
-->
<!--
The item group defining the location of the Vistual Studio solutions that should be build.
The solution path allows build templates, e.g. '$(DirSrc)\${CompanyName}\${ProductName}\MySolution.sln'
-->
<ItemGroup>
<SolutionsToBuild
Condition=" '$(DirSrc)' != '' AND '$(TestConfiguration)' != '$(ProductionConfiguration)' "
Include="$(DirSrc)\*.sln">
<Configuration>$(TestConfiguration)</Configuration>
<Platform>$(Platform)</Platform>
<Targets>Rebuild</Targets>
<Properties>
ShouldPerformCodeAnalysis=false;
</Properties>
</SolutionsToBuild>
<SolutionsToBuild
Condition=" '$(DirSrc)' != '' "
Include="$(DirSrc)\*.sln">
<Configuration>$(ProductionConfiguration)</Configuration>
<Platform>$(Platform)</Platform>
<Targets>Rebuild</Targets>
<Properties>
ShouldPerformCodeAnalysis=false;
</Properties>
</SolutionsToBuild>
</ItemGroup>
<PropertyGroup>
<!--
A flag that indicates whether an AssemblyInfo file with the company and copyright information should be generated.
The file will be placed in the Properties directory of the Visual Studio project and will be named
AssemblyInfo.Company.xx (cs/vb). This file will contain:
- The AssemblyCompanyAttribute with the company name
- The AssemblyCopyrightAttribute with the text provided by the ${CopyrightLong} template parameter.
-->
<ShouldGenerateAssemblyCompanyInfo>true</ShouldGenerateAssemblyCompanyInfo>
<!--
A flag that indicates whether an AssemblyInfo file with the version numbers should be generated. The file
will be placed in the Properties directory of the Visual Studio project and will be named
AssemblyInfo.Version.xx (cs/vb). This file will contain:
- The AssemblyVersionAttribute with the version as provided by the ${VersionAssembly} template parameter.
- The AssemblyFileVersionAttribute with the version as provided by the ${VersionAssemblyFile} template parameter.
- The AssemblyInformationalVersionAttribute with the version as provided by the ${VersionProduct} template parameter.
Also indicates that a VersionNumber.wxi should be generated. This file will be placed
in the project folder of the Visual Studio project. This file will contain:
- The ApplicationVersion property with the version as provided by the ${VersionProduct} template parameter.
- The InstallVersion property with the version as provided by the ${VersionInstall} template parameter.
- The ProductVersionFolder property with the version as provided by the ${VersionInstallFilePath} template parameter.
-->
<ShouldGenerateAssemblyVersionInfo>true</ShouldGenerateAssemblyVersionInfo>
<!--
A flag that indicates whether an AssemblyInfo file with the build information should be generated. The file
will be placed in the Properties directory of the Visual Studio project and will be named
AssemblyInfo.BuildInformation.xx (cs/vb). This file will contain
- The AssemblyConfigurationAttribute containing the configuration of the build, e.g. Debug
- The AssemblyBuildTimeAttribute containing the complete date and time that the file was generated (which
should be close enough to the time the assembly was build).
- The assemblyBuildInformationAttribute which contains the build number and VCS revision number.
Note for this file to compile successfully a reference to the Nuclei.Build assembly needs to be added.
This assembly can be found on NuGet.org (http://www.nuget.org/packages/Nuclei.Build/)
-->
<ShouldGenerateAssemblyBuildInfo>true</ShouldGenerateAssemblyBuildInfo>
</PropertyGroup>
<!--
The ItemGroup defining the information for the generation of the InternalsVisibleAttribute.
Three different ways of referencing the test projects public key are available. Test assemblies
can be referenced by:
- Providing the snk key that was / is used to sign the test assembly. This is mainly of use
for test assemblies which are compiled at the same time as the target assemblies, i.e. test
assemblies that are part of the same Visual Studio solution.
- Providing the signed test assembly. This is mainly of use for test assemblies that have been
compiled prior to compiling the target assemblies, e.g. third party test assemblies.
- Providing the full public key for the assembly. This is mainly of use for assemblies that
do not exists on disk, e.g. assemblies that are dynamically generated.
Multiple projects can be referenced in the 'projects' section by separating them with a semi-colon (;). Whitespace
can be added if required but it has no influence on the project list.
If the assemblies are not signed it is possible to leave out the signing information, e.g. the 'KeyFile'
property, the 'AssemblyFromPackage' property and the 'PublicKey' property.
-->
<PropertyGroup>
<!--
Defines the compiler constants for which the InternalsVisibleTo attributes should
be generated.
Separate multiple compiler constants with semi-colons.
-->
<!-- <InternalsVisibletoCompilerConstants>INTERNALS_VISIBLE_TO</InternalsVisibletoCompilerConstants> -->
</PropertyGroup>
<ItemGroup>
<InternalsVisibleTo Include="Test.Unit.Nuclei.Diagnostics">
<Projects>
Nuclei.Diagnostics;
</Projects>
<KeyFile>$(SOFTWARE_SIGNING_KEY_PATH)\nuclei.snk</KeyFile>
</InternalsVisibleTo>
<InternalsVisibleTo Include="Moq">
<Projects>
Nuclei.Diagnostics;
</Projects>
<AssemblyFromPackage>Moq.dll</AssemblyFromPackage>
</InternalsVisibleTo>
<InternalsVisibleTo Include="DynamicProxyGenAssembly2">
<Projects>
Nuclei.Diagnostics;
</Projects>
<PublicKey>0024000004800000940000000602000000240000525341310004000001000100c547cac37abd99c8db225ef2f6c8a3602f3b3606cc9891605d02baa56104f4cfc0734aa39b93bf7852f7d9266654753cc297e7d2edfe0bac1cdcf9f717241550e0a7b191195b7667bb4f64bcb8e2121380fd1d9d46ad2d92d2d15605093924cceaf74c4861eff62abf69b9291ed0a340e113be11e6a7d3113e92484cf7045cc7</PublicKey>
</InternalsVisibleTo>
</ItemGroup>
<!-- Build configuration -->
<PropertyGroup>
<!--
The version of the .NET framework at which the assemblies should be targeted. This value is set
for all projects that include the MsBuild.Projects.XXXX NuGet package.
-->
<TargetFrameworkVersion>v4.5</TargetFrameworkVersion>
</PropertyGroup>
<!--
**** UNIT TESTS ****
-->
<PropertyGroup>
<!--
The assembly name prefix for the assemblies containing the unit tests. Allows build templates,
e.g. '${CompanyName}.${ProductName}.Tests'.
-->
<!--<UnitTestAssemblyNamePrefix>Test.Unit</UnitTestAssemblyNamePrefix>-->
<!--
The full path to the location where the MsTest report file should be created. This path can include build templates,
e.g. $(DirBuildLogs)\${CompanyName}\${ProductName}\mytest.trx.
-->
<!--<FileReportMsTest>$(DirBuildLogs)\mstest.trx</FileReportMsTest>-->
<!--
The full path to the directory where the VsTest report files should be created. This path can include build templates,
e.g. $(DirBuildLogs)\${CompanyName}\${ProductName}.
-->
<!--<DirReportVsTest>$(DirBuildLogs)\vstest</DirReportVsTest>-->
<!--
The full path to the XML report file that is generated by OpenCover upon completion of the unit test execution.
Allows build templates, e.g. $(DirBuildLogs)\${CompanyName}\${ProductName}\opencover.xml.
-->
<!--<FileReportOpenCoverXml>$(DirBuildLogs)\opencover.xml</FileReportOpenCoverXml>-->
<!--
The full path to the CSV report file that is generated by OpenCover upon completion of the unit test execution.
Allows build templates. , e.g. $(DirBuildLogs)\${CompanyName}\${ProductName}\coverage.csv.
-->
<!--<FileReportOpenCoverCsv>$(DirBuildLogs)\coverage.csv</FileReportOpenCoverCsv>-->
<!--
The full path to the Cobertura report directory which will contain the cobertura report files which are generated
by converting the OpenCover results to Cobertura.
Allows build templates, e.g. $(DirBuildLogs)\${CompanyName}\${ProductName}
-->
<!-- <DirReportOpenCoverCobertura>$(DirBuildLogs)</DirReportOpenCoverCobertura> -->
</PropertyGroup>
<ItemGroup>
<!--
The ItemGroup items that define which files contain the unit test cases. Paths can include build templates,
e.g. $(DirBuildBinPlatformConfig)\${VersionMajor}.0\**\test*.dll
-->
<!--
<UnitTestAssemblies
Condition=" '$(DirSrc)' != '' "
Include="$(DirSrc)\**\bin\$(Configuration)\**\$(UnitTestAssemblyNamePrefix)*.dll" />
-->
</ItemGroup>
<ItemGroup>
<!--
The ItemGroup items that define the attributes that indicate code that should be ignored by OpenCover.
-->
<!--<OpenCoverIgnoreAttributes Include="System.Diagnostics.CodeAnalysis.ExcludeFromCodeCoverageAttribute" />-->
<!--<OpenCoverIgnoreAttributes Include="System.Runtime.CompilerServices.CompilerGeneratedAttribute" />-->
</ItemGroup>
<ItemGroup>
<!--
The ItemGroup items that define the filters used by OpenCover.
NOTE: Use the hexadecimal value for * (%2A) to avoid MsBuild trying to make sense out of the text.
-->
<!--<OpenCoverFilters Include="+[$(ProductNamespace)]%2A" />-->
<!--<OpenCoverFilters Include="+[$(ProductNamespace).%2A]%2A" />-->
<!--<OpenCoverFilters Include="-[%2A$(UnitTestAssemblyNamePrefix)%2A]%2A" />-->
<!--<OpenCoverFilters Include="-[NUnit]%2A" />-->
<!--<OpenCoverFilters Include="-[NUnit.%2A]%2A" />-->
</ItemGroup>
<!--
**** SOURCE ANALYSIS - XML ****
-->
<ItemGroup>
<!--
The paths to the XML files that should be validated against the given schema.
-->
<!--
<XmlFilesToValidate
Condition=" '$(DirSrc)' != '' "
Exclude="$(DirSrc)\**\ignore.xml"
Include="$(DirSrc)\**\*.xml">
<SchemaFile></SchemaFile>
<TargetNamespace></TargetNamespace>
</XmlFilesToValidate>
-->
</ItemGroup>
<!--
**** BINARY ANALYSIS - FXCOP ****
-->
<PropertyGroup>
<!--
The full path to the FxCop project file.
-->
<!--<FileProjectFxCop>UNDEFINED</FileProjectFxCop>-->
<!--
The full path to the FxCop output report. Allows build templates, e.g. $(DirBuildLogs)\${ProductName}_fxcop.xml.
-->
<!--<FileReportFxCop Condition=" '$(FileReportFxCop)' == '' ">$(DirBuildLogs)\fxcop.xml</FileReportFxCop>-->
<!--
The full path to the rules file that indicates which rules FxCop should use to analyse the binaries.
-->
<FileFxCopRuleSet Condition=" '$(FileFxCopRuleSet)' == '' ">$(DirSrc)\default.ruleset</FileFxCopRuleSet>
<!--
The full path to the XML file that contains the custom dictionary for FxCop.
-->
<!--<FxCopCustomDictionary>$(DirWorkspace)\customdictionary.xml</FxCopCustomDictionary>-->
<!--
The culture that FxCop should use for the spelling rules.
-->
<!--<FxCopCulture>$(CodeAnalysisCulture)</FxCopCulture>-->
<!--
A flag that indicates whether any fxcop analysis errors should be marked as errors or as warnings. If FxCop analysis
errors are marked as errors then any analysis error will stop the build.
-->
<FxCopWarningsAsErrors>true</FxCopWarningsAsErrors>
</PropertyGroup>
<ItemGroup>
<!--
The locations of the files that should be analyzed by FxCop.
-->
<FxCopFiles
Exclude="$(DirSrc)\**\bin\$(Configuration)\Test.*.dll"
Include="$(DirSrc)\**\bin\$(Configuration)\nuclei.diagnostics.dll">
<CustomDictionary>$(FxCopCustomDictionary)</CustomDictionary>