Files
frameledger/Directory.Build.props
poli0981andClaude Fable 5.2 1c60c87b92 legal: what an alpha is once .NET 11 has shipped - EULA 1.7, Disclaimer 2.14, Alpha notice 1.1; a resting alpha says so and names a prerelease only where it runs on one (D97, D98) (beta.37 PR-2) (#379)
Until 0.1.0-alpha.3 an alpha was "a beta's source built on a prerelease
.NET" and every text said so. 0.1.0-alpha.4 runs on .NET 11's release -
the betas' own from beta.37 - and the alpha line rests after it.

- EULA 1.7 (section 2B), Disclaimer 2.14 (section 0, which also gains
  the paragraph on Windows and the processor), Alpha notice 1.1 (what an
  alpha is, the hardware, the pause), the accuracy statement's line and
  its two copies. The texts were approved with the plan of 2026-11-11.
- Shared.AlphaLine: IsPrerelease(the runtime's description) and Rests,
  stamped from Directory.Build.props' FlAlphaLineRests (true on main
  since beta.37; set to false on the alpha branch when it tries a newer
  .NET). App/Services/AlphaTexts picks the banner and About's line from
  the two facts; a prerelease runtime is said whatever the stamp says.
- Strings in en, vi and ja: the banner and About's line no longer say
  "a prerelease .NET" unconditionally; three new keys.
- guide (the alphas are paused: install the beta; a paused alpha's
  anti-cheat list is not updated; ten betas after alpha.4 hide it from
  older alphas), LIMITATIONS, 11_UPDATER, 12_BUILD, 08_UI, the wiki.

Co-authored-by: Claude Fable 5.2 <noreply@anthropic.com>
2026-11-10 23:28:40 +00:00

165 lines
9.9 KiB
XML

<Project>
<!--
Shared MSBuild properties for every managed project. See docs/12_BUILD.md.
TargetFramework vs SupportedOSPlatformVersion are two different knobs and
must not be conflated:
- TargetFramework's platform version selects which Windows API
projections are available to compile against.
- SupportedOSPlatformVersion is the floor CA1416 enforces.
NFR-8 names Windows 10 22H2 = build 19045 as the oldest Windows the code is
held to (since 2026-11-11, D95: not blocked there, and neither tested nor
supported - Microsoft supports .NET 11 on Windows 11). Letting the supported
version default to the TFM's 19041 would silently accept installs three
releases below that floor.
A bare `net11.0-windows` is wrong for a different reason: it resolves to
net11.0-windows7.0, and CA1416 would then error on Mica, MiniDumpWriteDump
and IDXGIAdapter3::QueryVideoMemoryInfo — every Windows-10-era API this
application is built on.
Why the target is 22621 and not 19045: the SDK enforces
SupportedOSPlatformVersion <= TargetPlatformVersion (NETSDK1135), and 19045
is not a Windows targeting-pack version in any case — the packs are cut at
19041, 20348, 22000, 22621, 26100. docs/12_BUILD.md already requires the
Windows 11 SDK >= 10.0.22621 as a prerequisite, so targeting it costs
nothing and CA1416 still enforces the 19045 floor at the API level.
-->
<PropertyGroup>
<!-- .NET 11 since 0.1.0-beta.37 (owner decision D94, 2026-11-11; docs/12_BUILD.md). net10.0 until then, and
net11.0 on the alpha branch from 2026-10-31. -->
<TargetFramework>net11.0-windows10.0.22621.0</TargetFramework>
<SupportedOSPlatformVersion>10.0.19045.0</SupportedOSPlatformVersion>
<!-- x64 only (CLAUDE.md pinned stack, NFR-8). Previously asserted in prose
and enforced nowhere except an ad-hoc -r win-x64 on the publish line.
RuntimeIdentifier is set per-executable rather than here: forcing a RID
onto class libraries pulls RID-specific assets into their restore for
no benefit. -->
<Platforms>x64</Platforms>
<PlatformTarget>x64</PlatformTarget>
<LangVersion>latest</LangVersion>
<Nullable>enable</Nullable>
<ImplicitUsings>enable</ImplicitUsings>
<InvariantGlobalization>false</InvariantGlobalization>
<TreatWarningsAsErrors>true</TreatWarningsAsErrors>
<AnalysisLevel>latest-all</AnalysisLevel>
<EnforceCodeStyleInBuild>true</EnforceCodeStyleInBuild>
<EnableNETAnalyzers>true</EnableNETAnalyzers>
<Deterministic>true</Deterministic>
<ContinuousIntegrationBuild Condition="'$(CI)' == 'true'">true</ContinuousIntegrationBuild>
<GenerateDocumentationFile>true</GenerateDocumentationFile>
<!-- i18n: keep publish size down (docs/09_I18N.md). -->
<SatelliteResourceLanguages>en;vi;ja</SatelliteResourceLanguages>
<ManagePackageVersionsCentrally>true</ManagePackageVersionsCentrally>
<!-- ONE version source (P4 PR-5, docs/12_BUILD.md §Version): the VERSION file
at the repository root. src/native/CMakeLists.txt reads the same file for
the VERSIONINFO blocks, and tools/versioninfo-check.ps1 compares the built
binaries against it, so the managed and native halves cannot drift. The
condition lets release.yml pass -p:Version=<tag> for a pre-release
(0.1.0-beta.1 is not a number CMake's project() accepts, so the native
FileVersion stays the numeric core). SourceLink's "+sha" suffix is off so
About, Hello and the bug bundle print the version a user can find on the
releases page. -->
<FrameLedgerVersionFile>$(MSBuildThisFileDirectory)VERSION</FrameLedgerVersionFile>
<Version Condition="'$(Version)' == '' And Exists('$(FrameLedgerVersionFile)')">$([System.IO.File]::ReadAllText('$(FrameLedgerVersionFile)').Trim())</Version>
<IncludeSourceRevisionInInformationalVersion>false</IncludeSourceRevisionInInformationalVersion>
<!-- D73 (2026-10-31): the RELEASE LINE, from the RELEASE_LINE file beside VERSION - `main`, the betas and releases on
the .NET that global.json pins, or `alpha`, a beta's source built to try a newer .NET from the long-lived `alpha`
branch, where this file and global.json are two of the few lines that differ while it does (docs/12_BUILD.md
§The alpha line).
Not a property a command line sets: the file is the one source, release.yml refuses a tag that disagrees with it,
and the target below refuses a value that is neither line. Every assembly carries it (the ItemGroup below), and
Shared.BuildLine reads it at run time. -->
<FrameLedgerReleaseLineFile>$(MSBuildThisFileDirectory)RELEASE_LINE</FrameLedgerReleaseLineFile>
<FlReleaseLine Condition="Exists('$(FrameLedgerReleaseLineFile)')">$([System.IO.File]::ReadAllText('$(FrameLedgerReleaseLineFile)').Trim())</FlReleaseLine>
<!-- D98 (2026-11-11): THE ALPHA LINE RESTS - the betas build on the same .NET as the newest alpha (0.1.0-alpha.4,
.NET 11.0.0), so no alpha is cut until a newer .NET is tried. An alpha built while this says true tells its user
that the line is paused and to install the beta: a resting alpha gets no update, its anti-cheat list included
(Shared.AlphaLine, App/Services/AlphaTexts). Stamped on both lines, read by an alpha alone. When the `alpha`
branch starts trying a newer .NET it sets this to false there - one more line of its switch (docs/12_BUILD.md
§The alpha line). -->
<FlAlphaLineRests>true</FlAlphaLineRests>
</PropertyGroup>
<ItemGroup>
<AssemblyMetadata Include="FrameLedger.ReleaseLine" Value="$(FlReleaseLine)" />
<AssemblyMetadata Include="FrameLedger.AlphaLineRests" Value="$(FlAlphaLineRests)" />
</ItemGroup>
<Target Name="FrameLedgerReleaseLineCheck" BeforeTargets="BeforeBuild" Condition="'$(FlReleaseLine)' != 'main' And '$(FlReleaseLine)' != 'alpha'">
<Error Text="RELEASE_LINE at the repository root must say 'main' or 'alpha', and it says '$(FlReleaseLine)' (docs/12_BUILD.md §The alpha line)" />
</Target>
<!-- The NuGet audit (2026-10-25, docs/13_CI_CD.md §Dependabot and the NuGet audit): every restore checks the WHOLE
package graph, transitive packages included, against the advisory database, at every severity. These were the
SDK's defaults for net10.0, written down so that a later SDK's defaults cannot move them. With
TreatWarningsAsErrors, a vulnerable package is NU1901-NU1904 and the restore - and so the gate - is red, which
is what happened with SQLitePCLRaw 2.1.11 (Directory.Packages.props). -->
<PropertyGroup>
<NuGetAudit>true</NuGetAudit>
<NuGetAuditMode>all</NuGetAuditMode>
<NuGetAuditLevel>low</NuGetAuditLevel>
</PropertyGroup>
<!-- beta.14 (D50): every managed binary names the product and who wrote it, as the native ones always have
(19_SAFETY: a binary says plainly what it is). Explorer's Properties > Details and Task Manager read these. Until
beta.14 the SDK's defaults stood: the Agent's Company and Product read "FrameLedger.Agent", each library's its own
assembly name, and no managed binary carried a copyright. The copyright is the native FL_COPYRIGHT
(src/native/CMakeLists.txt) word for word: tools/versioninfo-check.ps1 reads both from the built binaries and is
red when they differ. The file description is the AssemblyTitle - an entry point sets its own, a library keeps its
assembly name - and the Description is the Comments field, the native blocks' sentence for a library. The SDK
stamps RepositoryUrl into every assembly as AssemblyMetadata; it is the App's IssueLink.Repository, and the App's
AssemblyIdentityTests holds the two equal (a fork changes both - FORKING.md). -->
<PropertyGroup>
<Company>FrameLedger</Company>
<Product>FrameLedger</Product>
<Authors>poli0981</Authors>
<Copyright>Copyright (C) 2026 poli0981. GPL-3.0-only with additional terms: see NOTICE</Copyright>
<Description>Performance measurement tool. Identifies itself deliberately; see https://github.com/poli0981/frameledger</Description>
<RepositoryUrl>https://github.com/poli0981/frameledger</RepositoryUrl>
</PropertyGroup>
<!-- beta.12: the source a build was made from - release.yml passes the tag (a rehearsal, its commit); a local build has
none. The App's links into the repository open THIS version's documents with it (Services/RepositoryLinks.cs).
Every assembly since beta.14 (D50), not the App's alone: the two publishes build the same libraries into one
out/app, and release.yml passes the same ref to both. -->
<ItemGroup Condition="'$(FrameLedgerSourceRef)' != ''">
<AssemblyMetadata Include="FrameLedgerSourceRef" Value="$(FrameLedgerSourceRef)" />
</ItemGroup>
<!-- Test projects: documentation comments are noise, and xUnit's own
analyzers already cover what matters there. -->
<PropertyGroup Condition="$(MSBuildProjectName.EndsWith('.Tests'))">
<GenerateDocumentationFile>false</GenerateDocumentationFile>
<IsPackable>false</IsPackable>
</PropertyGroup>
<!-- Analyzers everywhere (CLAUDE.md §Coding conventions). Build-time only,
so they do not violate Domain's "references nothing" rule. -->
<ItemGroup>
<PackageReference Include="Roslynator.Analyzers">
<PrivateAssets>all</PrivateAssets>
<IncludeAssets>runtime; build; native; contentfiles; analyzers; buildtransitive</IncludeAssets>
</PackageReference>
<PackageReference Include="Meziantou.Analyzer">
<PrivateAssets>all</PrivateAssets>
<IncludeAssets>runtime; build; native; contentfiles; analyzers; buildtransitive</IncludeAssets>
</PackageReference>
<PackageReference Include="Microsoft.VisualStudio.Threading.Analyzers">
<PrivateAssets>all</PrivateAssets>
<IncludeAssets>runtime; build; native; contentfiles; analyzers; buildtransitive</IncludeAssets>
</PackageReference>
</ItemGroup>
</Project>