tamp/Directory.Build.props at main · tamp-build/tamp · GitHub

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
<Project>

  <PropertyGroup>
    <LangVersion>latest</LangVersion>
    <Nullable>enable</Nullable>
    <ImplicitUsings>enable</ImplicitUsings>
    <TreatWarningsAsErrors>true</TreatWarningsAsErrors>
    <EnforceCodeStyleInBuild>true</EnforceCodeStyleInBuild>
    <DebugType>embedded</DebugType>
    <Deterministic>true</Deterministic>
    <ContinuousIntegrationBuild Condition="'$(CI)' == 'true'">true</ContinuousIntegrationBuild>
    <NeutralLanguage>en-US</NeutralLanguage>
    <NoWarn>$(NoWarn);CS1591</NoWarn>
  </PropertyGroup>

  <PropertyGroup Label="Tamp package metadata defaults">
    <Authors>Scott Singleton</Authors>
    <Company>Tamp Project</Company>
    <Copyright>Copyright (c) 2026 Scott Singleton</Copyright>
    <PackageProjectUrl>https://github.com/tamp-build/tamp</PackageProjectUrl>
    <RepositoryUrl>https://github.com/tamp-build/tamp</RepositoryUrl>
    <RepositoryType>git</RepositoryType>
    <PackageLicenseExpression>MIT</PackageLicenseExpression>
    <PackageTags>tamp;build;automation;ci;dotnet</PackageTags>
    <PublishRepositoryUrl>true</PublishRepositoryUrl>
    <EmbedUntrackedSources>true</EmbedUntrackedSources>
    <!--
      Debug info is embedded in the DLL (DebugType=embedded above) so
      consumers can step into Tamp from their builds without an extra
      snupkg. We deliberately do NOT emit a separate symbol package:
      embedded PDBs leave nothing for snupkg to pack, which trips NU5017.
    -->
  </PropertyGroup>


  <PropertyGroup Label="Tamp central version (TAM-81 — single source of truth for all packable projects in this repo). Bump this before tagging a release; csprojs do NOT carry their own Version element.">
    <Version>1.13.0</Version>
  </PropertyGroup>

  <!--
    TAM-248: opt-in Roslyn analyzer pack for the security chain.
    Activated by `/p:IncludeSecurityAnalyzers=true` (set by the
    SecurityScanRoslyn target in build/Build.cs). When unset, the default
    Compile / Test / Pack flow runs without these analyzers and keeps the
    existing TreatWarningsAsErrors green-build invariant.

    Skipped for test projects on purpose — we want SARIF focused on
    production code, not test scaffolding.

    ErrorLog is set here (not via /p:ErrorLog=…) so MSBuild evaluates
    $(MSBuildProjectName) per-project at load time. Passing /p:ErrorLog=
    on the command line treats the value as a literal and every project
    would clobber the same SARIF file.
  -->
  <ItemGroup Condition="'$(IncludeSecurityAnalyzers)' == 'true' AND '$(IsTestProject)' != 'true'">
    <PackageReference Include="SonarAnalyzer.CSharp" PrivateAssets="all" IncludeAssets="analyzers;build" />
    <PackageReference Include="Roslynator.Analyzers" PrivateAssets="all" IncludeAssets="analyzers;build" />
  </ItemGroup>

  <PropertyGroup Condition="'$(IncludeSecurityAnalyzers)' == 'true' AND '$(IsTestProject)' != 'true'">
    <ErrorLog>$(MSBuildThisFileDirectory)artifacts/security/roslyn/$(MSBuildProjectName)-$(TargetFramework).sarif,version=2.1</ErrorLog>
    <ReportAnalyzer>true</ReportAnalyzer>
  </PropertyGroup>

</Project>