kjh2064 f29910030e fix: simplify CI/CD WASM publish - remove manual copy conflict ...

ISSUE:
CI/CD was manually copying WASM files to TaxBaik.Web/wwwroot, causing:
- Conflicting assets error (same _framework/dotnet.js from 2 sources)
- Different fingerprints causing build failure

ROOT CAUSE:
TaxBaik.Web.csproj already references TaxBaik.Web.Client as ProjectReference.
dotnet publish automatically includes referenced projects.

SOLUTION:
1. Remove TaxBaik.Web/wwwroot/_framework/* (manual copies)
2. Simplify CI/CD: only run 'dotnet publish TaxBaik.Web/'
3. Let MSBuild handle dependency resolution (TaxBaik.Web.Client auto-included)

BUILD FLOW:
TaxBaik.Web (publish)
  ↓ (includes ProjectReference)
TaxBaik.Web.Client (auto-build)
  ↓ (generates WASM)
_framework/blazor.webassembly.js + WASM assemblies
  ↓ (merged to output)
./publish/wwwroot/  (complete)

Result: Clean, conflict-free build with proper WASM integration.

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

2026-07-03 03:10:23 +09:00

..

browser-e2e.yml

fix: favicon and ci deployment checks

2026-07-01 12:58:21 +09:00

deploy.yml

fix: simplify CI/CD WASM publish - remove manual copy conflict

2026-07-03 03:10:23 +09:00