Merge branch 'dev' of github.com:FritzAndFriends/BlazorWebFormsComponents into dev

Author: csharpfritz

.ai-team/agents/colossus/history.md

@@ -34,3 +34,5 @@ Added 9 smoke tests and 9 interaction tests for M7 sample pages: GridView Select
 
  Team update (2026-02-24): Menu auto-ID pattern  Menu now auto-generates IDs, JS interop crash fixed  decided by Cyclops
  Team update (2026-02-24): M8 scope excludes version bump to 1.0 and release  decided by Jeffrey T. Fritz
+
+ Team update (2026-02-25): Deployment pipeline patterns established  compute Docker version with nbgv before build, gate on secrets, dual NuGet publishing  decided by Forge

.ai-team/agents/cyclops/history.md

@@ -72,3 +72,5 @@ Audited 13 controls. Found: AccessKey/ToolTip missing from base class (universal
 - **Shared PagerSettings sub-component:** Created `PagerSettings` class (plain C# POCO, not a Blazor component) with all 12 Web Forms PagerSettings properties (Mode, PageButtonCount, First/Last/Next/PreviousPageText, image URLs, Position, Visible). Created `PagerPosition` enum in `Enums/` (PagerButtons already existed). Created `IPagerSettingsContainer` interface in `Interfaces/`. Created `UiPagerSettings` abstract base component following the `UiTableItemStyle` CascadingParameter pattern but for settings instead of styles. Created 3 concrete sub-component pairs: `GridViewPagerSettings`, `FormViewPagerSettings`, `DetailsViewPagerSettings` — each inherits `UiPagerSettings` and uses `[CascadingParameter(Name = "ParentXxx")]` to set properties on the parent's `PagerSettings` instance. Wired into GridView, FormView, DetailsView: added `IPagerSettingsContainer` to each control's interface list, added `PagerSettings` property + `PagerSettingsContent` RenderFragment parameter, rendered `@PagerSettingsContent` inside existing `<CascadingValue>` block. Key files: `Enums/PagerPosition.cs`, `PagerSettings.cs`, `Interfaces/IPagerSettingsContainer.cs`, `UiPagerSettings.cs`, `GridViewPagerSettings.razor(.cs)`, `FormViewPagerSettings.razor(.cs)`, `DetailsViewPagerSettings.razor(.cs)`.
  Team update (2026-02-24): Substitution/Xml formally deferred  no implementation needed  decided by Beast
  Team update (2026-02-24): M8 scope excludes version bump to 1.0 and release  decided by Jeffrey T. Fritz
+
+ Team update (2026-02-25): Deployment pipeline patterns established  compute Docker version with nbgv before build, gate on secrets, dual NuGet publishing  decided by Forge

.ai-team/agents/forge/history.md

@@ -89,3 +89,23 @@ Planned M7: "Control Depth & Navigation Overhaul" — 51 work items targeting ~1
  Team update (2026-02-24): Substitution/Xml formally deferred in status.md and README  decided by Beast
  Team update (2026-02-24): M8 scope excludes version bump to 1.0 and release  decided by Jeffrey T. Fritz
  Team update (2026-02-24): PagerSettings shared sub-component created for GridView/FormView/DetailsView  decided by Cyclops
+
+### Summary: v0.14 Deployment Pipeline Fixes (2026-02-25)
+
+Fixed three deployment pipeline issues on `fix/deployment-workflows` branch:
+
+- **Docker version computation:** `.dockerignore` excludes `.git`, so nbgv can't run inside the Docker build. Solution: compute version with `nbgv get-version` in the workflow BEFORE Docker build, pass as `ARG VERSION` into the Dockerfile, use `-p:Version=$VERSION -p:InformationalVersion=$VERSION` in both `dotnet build` and `dotnet publish`. This pattern (compute outside, inject via build-arg) is the standard approach when `.git` isn't available inside the build context.
+- **Azure App Service webhook:** Added a `curl -sf -X POST` step gated on `AZURE_WEBAPP_WEBHOOK_URL` secret. Uses `|| echo "::warning::..."` fallback so the workflow doesn't fail if the webhook is unavailable. The webhook URL comes from Azure Portal → App Service → Deployment Center.
+- **nuget.org publishing:** Added a second push step after the existing GitHub Packages push, gated on `NUGET_API_KEY` secret. Both pushes use `--skip-duplicate` for idempotency.
+
+**Key file paths:**
+- `.github/workflows/deploy-server-side.yml` — Docker build + push + Azure webhook
+- `.github/workflows/nuget.yml` — NuGet pack + push (GitHub Packages + nuget.org)
+- `samples/AfterBlazorServerSide/Dockerfile` — server-side demo container
+
+**Patterns established:**
+- Secret-gated workflow steps use `if: ${{ secrets.SECRET_NAME != '' }}` for graceful fallback when secrets aren't configured
+- Docker images are tagged with version number (from nbgv), `latest`, and commit SHA
+- Version is computed once via nbgv and shared via GitHub Actions step outputs (`steps.nbgv.outputs.version`)
+
+ Team update (2026-02-25): Deployment pipeline patterns established  compute Docker version with nbgv before build, gate on secrets, dual NuGet publishing  decided by Forge

.ai-team/decisions.md

@@ -462,12 +462,11 @@ Suggested timeline:
 **What:** `Label` currently inherits `BaseWebFormsComponent` but Web Forms `Label` inherits from `WebControl`. This means Label is missing all 9 style properties (CssClass, BackColor, ForeColor, Font, etc.). Also consider `AssociatedControlID` to render `<label for="...">` instead of `<span>`.
 **Why:** Label is one of the most commonly used controls. Missing style properties break migration for any page that styles its Labels.
 
-### 2026-02-23: Substitution and Xml remain permanently deferred
+### 2026-02-25: Substitution and Xml permanently deferred (consolidated)
 
 **By:** Beast
-**What:** Both controls are tightly coupled to server-side ASP.NET infrastructure: Substitution depends on the output caching pipeline (`HttpResponse.WriteSubstitution`); Xml depends on XSLT transformation. Neither maps to Blazor's component model.
-**Recommendation:** Document migration alternatives in `DeferredControls.md`. Substitution → Blazor component lifecycle. Xml → convert XML to C# objects and use Blazor templates.
-**Why:** Reinforces and formalizes the Sprint 3 deferral decision with specific migration guidance.
+**What:** Both controls are tightly coupled to server-side ASP.NET infrastructure: Substitution depends on the output caching pipeline; Xml depends on XSLT transformation. Neither maps to Blazor's component model. Both are formally marked as deferred in status.md and README.md. DeferredControls.md contains migration guidance: Substitution -> Blazor component lifecycle; Xml -> convert XML to C# objects and use Blazor templates.
+**Why:** Architecturally incompatible with Blazor. Marking as deferred (not "Not Started") accurately communicates they will not be implemented.
 
 ### 2026-02-23: Chart Type Gallery documentation convention
 
@@ -1344,12 +1343,6 @@ All P2 features (WI-47 through WI-52) have been tested with 32 bUnit tests acros
 
 Team should be aware that Login/ChangePassword/CreateUserWizard BaseStyledComponent inheritance was already in place — WI-52's implementation may have been a no-op or only required template changes to wire `Style`/`CssClass` to the outer element.
 
-### Substitution and Xml formally deferred
-
-**By:** Beast
-**What:** Substitution and Xml controls are now formally marked as "⏸️ Deferred" (not "Not Started") in status.md. DeferredControls.md already had migration guidance; status.md and README.md now reflect the permanent deferral. Chart is marked as fully complete with no "Phase 1" qualifier.
-**Why:** These two controls are architecturally incompatible with Blazor (Substitution relies on output caching; Xml relies on XSLT transforms). Marking them as deferred rather than "Not Started" accurately communicates that they will not be implemented, and clears the remaining work count to 0.
-
 # Decision: M7 Integration Tests Added (WI-39 + WI-40)
 
 **Author:** Colossus
@@ -1924,3 +1917,8 @@ Removed the `@rendermode InteractiveServer` directive. No other sample page in t
 - `dotnet build samples/AfterBlazorClientSide/ --configuration Release` — ✅ passes
 - `dotnet build samples/AfterBlazorServerSide/ --configuration Release` — ✅ passes
 - `dotnet test src/BlazorWebFormsComponents.Test/ --no-restore` — ✅ passes
+
+### 2026-02-25: Deployment pipeline patterns for Docker versioning, Azure webhook, and NuGet publishing
+**By:** Forge
+**What:** Established three CI/CD patterns: (1) Compute version with nbgv outside Docker build and inject via build-arg, since .dockerignore excludes .git. (2) Gate optional deployment steps on repository secrets with `if: ${{ secrets.SECRET_NAME != '' }}` so workflows don't fail when secrets aren't configured. (3) Dual NuGet publishing  always push to GitHub Packages, conditionally push to nuget.org.
+**Why:** The .dockerignore excluding .git is a structural constraint that won't change (it's correct for build performance). Secret-gating ensures the workflows work in forks and PRs where secrets aren't available. Dual NuGet publishing gives us private (GitHub) and public (nuget.org) distribution without duplicating the pack step. These patterns should be followed for any future workflow additions.

.github/workflows/deploy-server-side.yml

@@ -29,6 +29,19 @@ jobs:
         with:
           fetch-depth: 0
 
+      - name: Setup .NET for version computation
+        uses: actions/setup-dotnet@v4
+        with:
+          dotnet-version: '10.0.x'
+
+      - name: Compute version with nbgv
+        id: nbgv
+        run: |
+          dotnet tool install --global nbgv
+          VERSION=$(nbgv get-version -v NuGetPackageVersion)
+          echo "version=$VERSION" >> "$GITHUB_OUTPUT"
+          echo "Computed version: $VERSION"
+
       - name: Log in to GitHub Container Registry
         uses: docker/login-action@v3
         with:
@@ -45,6 +58,17 @@ jobs:
           context: .
           file: samples/AfterBlazorServerSide/Dockerfile
           push: true
+          build-args: |
+            VERSION=${{ steps.nbgv.outputs.version }}
           tags: |
             ${{ env.REGISTRY }}/${{ env.IMAGE_NAME }}:latest
+            ${{ env.REGISTRY }}/${{ env.IMAGE_NAME }}:${{ steps.nbgv.outputs.version }}
             ${{ env.REGISTRY }}/${{ env.IMAGE_NAME }}:${{ github.sha }}
+
+      - name: Trigger Azure App Service deployment
+        if: ${{ secrets.AZURE_WEBAPP_WEBHOOK_URL != '' }}
+        run: |
+          curl -sf -X POST "${{ secrets.AZURE_WEBAPP_WEBHOOK_URL }}" \
+            -H "Content-Length: 0" \
+            --max-time 60 \
+            || echo "::warning::Azure webhook call failed — the App Service may need to be updated manually"

.github/workflows/nuget.yml

@@ -40,6 +40,10 @@ jobs:
       - name: Push to GitHub Packages
         run: dotnet nuget push ./nupkg/*.nupkg --source "https://nuget.pkg.github.com/${{ github.repository_owner }}/index.json" --api-key ${{ secrets.GITHUB_TOKEN }} --skip-duplicate
 
+      - name: Push to nuget.org
+        if: ${{ secrets.NUGET_API_KEY != '' }}
+        run: dotnet nuget push ./nupkg/*.nupkg --source "https://api.nuget.org/v3/index.json" --api-key ${{ secrets.NUGET_API_KEY }} --skip-duplicate
+
       - name: Upload NuGet package artifact
         uses: actions/upload-artifact@v4
         with:

samples/AfterBlazorServerSide/Dockerfile

@@ -6,6 +6,7 @@ EXPOSE 80
 ENV ASPNETCORE_HTTP_PORTS=80
 
 FROM mcr.microsoft.com/dotnet/sdk:10.0 AS build
+ARG VERSION=0.0.0
 WORKDIR /src
 COPY ["Directory.Build.props", "./"]
 COPY ["samples/AfterBlazorServerSide/AfterBlazorServerSide.csproj", "samples/AfterBlazorServerSide/"]
@@ -14,10 +15,10 @@ COPY ["samples/SharedSampleObjects/SharedSampleObjects.csproj", "samples/SharedS
 RUN dotnet restore "samples/AfterBlazorServerSide/AfterBlazorServerSide.csproj"
 COPY . .
 WORKDIR "/src/samples/AfterBlazorServerSide"
-RUN dotnet build "AfterBlazorServerSide.csproj" -c Release -o /app/build
+RUN dotnet build "AfterBlazorServerSide.csproj" -c Release -o /app/build -p:Version=$VERSION -p:InformationalVersion=$VERSION
 
 FROM build AS publish
-RUN dotnet publish "AfterBlazorServerSide.csproj" -c Release -o /app/publish
+RUN dotnet publish "AfterBlazorServerSide.csproj" -c Release -o /app/publish -p:Version=$VERSION -p:InformationalVersion=$VERSION
 
 FROM base AS final
 WORKDIR /app