Fix Windows portable release workflow

Author: masarray

.github/workflows/release-package.yml

@@ -49,6 +49,9 @@ jobs:
         with:
           dotnet-version: 8.0.x
 
+      - name: Show .NET SDK selection
+        run: dotnet --info
+
       - name: Resolve release version
         id: version
         shell: pwsh

docs/RELEASE_NOTES_v1.2.1.md

@@ -0,0 +1,21 @@
+# Release Notes — v1.2.1-landing-and-release-fix
+
+This maintenance release improves the public landing page and fixes the Windows portable release workflow.
+
+## Highlights
+
+- Premium GitHub Pages landing page refresh with cleaner typography, stronger screenshot presentation, app-icon branding, favicon, scroll reveal animation, and product trailer section.
+- Windows portable release script now avoids command-line `AssemblyName` overrides so referenced projects keep their own assembly names during restore and publish.
+- The release workflow pins the repository to the .NET 8 SDK through `global.json` and prints `dotnet --info` for easier CI diagnosis.
+- The portable package remains a self-contained single-EXE app payload by default.
+
+## Recommended package
+
+Download the portable Windows package from GitHub Releases:
+
+```text
+ProcessBusInsight-v1.2.1-landing-and-release-fix-win-x64-portable.zip
+SHA256SUMS.txt
+```
+
+Npcap is required on the target Windows machine and is not bundled with the application.

docs/RELEASE_PACKAGING.md

@@ -46,3 +46,7 @@ Manual inputs:
 ## Runtime prerequisite
 
 Npcap is required on the target Windows machine and is not bundled in the repository.
+
+## CI restore note
+
+The portable release script performs a runtime-specific restore and then publishes with `--no-restore`. It intentionally does not pass `/p:AssemblyName=...` on the command line because MSBuild global properties also flow into referenced projects. Passing the same assembly name into the whole project graph can make NuGet restore report `Ambiguous project name`.

global.json

@@ -0,0 +1,7 @@
+{
+  "sdk": {
+    "version": "8.0.100",
+    "rollForward": "latestFeature",
+    "allowPrerelease": false
+  }
+}

scripts/publish-windows-portable.ps1

@@ -35,8 +35,23 @@ Remove-Item -LiteralPath $publishDir -Recurse -Force -ErrorAction SilentlyContin
 Remove-Item -LiteralPath $stageDir -Recurse -Force -ErrorAction SilentlyContinue
 New-Item -ItemType Directory -Path $publishDir, $stageDir, $releaseDir | Out-Null
 
+$resolvedProjectPath = (Resolve-Path $ProjectPath).Path
+
+# Runtime-specific restore is done explicitly, then publish runs with --no-restore.
+# Do not pass /p:AssemblyName from the command line. MSBuild global properties flow into
+# project references too, which can make every project in the graph look like the same
+# project name to NuGet restore and trigger: Ambiguous project name 'ProcessBusInsight'.
+$restoreArgs = @(
+    "restore", $resolvedProjectPath,
+    "-r", $Runtime,
+    "/p:ContinuousIntegrationBuild=true"
+)
+
+dotnet @restoreArgs
+
 $publishArgs = @(
-    "publish", $ProjectPath,
+    "publish", $resolvedProjectPath,
+    "--no-restore",
     "-c", $Configuration,
     "-r", $Runtime,
     "-o", $publishDir,
@@ -46,7 +61,7 @@ $publishArgs = @(
     "/p:PublishTrimmed=false",
     "/p:DebugType=None",
     "/p:DebugSymbols=false",
-    "/p:AssemblyName=$AppName"
+    "/p:ErrorOnDuplicatePublishOutputFiles=true"
 )
 
 if ($selfContained) {