Centralize and fix assembly versioning (#1704)

Add src/Directory.Build.props to set AssemblyVersion and FileVersion
consistently across all library projects:

- AssemblyVersion is pinned to 4.0.0.0 (major only). Because OpenCvSharp
  is a strong-named assembly, changing AssemblyVersion on every release
  would break .NET Framework consumers that lack binding redirects.

- FileVersion is also pinned to 4.0.0.0. The date-based 4th component
  used in NuGet package versions (e.g. 20260530) exceeds the 65535
  per-component limit of the Windows FILEVERSION PE resource, so it
  cannot be used directly.

- InformationalVersion is left to the .NET SDK default, which sets it
  to the full $(Version) string including pre-release suffix and commit
  SHA (e.g. "4.13.0.20260530-beta+<sha>"). This is the human-readable
  version visible in file properties ("Product version") and most tooling,
  and is automatically correct whenever `dotnet pack -p:Version=...` is used.

Remove the now-redundant hardcoded AssemblyVersion/FileVersion entries
from OpenCvSharp.csproj, OpenCvSharp.Extensions.csproj, and
OpenCvSharp.WpfExtensions.csproj.

OpenCvSharp.Analyzers.csproj is intentionally unchanged; it already pins
to 1.0.0.0 at the project level with an explanatory comment.

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>

Author: shimat

docs/issue-backlog.md

@@ -9,7 +9,7 @@ Check off items as they are resolved.
 
 ## ✅ Quick wins (small, self-contained fixes)
 
-### [ ] #1766 — IL3000 warning with PublishTrimmed / PublishAoT
+### [x] #1766 — IL3000 warning with PublishTrimmed / PublishAoT
 
 - **State**: closed (stale)
 - **URL**: https://github.com/shimat/opencvsharp/issues/1766
@@ -23,9 +23,10 @@ Check off items as they are resolved.
 
 - **State**: closed (stale)
 - **URL**: https://github.com/shimat/opencvsharp/issues/1704
-- **Root cause**: `AssemblyVersion` and `FileVersion` in the managed assemblies are not aligned with the NuGet package version, which breaks Windows Installer upgrade detection.
-- **Fix**: Set `<AssemblyVersion>` and `<FileVersion>` to `$(Version)` in `Directory.Build.props`.
-- **Effort**: Low
+- **Root cause**: `AssemblyVersion` and `FileVersion` were not aligned with the NuGet package version. The csproj now has them hardcoded to `4.13.0.0`, so the `0.0.0.0` symptom may already be resolved. The remaining issue is that these values must be updated manually on each release.
+- **Note**: Because OpenCvSharp is a strong-named assembly (`SignAssembly=true`), bumping `AssemblyVersion` on every release would be a breaking change for .NET Framework consumers (binding redirects required). The recommended approach is to keep `AssemblyVersion` pinned to the major version (e.g. `4.0.0.0`) and only align `FileVersion` / `InformationalVersion` with the NuGet package version automatically via CI.
+- **Fix**: Keep `AssemblyVersion` at `4.0.0.0` (major-pinned); automate `FileVersion` and `InformationalVersion` from `$(Version)` in the release pipeline.
+- **Effort**: Low–Medium
 
 ---
 

src/Directory.Build.props

@@ -0,0 +1,24 @@
+<Project>
+  <PropertyGroup>
+    <!--
+      AssemblyVersion is pinned to the major version (4.0.0.0) to avoid breaking
+      strong-named binding for .NET Framework consumers. Bumping AssemblyVersion on
+      every release would require consumers to add binding redirects in app.config,
+      which is a breaking change.
+
+      FileVersion is also pinned to 4.0.0.0 because the date-based 4th component
+      used in NuGet package versions (e.g. 4.13.0.20260530) exceeds the 65535
+      per-component limit of the Windows FILEVERSION PE resource.
+
+      InformationalVersion is NOT set here; the .NET SDK automatically populates it
+      with $(Version) (e.g. "4.13.0.20260530-beta+<commitsha>") at pack/build time,
+      which is the human-readable version visible in file properties ("Product version")
+      and most tooling.
+
+      Individual projects may override these values when they have specific requirements
+      (e.g. OpenCvSharp.Analyzers pins to 1.0.0.0 independently).
+    -->
+    <AssemblyVersion>4.0.0.0</AssemblyVersion>
+    <FileVersion>4.0.0.0</FileVersion>
+  </PropertyGroup>
+</Project>

src/OpenCvSharp.Extensions/OpenCvSharp.Extensions.csproj

@@ -20,9 +20,6 @@
     <RepositoryUrl>https://github.com/shimat/opencvsharp.git</RepositoryUrl>
     <RepositoryType>git</RepositoryType>
     <SymbolPackageFormat>snupkg</SymbolPackageFormat>
-    <AssemblyVersion>4.13.0.0</AssemblyVersion>
-    <FileVersion>4.13.0.0</FileVersion>
-    
     <!-- NuGet Package Metadata -->
     <Title>OpenCvSharp GDI+ extension library.</Title>
     <Authors>shimat</Authors>

src/OpenCvSharp.WpfExtensions/OpenCvSharp.WpfExtensions.csproj

@@ -26,8 +26,6 @@
     <PublishRepositoryUrl>true</PublishRepositoryUrl>
     <IncludeSymbols>true</IncludeSymbols>
     <SymbolPackageFormat>snupkg</SymbolPackageFormat>
-    <AssemblyVersion>4.13.0.0</AssemblyVersion>
-    <FileVersion>4.13.0.0</FileVersion>
     <GeneratePackageOnBuild>false</GeneratePackageOnBuild>
     <PackageReadmeFile>README.managed.md</PackageReadmeFile>
   </PropertyGroup>

src/OpenCvSharp/OpenCvSharp.csproj

@@ -21,9 +21,6 @@
     <RepositoryUrl>https://github.com/shimat/opencvsharp.git</RepositoryUrl>
     <RepositoryType>git</RepositoryType>
     <SymbolPackageFormat>snupkg</SymbolPackageFormat>
-    <AssemblyVersion>4.13.0.0</AssemblyVersion>
-    <FileVersion>4.13.0.0</FileVersion>
-    
     <!-- NuGet Package Metadata -->
     <Title>OpenCvSharp core library. A package of separate native bindings for your OS is required.</Title>
     <Authors>shimat</Authors>