[NotYoojun]

Summary

• Packaging: the NuGet package is now produced by msbuild -t:Pack from source/iNKORE.UI.WPF.Modern.nuspec instead of by hand. The layout is the same as 0.10.2.1 (net452, net6.0-windows10.0.18362, net6.0-windows7.0), with two fixes:

  • translations now work on .NET 6+ too; the hand-made package had none there, so those apps only got English. Resource.Embedder embeds them in the DLLs on every target, as it already did on .NET Framework, so consumers get no culture folders in their output;
  • iNKORE.UI.WPF.dll and System.ValueTuple.dll are no longer duplicated in lib/net452.

• Versioning: the version comes from MSBuild. VersionPrefix in Directory.Build.props is used for local and CI builds; releases pass -p:Version from the tag. The iNKORE.UI.WPF version is set once, in Directory.Build.targets.

• build.yml: runs on PRs (after approval on the pr-build environment), on v* tags and by hand. It builds the solution, packs, zips the Gallery and runs tests/Package:

  • checks on the package layout (including no culture folders), dependencies and versions;
  • WPF consumer apps on net8.0-windows, net8.0-windows10.0.19041.0 and net48, built with both dotnet build and MSBuild, then run. They check the zh-TW strings, and that the output has no culture folders.

  The nupkg and iNKORE.UI.WPF.Modern.Gallery@<version>.zip are uploaded unwrapped (archive: false), so each artifact downloads as the file itself.

• release.yml: publishing a GitHub release for a v* tag, after approval on the nuget environment, pushes that tag build's nupkg to NuGet.org (Trusted Publishing) and attaches the nupkg and Gallery zip to the release.

• Actions: every action is pinned to a commit SHA, with its version in a comment. Dependabot (.github/dependabot.yml) keeps them up to date in one grouped PR a week.

• Resources: renamed the gd-gb / ca-Es-VALENCIA resx files to their standard culture casing, gd-GB and ca-ES-valencia.

Releasing

1. Push a tag vX.Y.Z; Build runs automatically.
2. Create the GitHub release for that tag, write the notes, publish.
3. Approve the nuget deployment.

Notes

• build.yml has passed on this PR. release.yml only runs when a release is published, so the first release will be its first run.
• After merging, turn on Settings → Actions → "Require actions to be pinned to a full-length commit SHA".
• Known issue, also in 0.10.2.1, to be fixed separately: apps on plain net*-windows resolve lib/net6.0-windows7.0, where the system accent and theme don't work, because the DLL needs Microsoft.Windows.SDK.NET.
• NU5125 (licenseUrl) during pack is expected.

Tested locally:

• pack, and the package contents compared against 0.10.2.1;
• consumer apps on all three TFMs, built with dotnet build and MSBuild: the zh-TW strings load from the embedded resources, and no culture folders appear in the output;
• the structure test rejects a package that still has culture folders.