From c25bd820c3d434da95a7d103f1527e7e0831e5c3 Mon Sep 17 00:00:00 2001
From: iamboss <iamboss@superhightech.com.tw>
Date: Sun, 26 Jul 2026 18:00:18 +0800
Subject: [PATCH] build(Hi.WpfPlus): start the 3.2 package line and restart
 VersionBuild

The 3.1 line ends at Hi.WpfPlus 3.1.143 -- tag v3.1.143, part of the aligned
hinc-suite/3.1.175 set. master now produces 3.2 and VersionBuild restarts at 0,
so the first published 3.2 package is 3.2.1: IncrementPackageID.targets bumps
before the build, not after it.

The 3.1.158 stamp this replaces was a local increment from a deploy run whose
upload step is commented out, so it never reached the feed and nothing depends on
it. Fixes for customers pinned to 3.1 come off the support/3.1 branch.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
---
 Hi.WpfPlus.csproj | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/Hi.WpfPlus.csproj b/Hi.WpfPlus.csproj
index cb4ff51..ea35e92 100644
--- a/Hi.WpfPlus.csproj
+++ b/Hi.WpfPlus.csproj
@@ -12,8 +12,8 @@
 			HiAPI wpf canvas.
 		</Description>
     <Configurations>Debug;Release</Configurations>
-    <VersionBuild>157</VersionBuild>
-    <VersionPrefix>3.1.$(VersionBuild)</VersionPrefix>
+    <VersionBuild>0</VersionBuild>
+    <VersionPrefix>3.2.$(VersionBuild)</VersionPrefix>
     <PackageId>Hi.WpfPlus</PackageId>
     <PackageTags>HiAPI</PackageTags>
     <RuntimeIdentifiers>win-x64</RuntimeIdentifiers>
@@ -29,7 +29,7 @@
     <ProjectReference Include="..\HiDisp\HiDisp.csproj" />
   </ItemGroup>
   <ItemGroup Condition="'$(Configuration)'=='Release'">
-    <PackageReference Include="HiDisp" Version="3.1.*" />
+    <PackageReference Include="HiDisp" Version="3.2.*" />
   </ItemGroup>
   <PropertyGroup Condition="'$(Configuration)'=='Release'">
     <IsIgnoreObfuscar>true</IsIgnoreObfuscar>