This repository has been 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 pathsettings.props
1737 lines (1491 loc) · 87.3 KB
/
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 ToolsVersion="4.0"
DefaultTargets="Run"
xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
<!--
Certain properties and items in this settings file allow replacement of the following templates:
${VersionMajor} - The major version number
${VersionMinor} - The minor version number
${VersionPatch} - The patch version number
${VersionBuild} - The build number of the version
${VersionPreRelease} - The pre-release code, e.g. 'unstable'
${VersionSemantic} - The semantic version, e.g. 1.2.3
${VersionSemanticFull} - The full semantic version, e.g. 1.2.3-unstable.1+001
${VersionSEmanticNuGet} - The full semantic version as used by nuget, e.g. 1.2.3-unstable0001
${Configuration} - The configuration, e.g. Release
${Platform} - The platform name, e.g. Any CPU
${PlatformWithoutSpaces} - The platform name without spaces in it, e.g. AnyCPU
${VcsRevision} - The current VCS revision 'number'
${VcsBranch} - The name of the current VCS branch
${ReleaseNotesShort} - The contents of the short release notes
${ReleaseNotesFull} - The contents of the full release notes
${Now} - The current date and time in round trip format, e.g. 2015-05-15T19:31:45.1234567+12:00
${Date} - The current date in the format year-month-dayofmonth, e.g. 2015-05-15
${DayOfMonth} - The current day of the month, e.g. 15
${Month} - The current month, e.g. 05
${Year} - The current year, e.g. 2015
${ProductName} - The name of the product
${ProductNameInFilePath} - The product name written in a way that it can be used in the file path
${ProductDescription} - The (short) description of the product
${ProductNamespace} - The namespace in which all the code for the product is placed
${ProductStartingYear} - The year the current product was created / released.
${CompanyName} - The name of the company
${CompanyNameInFilePath} - The name of the company written in a way that it can be used in the file path
${CompanyUrl} - The URL of the company website
${CopyrightShort} - The short form of the copyright
${CopyrightLong} - The long form of the copyright
${FileReleaseNotesShort} - The file containing the short release notes
${FileReleaseNotesFull} - The file containing the full release notes
${DirWorkspace} - The full path to the directory that contains forms the base of the workspace for the project, e.g. c:\myproject
${DirBin} - The full path to the directory that contains the binaries, e.g. c:\myproject\build\bin\anycpu\release
${DirDeploy} - The full path to the directory that contains the artifacts, e.g. c:\myproject\build\deploy
${DirLogs} - The full path to the directory that contain the build logs, e.g. c:\myproject\build\logs
${DirSrc} - The full path to the directory that contains the source files, e.g. c:\myproject\src
${DirTemp} - The full path to the directory that contains the temporary build files, e.g c:\myproject\build\temp
${DirNBuildKit} - The full path to the directory that contains the nBuildKit scripts, e.g. c:\myproject\packages\nbuildkit.msbuild.0.1.0\build
${DirNBuildKitExtensions} - The full path to the directory that contains the nBuildKit extension scripts, e.g. c:\myproject\packages\nbuildkit.msbuild.0.1.0\build\extensions
${DirNBuildKitTemplates} - The full path to the directory that contains the nBuildKit template files, e.g. c:\myproject\packages\nbuildkit.msbuild.0.1.0\build\templates
${VersionNBuildKit} - The semantic version of nBuildKit that was used for the current build
Special template parameters exists for additional version numbers. These are defined in the TemplateVersion ItemGroup
as defined below.
-->
<!-- Overrides for the project specific properties -->
<PropertyGroup>
<!--
The name of the product. This is for instance used for:
* Copyrights
* API documentation
-->
<ProductName Condition=" '$(ProductName)' == '' ">Ops.Resource.Discovery</ProductName>
<!--
The name of the product that can be used as part of a file path. This is for instance used for:
* CCM
* SourceMonitor
* Deployment directory naming
-->
<ProductNameInFilePath Condition=" '$(ProductNameInFilePath)' == '' ">OpsResourceDiscovery</ProductNameInFilePath>
<!--
The description of the product. This is for instance used for:
* Installer information
-->
<ProductDescription>
The scripts and tools to create a Consul server in a windows server / docker container.
</ProductDescription>
<!--
The namespace in which all the code for the product is placed. This is for instance used for:
* Finding the correct assemblies and namespaces for unit testing and coverage reporting
* Generated code files that contain namespaces
-->
<ProductNamespace Condition=" '$(ProductNamespace)' == '' ">Ops.Resource.Discovery</ProductNamespace>
<!--
The first year the product was available / created. This is for instance used for:
* Copyrights
-->
<ProductStartingYear Condition=" '$(ProductStartingYear)' == '' ">2015</ProductStartingYear>
<!--
The name of the company. This is for instance used for:
* Copyrights
* API documentation
-->
<CompanyName Condition=" '$(CompanyName)' == '' ">P. van der Velde</CompanyName>
<!--
The name of the company that can be used as a part of a file path. This is for instance used for:
* Installer file paths
-->
<CompanyNameInFilePath Condition=" '$(CompanyNameInFilePath)' == '' ">pvandervelde</CompanyNameInFilePath>
<!--
The URL of the company website. This is for instance used for:
* nuspec files
-->
<CompanyUrl Condition=" '$(CompanyUrl)' == '' ">https://github.com/$(GitHubUserName)/ops-resource-discovery</CompanyUrl>
<!--
The email address that is specified in the documentation. This is for instance used for:
* API documentation
-->
<EmailDocumentation Condition=" '$(EmailDocumentation)' == '' ">UNDEFINED</EmailDocumentation>
<!--
The short form of the copyright text. This is for instance used for:
* Documentation copyrights
* Generated file copyrights
-->
<CopyrightShort>Copyright (c) - $(CompanyName). All rights reserved.</CopyrightShort>
<!--
The long form of the copyright text. This is for instance used for:
* Assembly copyrights
-->
<CopyrightLong>Copyright (c) - $(CompanyName) $(ProductStartingYear) - $([System.DateTime]::Now.ToString("yyyy")). All rights reserved.</CopyrightLong>
</PropertyGroup>
<!--
Overrides for the VCS specific properties
-->
<PropertyGroup>
<!-- The user name of the user who owns the repository on GitHub -->
<GitHubUserName Condition=" '$(GitHubUserName)' == '' ">UNDEFINED</GitHubUserName>
<!--
The github repository that contains the source code for the current product. Used when getting the release notes
from the github issues. The correct format is <USERNAME>/<REPOSITORYNAME>
-->
<GitHubRepositoryName Condition=" '$(GitHubRepositoryName)' == '' ">UNDEFINED</GitHubRepositoryName>
<!--
The full URL to the GIT repository. Can include the '%GitHubToken%' environment variable for authenticated
connection to the repository, e.g. https://%GitHubToken%:@github.com/MyUser/MyProject.git
-->
<GitRemoteRepository Condition=" '$(GitRemoteRepository)' == '' ">origin</GitRemoteRepository>
<!--
A flag indicating whether or not the workspace is a GIT workspace or not. If no value is provided then
any workspace that contains a .git folder will be assumed to be a GIT workspace.
-->
<IsGitWorkspace Condition=" '$(IsGitWorkspace)' == '' AND !Exists('$(DirWorkspace)\.git')">false</IsGitWorkspace>
<IsGitWorkspace Condition=" '$(IsGitWorkspace)' == '' AND Exists('$(DirWorkspace)\.git')">true</IsGitWorkspace>
<!--
A flag that indicates whether or not the workspace is a TFS workspace. Defaults to false.
-->
<IsTfsWorkspace Condition=" '$(IsTfsWorkspace)' == '' ">false</IsTfsWorkspace>
</PropertyGroup>
<!--
Defines the custom version numbers that should be available for template replacement.
The template consists of a name and a version number string. The name will be used as the
name of the template, i.e. 'VersionAssembly' will be available in the collection of template
parameters available for replacement.
Each version number may consist of zero or more template parameters. Template parameters
must be enclosed in '${}', e.g. ${VersionMajor} will be replaced by the major version number
as indicated at the top of the file.
Note that custom version number templates may not reference other custom version number templates.
-->
<ItemGroup>
<!--
The template for the version number that will be used in the 'AssemblyVersionAttribute' in the
'AssemblyInfo.VersionNumber.xx' file which can be generated if the 'ShouldGenerateAssemblyVersionInfo'
property is set to 'true'
-->
<TemplateVersion Include="VersionAssembly">
<Template>${VersionMajor}.${VersionMinor}.0.0</Template>
</TemplateVersion>
<!--
The template for the version number that will be used in the 'AssemblyFileVersionAttribute' in the
'AssemblyInfo.VersionNumber.xx' file which can be generated if the 'ShouldGenerateAssemblyVersionInfo'
property is set to 'true'
-->
<TemplateVersion Include="VersionAssemblyFile">
<Template>${VersionMajor}.${VersionMinor}.${VersionPatch}.${VersionBuild}</Template>
</TemplateVersion>
<!--
The template for the version number that will be used in the 'AssemblyInformationalVersionAttribute' in the
'AssemblyInfo.VersionNumber.xx' file which can be generated if the 'ShouldGenerateAssemblyVersionInfo'
property is set to 'true'
Also used as the 'ApplicationVersion' in the 'VersionNumber.wxi' file.
-->
<TemplateVersion Include="VersionProduct">
<Template>${VersionSemanticFull}</Template>
</TemplateVersion>
<!--
The template for the version number that will be used as the 'InstallVersion' in the
'VersionNumber.wxi' file which can be generated if the 'ShouldGenerateAssemblyVersionInfo'
property is set to 'true'
-->
<TemplateVersion Include="VersionInstall">
<Template>${VersionMajor}.${VersionMinor}.${VersionPatch}</Template>
</TemplateVersion>
<!--
The template for the version number that will be used as the 'ProductVersionFolder' in the
'VersionNumber.wxi' file which can be generated if the 'ShouldGenerateAssemblyVersionInfo'
property is set to 'true'
-->
<TemplateVersion Include="VersionInstallFilePath">
<Template>${VersionMajor}.${VersionMinor}</Template>
</TemplateVersion>
</ItemGroup>
<!--
Directories
-->
<PropertyGroup>
<!--
NOTE: The 'DirWorkspace' property is always set prior to loading the current file. The variable is set
to the directory which contains the current file.
-->
<!-- The directory that will contain all the files generated during the build process -->
<DirBuild Condition=" '$(DirBuild)' == '' ">$(DirWorkspace)\build</DirBuild>
<!--
The directory that will contain all the binaries generated during the build process.
Note that there may be configuration and platform specific sub-directories.
-->
<DirBuildBin Condition=" '$(DirBuildBin)' == '' ">$(DirBuild)\bin</DirBuildBin>
<!--
The directory where the current binaries are placed after being generated.
Note that $(Platform) and $(Configuration) do not have to be defined in this settings file. They may be provided
externally as long as they are provided before the settings file is loaded!
-->
<DirBuildBinPlatformConfig Condition=" '$(DirBuildBinPlatformConfig)' == '' ">$([System.IO.Path]::GetFullPath('$(DirBuildBin)\$(PlatformWithoutSpaces)\$(Configuration)\'))</DirBuildBinPlatformConfig>
<!-- The directory that will contain all the generated artifacts during the build process -->
<DirBuildDeploy Condition=" '$(DirBuildDeploy)' == '' ">$(DirBuild)\deploy</DirBuildDeploy>
<!-- The directory that will contain all the documentation files which are generated during the build process -->
<DirBuildDoc Condition=" '$(DirBuildDoc)' == '' ">$(DirBuildDeploy)\doc</DirBuildDoc>
<!-- The directory that will contain all the generated build logs during the build process -->
<DirBuildLogs Condition=" '$(DirBuildLogs)' == '' ">$(DirBuild)\logs</DirBuildLogs>
<!-- The directory that will contain the reports generated by OpenCover and ReportGenerator describing the coverage of the unit tests. -->
<DirReportGeneratorOutput Condition=" '$(DirReportGeneratorOutput)' == '' ">$(DirBuildLogs)\coverage</DirReportGeneratorOutput>
<!-- The directory that contains the report files generated by MoMA -->
<DirReportMoma Condition=" '$(DirReportMoma)' == '' ">$(DirBuildLogs)\moma</DirReportMoma>
<!-- The directory that will contain all the temporary files needed during the build process -->
<DirBuildTemp Condition=" '$(DirBuildTemp)' == '' ">$(DirBuild)\temp</DirBuildTemp>
<DirBuildTempDiscovery>$(DirBuildTemp)\discovery</DirBuildTempDiscovery>
<DirBuildTempDiscoveryShared>$(DirBuildTempDiscovery)\shared</DirBuildTempDiscoveryShared>
<DirBuildTempDiscoveryHyperV>$(DirBuildTempDiscovery)\hyperv</DirBuildTempDiscoveryHyperV>
<DirBuildTempDiscoveryLan>$(DirBuildTempDiscovery)\lan</DirBuildTempDiscoveryLan>
<!-- The directory that will contain all the test files generated during the test process -->
<DirBuildTest Condition=" '$(DirBuildTest)' == '' ">$(DirBuild)\tests</DirBuildTest>
<!-- The directory that contains all the Chef cookbooks -->
<DirChefCookbooks Condition=" '$(DirChefCookbooks)' == '' ">$(DirWorkspace)\cookbooks</DirChefCookbooks>
<DirChefCookbooksDiscoveryServer>$(DirChefCookbooks)\ops_resource_discovery</DirChefCookbooksDiscoveryServer>
<!-- The directory that contains all the NuGet packages for the project -->
<DirPackages Condition=" '$(DirPackages)' == '' ">$(DirWorkspace)\packages</DirPackages>
<!-- The directory that contains the source files for the project -->
<DirSrc Condition=" '$(DirSrc)' == '' ">$(DirWorkspace)\src</DirSrc>
<!-- The directory that contains all the script files -->
<DirScripts Condition=" '$(DirScripts)' == '' ">$(DirWorkspace)\scripts</DirScripts>
<!-- The directory that contains the template files for the project -->
<DirTemplates Condition=" '$(DirTemplates)' == '' ">$(DirWorkspace)\templates</DirTemplates>
<!-- The directory that contains all the test files for the project -->
<DirTest Condition=" '$(DirTest)' == '' ">$(DirWorkspace)\tests</DirTest>
</PropertyGroup>
<!--
Relative directories
-->
<PropertyGroup>
<RelDirConfiguration>configuration</RelDirConfiguration>
<RelDirConfigurationCookbooks>$(RelDirConfiguration)\cookbooks</RelDirConfigurationCookbooks>
<RelDirConfigurationCookbooksServer>$(RelDirConfigurationCookbooks)\ops_resource_discovery</RelDirConfigurationCookbooksServer>
<RelDirVerification>verification</RelDirVerification>
<RelDirVerificationTests>$(RelDirVerification)\tests</RelDirVerificationTests>
</PropertyGroup>
<!--
**** PREPARE - VERSIONING ****
-->
<PropertyGroup>
<!--
The full path to the file that contains the current version of the project in MsBuild format. The file is expected
to have the following structure:
<?xml version="1.0" encoding="utf-8"?>
<Project ToolsVersion="3.5"
DefaultTargets="Build"
xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
<PropertyGroup>
<BuildNumber>$(BUILD_NUMBER)</BuildNumber>
<BuildNumber Condition=" '$(BuildNumber)' == '' ">0</BuildNumber>
<VersionMajor>1</VersionMajor>
<VersionMinor>2</VersionMinor>
<VersionPatch>3</VersionPatch>
<VersionBuild>$(BuildNumber)</VersionBuild>
<VersionPreRelease></VersionPreRelease>
</PropertyGroup>
</Project>
-->
<FileVersionMsBuild Condition=" '$(FileVersionMsBuild)' == '' ">$(DirWorkspace)\version.xml</FileVersionMsBuild>
<!--
The full path to the file that is used to store the version information during the build.
-->
<FileSemanticVersion Condition=" '$(FileSemanticVersion)' == '' ">$(DirBuildTemp)\semantic_version.json</FileSemanticVersion>
<!--
When using GitVersion with a git repository that needs authentication the following properties
have to be defined on via an environment variable (either local to the process that executes the build,
or global to the user):
GitPassword - The user token that provides access to GitHub
The following properties can be defined on the command line or via the current script:
GitUserName - The user name of the user who owns the Git repository
Note that if no authentication is required, e.g. the repository allows anonymous access or
the authentication is done through the user account, i.e. via Active Directory, then
the user name should be left empty.
-->
<GitUserName Condition=" '$(GitUserName)' == '' "></GitUserName>
<!--
The full directory path to the script that handles custom generation of the version numbers.
The script is expected be a custom implementation of the CalculateCustomVersion.msbuild script.
The script file can be called anything as long as it contains an inline task
called CalculateCustomVersion that takes no parameters and returns the version number parts as follows:
VersionMajor - The major component of the version number, e.g. 1.
VersionMinor - The minor component of the version number, e.g. 2.
VersionPatch - The patch component of the version number, e.g. 3.
VersionBuild - The build component of the version number, e.g. 4.
VersionPreRelease - The pre-release section of the version number, e.g. 'unstable'
VersionSemantic - The short semantic version, normally made up of
<MAJOR>.<MINOR>.<PATCH>, e.g. 1.2.3
VersionSemanticFull - The full semantic version, normally made up of
<MAJOR>.<MINOR>.<PATCH>-<METADATA>+<BUILD>, e.g. 1.2.3-unstable+4
VersionSemanticNuget - The NuGet compatible semantic version, normally made up of
<MAJOR>.<MINOR>.<PATCH>-<PRERELEASE><BUILD>, e.g. 1.2.3-unstable4
-->
<VersionScriptPath Condition=" '$(VersionScriptPath)' == '' ">UNDEFINED</VersionScriptPath>
</PropertyGroup>
<!--
**** PREPARE - RELEASE NOTES ****
-->
<PropertyGroup>
<!-- The full path to the file that is used to store the release notes for the current release during the build. -->
<FileReleaseNotesShort Condition=" '$(FileReleaseNotesShort)' == '' ">$(DirBuildTemp)\releasenotes_short.md</FileReleaseNotesShort>
<!-- The full path to the file that is used to store the release notes for all the releases during the build. -->
<FileReleaseNotesFull Condition=" '$(FileReleaseNotesFull)' == '' ">$(DirBuildTemp)\releasenotes_full.md</FileReleaseNotesFull>
<!--
The following properties have to be defined on via an environment variable (either local to the process that
executes the build, or global to the user):
- Always
GitHubToken - The user token that provides access to GitHub
- When using YouTrack
IssueTrackerPassword - The password for the issue tracker user
-->
<!-- The user name of the user who owns the GitHub repository -->
<GitHubUserName Condition=" '$(GitHubUserName)' == '' ">UNDEFINED</GitHubUserName>
<!--- The URL of the YouTrack server, e.g. http://myuser.myjetbrains.com/youtrack -->
<YouTrackServer Condition=" '$(YouTrackServer)' == '' ">UNDEFINED</YouTrackServer>
<!-- The user name for YouTrack -->
<IssueTrackerUserName Condition=" '$(IssueTrackerUserName)' == '' ">UNDEFINED</IssueTrackerUserName>
<!-- The project ID that is used to identify the product in the issue tracker -->
<IssueTrackerProjectId Condition=" '$(IssueTrackerProjectId)' == '' ">UNDEFINED</IssueTrackerProjectId>
<!-- The filter for getting issues from YouTrack -->
<IssueFilter Condition=" '$(IssueFilter)' == '' ">UNDEFINED</IssueFilter>
</PropertyGroup>
<!--
**** PREPARE - VCS INFO ****
-->
<PropertyGroup>
<!-- The full path to the file that contains the information about the current VCS workspace. -->
<FileVcsInfo Condition=" '$(FileVcsInfo)' == '' ">$(DirBuildTemp)\vcs.info.json</FileVcsInfo>
</PropertyGroup>
<!--
**** PREPARE - GENERATE FILES ****
-->
<!--
Additional items that should be available for the template replacement.
The default template parameters, as indicated at the top of this file, are always available.
-->
<ItemGroup>
<TemplateTokens Include="DirBuildTempDiscoveryShared">
<ReplacementValue>$(DirBuildTempDiscoveryShared)</ReplacementValue>
</TemplateTokens>
<TemplateTokens Include="DirBuildTempDiscoveryHyperV">
<ReplacementValue>$(DirBuildTempDiscoveryHyperV)</ReplacementValue>
</TemplateTokens>
<TemplateTokens Include="DirBuildTempDiscoveryLan">
<ReplacementValue>$(DirBuildTempDiscoveryLan)</ReplacementValue>
</TemplateTokens>
</ItemGroup>
<!--
*************************************
* *
* BUILD SETTINGS *
* *
*************************************
-->
<!-- Overrides for the global properties -->
<PropertyGroup>
<!-- A flag indicating whether or not to display debug log information, usually at the start of the script execution. -->
<ShouldDisplayDebugLog Condition=" '$(ShouldDisplayDebugLog)' == '' ">true</ShouldDisplayDebugLog>
<!--
A flag that indicates whether or not the workspace should be cleaned before the build is started. If set to
true then the 'DirBuild' directory will be removed as well as all known generated files.
-->
<ShouldClean Condition=" '$(ShouldClean)' == ''">true</ShouldClean>
<!--
Indicates that the execution of the build script runs through the steps but does not actually execute them.
-->
<ShouldExecute Condition=" '$(ShouldExecute)' == '' ">true</ShouldExecute>
</PropertyGroup>
<!-- Overrides for the build configuration -->
<PropertyGroup>
<!-- The build configuration (debug / release / ...) that will be used to run all the unit tests and the static verification on -->
<TestConfiguration Condition=" '$(TestConfiguration)' == '' ">release</TestConfiguration>
<!-- The build configuration (debug / release / ..) that will be used to create the binaries that should be deployed -->
<ProductionConfiguration Condition=" '$(ProductionConfiguration)' == '' ">deploy</ProductionConfiguration>
<!-- The platform for which the binaries will be build -->
<Platform Condition=" '$(Platform)' == '' ">Any CPU</Platform>
<PlatformWithoutSpaces>$(Platform.Replace(" ",""))</PlatformWithoutSpaces>
</PropertyGroup>
<!--
**** BUILD STEPS ****
-->
<!--
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.
The following build steps are by default provided through the given properties:
$(BuildStepsPrepareWorkspace) - Deletes the existing build artifacts and creates the required directories.
$(BuildStepsPrepareRestoreNuGet) - Restores the NuGet packages for the project.
$(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)
$(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
$(BuildStepsPrepareVcsInfo) - Stores the Version Control System (VCS) information in a file for later use.
Currently supported version control systems is GIT
$(BuildStepsPrepareGenerateFiles) - Generates one or more files from a set of template files.
$(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.
$(BuildStepsAnalyzeBinariesMoma) - Analyzes the binary files with Moma (Mono Migration Analyzer).
$(BuildStepsAnalyzeBinariesFxCop) - Analyzes the binary files with FxCop.
$(BuildStepsBuildApiDocumentationWithSandcastle) - Builds the API documentation with SandCastle from the inline XML documentation comments.
$(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.
Each script has the following properties passed to it:
$(BuildPropertyFile) - The full path to the settings.props file (i.e. this file).
$(ShouldDisplayDebugLog) - A flag indicating whether or not to display debug log information, usually at the start of the script execution.
$(NBuildKitVersion) - The full version of the nBuildKit library that is executing the build.
$(DirNBuildKitMsBuild) - The full path to the directory that contains the nBuildKit scripts.
$(DirNBuildKitMsBuildExtensions) - The full path to the directory that contains the nBuildKit extension scripts.
$(DirNBuildKitMsBuildTemplates) - The full path to the directory that contains the nBuildKit templates.
Additionally any properties defined by the 'Properties' section are also pushed up.
-->
<ItemGroup>
<BuildStepsToExecute Include="$(BuildStepsPrepareWorkspace)">
<Properties>
</Properties>
</BuildStepsToExecute>
<BuildStepsToExecute Include="$(BuildStepsPrepareRestoreNuGet)">
<Properties>
</Properties>
</BuildStepsToExecute>
<BuildStepsToExecute Include="$(BuildStepsPrepareGetVersion)">
<Properties>
</Properties>
</BuildStepsToExecute>
<!--
<BuildStepsToExecute Include="$(BuildStepsPrepareReleaseNotes)">
<Properties>
</Properties>
</BuildStepsToExecute>
-->
<BuildStepsToExecute Include="$(BuildStepsPrepareVcsInfo)">
<Properties>
</Properties>
</BuildStepsToExecute>
<!--
<BuildStepsToExecute Include="$(BuildStepsPrepareGenerateFiles)">
<Properties>
</Properties>
</BuildStepsToExecute>
-->
<BuildStepsToExecute Include="$(DirWorkspace)\build.prepare.discovery.msbuild">
<Properties>
</Properties>
</BuildStepsToExecute>
<!--
<BuildStepsToExecute Include="$(BuildStepsAnalyzeSourceCcm)">
<Properties>
</Properties>
</BuildStepsToExecute>
<BuildStepsToExecute Include="$(BuildStepsAnalyzeSourceSouceMonitor)">
<Properties>
</Properties>
</BuildStepsToExecute>
-->
<!--
<BuildStepsToExecute Include="$(DirWorkspace)\analyze.rubocop.msbuild">
<Properties>
</Properties>
</BuildStepsToExecute>
<BuildStepsToExecute Include="$(DirWorkspace)\analyze.foodcritic.msbuild">
<Properties>
</Properties>
</BuildStepsToExecute>
-->
<!--
<BuildStepsToExecute Include="$(BuildStepsBuildVisualStudioSolution)">
<Properties>
</Properties>
</BuildStepsToExecute>
<BuildStepsToExecute Include="$(BuildStepsUnitTestNUnit)">
<Properties>
Configuration=$(TestConfiguration);
Platform=$(Platform)
</Properties>
</BuildStepsToExecute>
<BuildStepsToExecute Include="$(BuildStepsUnitTestMsTest)">
<Properties>
Configuration=$(TestConfiguration);
Platform=$(Platform)
</Properties>
</BuildStepsToExecute>
-->
<!--
<BuildStepsToExecute Include="$(DirWorkspace)\test.unit.chefspec.msbuild">
<Properties>
Configuration=$(TestConfiguration);
Platform=$(Platform)
</Properties>
</BuildStepsToExecute>
-->
<!--
<BuildStepsToExecute Include="$(BuildStepsAnalyzeBinariesMoma)">
<Properties>
Configuration=$(TestConfiguration);
Platform=$(Platform)
</Properties>
</BuildStepsToExecute>
<BuildStepsToExecute Include="$(BuildStepsAnalyzeBinariesFxCop)">
<Properties>
Configuration=$(TestConfiguration);
Platform=$(Platform)
</Properties>
</BuildStepsToExecute>
<BuildStepsToExecute Include="$(BuildStepsBuildApiDocumentationWithSandcastle)">
<Properties>
Configuration=$(ProductionConfiguration);
Platform=$(Platform)
</Properties>
</BuildStepsToExecute>
-->
<!--
<BuildStepsToExecute Include="$(BuildStepsPackNuGet)">
<Properties>
</Properties>
</BuildStepsToExecute>
-->
<BuildStepsToExecute Include="$(BuildStepsPackZip)">
<Properties>
Configuration=$(ProductionConfiguration);
Platform=$(Platform)
</Properties>
</BuildStepsToExecute>
<!--
This should be part of a series of steps. The different steps in this stage should be called only when needed.
Need nBuildKit 0.8 for that.
-->
<!--
<BuildStepsToExecute Include="$(DirWorkspace)\build.hypervimage.msbuild">
<Properties>
Configuration=$(ProductionConfiguration);
Platform=$(Platform)
</Properties>
</BuildStepsToExecute>
<BuildStepsToExecute Include="$(DirWorkspace)\build.containerimage.msbuild">
<Properties>
Configuration=$(ProductionConfiguration);
Platform=$(Platform)
</Properties>
</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.
Each script has the following properties passed to it:
$(BuildPropertyFile) - The full path to the settings.props file (i.e. this file).
$(ShouldDisplayDebugLog) - A flag indicating whether or not to display debug log information, usually at the start of the script execution.
$(NBuildKitVersion) - The full version of the nBuildKit library that is executing the build.
$(DirNBuildKitMsBuild) - The full path to the directory that contains the nBuildKit scripts.
$(DirNBuildKitMsBuildExtensions) - The full path to the directory that contains the nBuildKit extension scripts.
$(DirNBuildKitMsBuildTemplates) - The full path to the directory that contains the nBuildKit templates.
Additionally any properties defined by the 'Properties' section are also pushed up.
-->
<ItemGroup>
<!--
<BuildFailureStepsToExecute Include="">
<Properties>
</Properties>
</BuildFailureStepsToExecute>
-->
</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. Template parameters must be enclosed in '${}'.
Additional parameters can be provided through the 'TemplateTokens' ItemGroup below.
-->
<ItemGroup>
<BuildFilesToGenerate Include="$(DirBuildTemp)\MyFile.txt">
<Template>$(DirTemplates)\MyTemplatefile.txt</Template>
</BuildFilesToGenerate>
<BuildFilesToGenerate Include="$(DirBuildTemp)\MyOtherFile.txt">
<Template>$(DirTemplates)\MyOtherTemplatefile.txt</Template>
<Token>MyAdditionalTemplateParameter</Token>
<ReplacementValue>MyAdditionalTemplateValue</ReplacementValue>
</BuildFilesToGenerate>
</ItemGroup>
<!--
**** SOURCE ANALYSIS - CCM ****
-->
<PropertyGroup>
<!--
The full path to the template file that is used to provide the project information for CCM. Defaults
to the template file included with nBuildKit.
-->
<FileTemplateCcm Condition=" '$(FileTemplateCcm)' == '' ">$(DirNBuildKitMsBuildTemplates)\ccm.xml</FileTemplateCcm>
<!--
The full path to the report file generated by CCM. Allows build templates. Allows build templates,
e.g. $(DirBuildLogs)\${ProductName}_ccm.xml.
-->
<FileReportCcm Condition=" '$(FileReportCcm)' == '' ">$(DirBuildLogs)\ccm.xml</FileReportCcm>
</PropertyGroup>
<!--
**** SOURCE ANALYSIS - SOURCEMONITOR ****
-->
<PropertyGroup>
<!--
The full path to the template file that is used to provide the project information for SourceMonitor. Defaults
to the template file included with nBuildKit.
-->
<FileTemplateSourceMonitor Condition=" '$(FileTemplateSourceMonitor)' == '' ">$(DirNBuildKitMsBuildTemplates)\sourcemonitor.xml</FileTemplateSourceMonitor>
<!--
The full path to the report file generated by SourceMonitor. Allows build templates. Allows build templates,
e.g. $(DirBuildLogs)\${ProductName}_sourcemonitor.xml
-->
<FileReportSourceMonitor Condition=" '$(FileReportSourceMonitor)' == '' ">$(DirBuildLogs)\sourcemonitor.xml</FileReportSourceMonitor>
</PropertyGroup>
<!--
**** 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 Include="$(DirSrc)\myproject.sln">
<Configuration>$(TestConfiguration)</Configuration>
<Platform>$(Platform)</Platform>
<Targets>Rebuild</Targets>
<Properties></Properties>
</SolutionsToBuild>
<SolutionsToBuild Include="$(DirSrc)\myproject.sln">
<Configuration>$(ProductionConfiguration)</Configuration>
<Platform>$(Platform)</Platform>
<Targets>Rebuild</Targets>
<Properties></Properties>
</SolutionsToBuild>
</ItemGroup>
<PropertyGroup>
<!--
A flag that indicates whether the source files with the company and product information should be generated.
The files will be placed in the source directory (i.e. DirSrc) and will be called CompanyInformation.xx
(cs/vb/wxi) and ProductInformation.xx (cs/vc/wxi).
The CompanyInformation file will contain the Company website URL, the company name and the company name as used
in file paths.
The ProductInformation file will contain the product name, the product description and the product name as used
in file paths.
Any namespaces will be created as <ProductNamespace>.Internals where 'ProductNamespace' is defined
in the current file at the top.
-->
<ShouldGenerateCompanyAndProductInfo>false</ShouldGenerateCompanyAndProductInfo>
<!--
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>false</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>false</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>false</ShouldGenerateAssemblyBuildInfo>
<!--
A flag that indicates whether an application manifest file should be generated for executables. The
manifest file is placed in the same directory as the Visual Studio project and will be named
<ProjectOutputName>.manifest, e.g. MyCoolApp.exe.manifest.
-->
<ShouldGenerateApplicationManifest>false</ShouldGenerateApplicationManifest>
<!--
A flag that indicates whether the current project is a Test project. The value will be set in the Visual
Studio project files based on whether the project is a test project (as determined by the ProjectType GUID).
This value is defined here just so that there is a value when no other value is specified. Do not comment this
value out unless you know what you are doing!
-->
<IsTest Condition=" '$(IsTest)' == '' ">false</IsTest>
</PropertyGroup>
<!-- Build configuration -->
<PropertyGroup>
<!--
A flag indicating whether warnings should be treated as errors by the compiler. This value is set
for all projects that include the MsBuild.Projects.XXXX NuGet package.
-->
<TreatWarningsAsErrors>true</TreatWarningsAsErrors>
<!--
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>
<!--
The platform against which the code should be compiled. Note that the target should not have space in it,
i.e. AnyCPU, x86, x64 etc.
-->
<PlatformTarget>$(PlatformWithoutSpaces)</PlatformTarget>
</PropertyGroup>
<!-- Execute code analysis after the build -->
<PropertyGroup>
<!--
A flag that indicates whether or not the code analysis should be executed immediately after the compilation
process is complete.
-->
<ShouldPerformCodeAnalysis Condition=" '$(ShouldPerformCodeAnalysis)' == '' ">true</ShouldPerformCodeAnalysis>
<!--
The code analysis rule set that should be used for non-test assemblies.
-->
<CodeAnalysisRuleSet Condition="$(ShouldPerformCodeAnalysis) AND !$(IsTest)">$(SolutionDir)\codeanalysis.base.ruleset</CodeAnalysisRuleSet>
<!--
The code analysis rule set that should be used for test assemblies. If no code analysis should be executed on test
assemblies then it can be turned off in the settings for the different build configurations below.
-->
<CodeAnalysisRuleSet Condition="$(ShouldPerformCodeAnalysis) AND $(IsTest)">$(SolutionDir)\codeanalysis.test.ruleset</CodeAnalysisRuleSet>
<!--
The culture which will be used by the code analysis when searching for spelling errors. The culture name should
be formatted using the .NET culture format.
-->
<CodeAnalysisCulture Condition="$(ShouldPerformCodeAnalysis)">en-US</CodeAnalysisCulture>
</PropertyGroup>
<!-- Generate the XML documentation file -->
<PropertyGroup>
<!--
A flag indicating whether or not the XML documentation file should be generated during the compilation process.
Note that if 'WarningsAsErrors' is enabled then missing documentation will generate errors that stop the
build process.
If documentation should only be generated for non-test assemblies then add the '!$(IsTest)' condition
to the property.
-->
<GenerateDocumentation>true</GenerateDocumentation>
<!--
The full file path where the XML documentation file should be created.
-->
<DocumentationFile Condition="$(GenerateDocumentation) AND !$(IsTest)">$(OutputPath)\$(AssemblyName).XML</DocumentationFile>
</PropertyGroup>
<!-- Strong name the binaries -->
<PropertyGroup>
<!--
A flag that indicates whether or not the assemblies should be strong named during the compilation process.
-->
<ShouldSign Condition=" '$(ShouldSign)' == '' ">true</ShouldSign>
<SignAssembly Condition="$(ShouldSign)">true</SignAssembly>
<DelaySign Condition="$(ShouldSign)">false</DelaySign>
<!--
The full path of the key file that will be used to sign the assemblies during the compilation process.
-->
<AssemblyOriginatorKeyFile Condition="$(ShouldSign)">$(SOFTWARE_SIGNING_KEY_PATH)</AssemblyOriginatorKeyFile>
</PropertyGroup>
<!--
Debug configuration
-->
<PropertyGroup Condition=" '$(Configuration)' == 'Debug' ">
<DebugSymbols>true</DebugSymbols>
<DebugType>full</DebugType>
<DefineDebug>true</DefineDebug>
<DefineTrace>true</DefineTrace>
<Optimize>false</Optimize>
<RunCodeAnalysis>$(ShouldPerformCodeAnalysis)</RunCodeAnalysis>
</PropertyGroup>
<!--
Release configuration
-->
<PropertyGroup Condition=" '$(Configuration)' == 'Release' ">
<DebugSymbols>false</DebugSymbols>
<DebugType>pdbonly</DebugType>
<DefineDebug>false</DefineDebug>
<DefineTrace>true</DefineTrace>
<Optimize>true</Optimize>
<RunCodeAnalysis>$(ShouldPerformCodeAnalysis)</RunCodeAnalysis>
</PropertyGroup>
<!-- Compiler specific configurations -->
<PropertyGroup>
<!--
Indicates what the warning level is for the C# compiler.
-->
<CSharpWarningLevel>4</CSharpWarningLevel>
<!--
Define any additional constants for the C# compiler. Multiple constants should be
separated by a semi-colon (;).
-->
<CSharpConstants>TRACE</CSharpConstants>
<!--
The name of the directory that contains the VB.NET AssemblyInfo and resoure files.
-->
<VbNetAppDesignerFolder>My Project</VbNetAppDesignerFolder>
<!--
Indicates if the VB.NET Option Explicit is 'on' or 'off'
-->
<VbNetOptionExplicit>On</VbNetOptionExplicit>
<!--
Indicates if the VB.NET Option strict is 'on' or 'off'
-->
<VbNetOptionStrict>On</VbNetOptionStrict>
</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