Integrate GitVersion and add version provider abstraction
- Added GitVersion for semantic versioning and build metadata - Introduced IVersionProvider and VersionProvider for UI-friendly version display - MainForm now uses IVersionProvider for version label - Registered VersionProvider in DI container - Improved logging: filtered out AutoMapper license logs - General code cleanup in Program.cs
This commit is contained in:
parent
5cb491f1b5
commit
509d5357a8
8 changed files with 154 additions and 44 deletions
12
imagecatalog/GitVersion.README.md
Normal file
12
imagecatalog/GitVersion.README.md
Normal file
|
|
@ -0,0 +1,12 @@
|
|||
This project uses GitVersion (via `GitVersion.MsBuild`) to compute semantic version numbers during build.
|
||||
|
||||
How it works:
|
||||
- The `GitVersion.MsBuild` package runs during `dotnet build` and sets MSBuild properties such as `Version`, `AssemblyVersion`, `FileVersion`, and `InformationalVersion`.
|
||||
- The repository is configured via `.gitversion.yml` at the repo root. Tags and branch names drive the generated semantic version.
|
||||
|
||||
Usage notes:
|
||||
- Create annotated tags like `v1.2.3` or `1.2.3` to mark releases.
|
||||
- In CI, ensure the Git clone includes tags and history (no shallow single-commit clones).
|
||||
- The UI should read `AssemblyInformationalVersion` for a friendly version string; fall back to `FileVersion` or `AssemblyName.Version` if needed.
|
||||
|
||||
See https://gitversion.net for more configuration options.
|
||||
Loading…
Add table
Add a link
Reference in a new issue