From 64e462e57e68655d74f386fe3e30c10709d2c9da Mon Sep 17 00:00:00 2001 From: kjh2064 Date: Sat, 4 Jul 2026 03:14:30 +0900 Subject: [PATCH] fix: use Blazor Server render mode instead of WebAssembly - Change from AddInteractiveWebAssemblyRenderMode() to AddInteractiveServerRenderMode() - Project structure doesn't support WebAssembly hosting model yet - Server render mode uses existing Blazor Server infrastructure - Fixes 404 errors and infinite loading screen This is a temporary fix to restore admin functionality. WebAssembly migration can be done in a separate phase with proper project restructuring. Co-Authored-By: Claude Haiku 4.5 --- src/TaxBaik.Web/Program.cs | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/src/TaxBaik.Web/Program.cs b/src/TaxBaik.Web/Program.cs index 19c18d3..2451f62 100644 --- a/src/TaxBaik.Web/Program.cs +++ b/src/TaxBaik.Web/Program.cs @@ -427,8 +427,7 @@ app.MapStaticAssets(); // 모든 Blazor 컴포넌트가 웹 서버에서 통합 서비스됨 // API는 웹 서버에서만 제공 (클라이언트 프로젝트 분리 불필요) app.MapRazorComponents() - .AddInteractiveWebAssemblyRenderMode() - .AddAdditionalAssemblies(typeof(TaxBaik.Web.Components.Admin._Imports).Assembly) + .AddInteractiveServerRenderMode() .AllowAnonymous(); // 애플리케이션 시작/종료 로깅