ExtremeCSharpTestDataFactory/Directory.Build.props at master · nilvon9wo/ExtremeCSharpTestDataFactory · 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
<Project>

  <!--
    Without EnforceCodeStyleInBuild, the strict IDE0xxx/error-severity rules
    in .editorconfig are enforced only by an IDE's live analysis (or
    `dotnet format`), never by `dotnet build` or CI - a silent gap that let
    real violations through undetected. This closes it for every project in
    the solution.
  -->
  <PropertyGroup>
    <EnforceCodeStyleInBuild>true</EnforceCodeStyleInBuild>
    <AnalysisLevel>latest</AnalysisLevel>
  </PropertyGroup>

  <!--
    Without this, each multi-targeted TFM's compile pass infers its own
    default C# language version - netstandard2.0 defaults to a much older
    one unless told otherwise, and would reject init accessors, primary
    constructors, collection expressions, etc. outright. Pinning this once,
    solution-wide, keeps every TFM's compile pass on the same modern syntax
    rules; per-TFM *runtime*-capability gaps (not syntax) are still handled
    separately, per project, via PolySharp/#if.
  -->
  <PropertyGroup>
    <LangVersion>latest</LangVersion>
  </PropertyGroup>

  <!--
    Single source of truth for the version of every mainline (non-preview)
    publishable package - `Xfty`, `Xfty.EntityFrameworkCore`,
    `Xfty.EntityFramework6`, `Xfty.Bogus`, `Xfty.VectorDatabases`, `Xfty.Xunit`,
    `Xfty.AutoFixture`, `Xfty.AutoBogus`, `Xfty.FSharpAsync`. They no longer
    carry their own <Version>; they inherit this one, so they stay in
    lockstep automatically.

    `0.0.0-dev` is only the LOCAL-build fallback (a `dotnet pack` on a dev
    machine produces `*.0.0.0-dev.nupkg`, obviously not a release). The real
    release version is NOT set here and is NOT bumped per release: the
    `publish.yml` workflow reads the newest `## [x.y.z]` heading from
    CHANGELOG.md and stamps it in (`-p:Version=` / an in-runner edit of this
    file) at pack time. Cutting a release = adding that CHANGELOG heading in
    your PR; merging to master publishes it. See docs/contribute/packaging.md.

    The two PREVIEW packages (`Xfty.VectorDatabases.Qdrant`,
    `Xfty.VectorDatabases.MicrosoftExtensionsVectorData`) deliberately keep
    their own <Version> (`0.x-preview.*`) in their own .csproj - that value
    overrides this one because the project sets it after this import.
  -->
  <PropertyGroup>
    <Version>0.0.0-dev</Version>
  </PropertyGroup>

</Project>