Blazor lets you build interactive web UIs entirely in C#, eliminating JavaScript context-switching
Components are .razor files mixing HTML + C# logic, self-contained and reusable
Two-way binding with @bind syncs form fields to C# properties automatically
Blazor Server runs C# on the server with SignalR; WebAssembly runs it in the browser
Biggest mistake: thinking Blazor Server and WebAssembly need different coding patterns — they share the same component model
Plain-English First
Imagine your TV remote. Normally you need a special remote (JavaScript) to change the channel on a specific TV (the browser). Blazor is like a universal remote that lets you use the same language you already know (C#) to control the browser directly. You stop learning two different languages and just use the one you love — C# does the clicking, the form-filling, and the live updates, all without writing a single line of JavaScript.
Blazor Components — The Single File That Does Everything
In Blazor, a component is a .razor file that contains three things in one place: HTML markup that defines the structure, a @code block that holds C# logic, and optional CSS isolation. This is the core mental model shift — stop thinking in terms of separate HTML files, JavaScript files, and C# controllers. A Blazor component is a self-contained unit of UI.
Every component has a lifecycle. When Blazor first renders a component it calls OnInitializedAsync — this is where you load data from an API or a database. After every parameter change, OnParametersSetAsync fires. The framework tracks which properties are bound to the UI and re-renders only the affected DOM nodes when those values change.
Components are also reusable by design. You define a ProductCard component once and drop <ProductCard Product="myProduct" /> anywhere in your app. Parameters flow down from parent to child via [Parameter] attributes, keeping your UI predictable and testable.
The key reason Blazor components beat raw Razor Pages for interactive UIs is that a Razor Page requires a full HTTP round-trip to reflect any change. A Blazor component updates in-place, in memory, without reloading the page — just like a React component does, but entirely in C#.
ProductCard.razorCSHARP
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
@* ProductCard.razor — a reusable component that displays one product *@
@* Drop it anywhere with: <ProductCardProduct="someProduct"OnAddToCart="HandleAdd" /> *@
<div class="product-card">
<h3>@Product.Name</h3>
<p class="price">@Product.Price.ToString("C")</p> @* 'C' formats as currency *@
@if (Product.StockCount > 0)
{
<!-- Buttonis only rendered when stock exists -->
<button class="btn-primary" @onclick="AddToCart">Add to Cart</button>
}
else
{
<span class="out-of-stock">Out of Stock</span>
}
</div>
@code {
// [Parameter] marks a public property that a parent component can set
[Parameter]
public required ProductModelProduct { get; set; }
// EventCallback lets the child notify the parent without tight coupling
[Parameter]
publicEventCallback<ProductModel> OnAddToCart { get; set; }
// This method is called when the button fires its @onclick eventprivateasyncTaskAddToCart()
{
// Invoke the parent's handler and pass the product as the argumentawaitOnAddToCart.InvokeAsync(Product);
}
// Lifecycle hook — runs once after the component first rendersprotectedoverridevoidOnInitialized()
{
// Good place for lightweight sync setup (no data fetching here)Console.WriteLine($"ProductCard initialized for: {Product.Name}");
}
}
// --- ProductModel.cs (put this in your Models folder) ---publicclassProductModel
{
publicintId { get; set; }
publicstringName { get; set; } = string.Empty;
publicdecimalPrice { get; set; }
publicintStockCount { get; set; }
}
Output
Console (browser dev tools or terminal for Blazor Server):
ProductCard initialized for: Mechanical Keyboard
Rendered HTML (when StockCount > 0):
<div class="product-card">
<h3>Mechanical Keyboard</h3>
<p class="price">$129.99</p>
<button class="btn-primary">Add to Cart</button>
</div>
Pro Tip: EventCallback vs Action
Always use EventCallback<T> instead of Action<T> for component events. EventCallback automatically calls StateHasChanged on the parent after the handler runs, so the parent's UI updates without you lifting a finger. Action<T> skips that step and your UI appears to ignore the event.
Production Insight
EventCallback<T> is critical when the parent updates its own state after a child event. Without it, parents stay stale.
A common production bug: a parent shows an outdated product list after a child 'delete' event because Action<T> was used.
Rule: always prefer EventCallback<T> — it's one less thing to debug at 2 AM.
Key Takeaway
A .razor component is a self-contained unit — markup, logic, lifecycle all in one file.
Data flows down via [Parameter], events flow up via EventCallback.
This pattern mirrors React but in C# with full type safety.
Two-Way Data Binding and Real-Time Form State with @bind
One of the first things you'll want to do in any web app is connect a form field to a C# object and have changes reflect immediately — in both directions. Type in the box, the C# property updates. Change the C# property in code, the box updates. Blazor calls this two-way binding and it's powered by the @bind directive.
Under the hood, @bind on an <input> is syntactic sugar for wiring up the value attribute to a property AND attaching an onchange event handler that writes the new value back. You can be explicit about timing using @bind:event="oninput" if you want the property to update on every keystroke rather than on blur.
This matters for real-world scenarios like live search boxes, character counters, or dependent dropdowns where changing one field should immediately filter the options in another. Without two-way binding you'd write the same plumbing logic yourself every time.
Beyond simple inputs, EditForm is Blazor's built-in form component that wraps DataAnnotations validation. You get client-side validation for free from the same [Required] and [Range] attributes you already use on your models — no duplicate validation rules in JavaScript.
CheckoutForm.razorCSHARP
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
@page "/checkout"
@* This page demonstrates two-way binding, live character count, and form validation *@
<h2>Checkout</h2>
@* EditForm links the form to the C# model and handles validation lifecycle *@
<EditFormModel="order"OnValidSubmit="HandleValidSubmit">
<DataAnnotationsValidator /> @* Reads [Required], [Range] etc. from OrderModel *@
<ValidationSummary /> @* Displays all current validation errors *@
<div class="form-group">
<label>FullName</label>
@* @bind wires value <-> order.CustomerName two-ways *@
<InputText @bind-Value="order.CustomerName"class="form-control" />
<ValidationMessageFor="@(() => order.CustomerName)" />
</div>
<div class="form-group">
<label>OrderNotes (@notesRemaining chars remaining)</label>
@* @bind:event="oninput" updates on EVERY keystroke, not just on blur *@
<textarea @bind="order.Notes" @bind:event="oninput"class="form-control" maxlength="200"></textarea>
</div>
<div class="form-group">
<label>Quantity</label>
<InputNumber @bind-Value="order.Quantity"class="form-control" />
<ValidationMessageFor="@(() => order.Quantity)" />
</div>
<button type="submit"class="btn-primary">PlaceOrder</button>
</EditForm>
@if (orderConfirmed)
{
<p class="success">Order placed for @order.CustomerName! Qty: @order.Quantity</p>
}
@code {
// The model the form is bound to — all fields live hereprivateOrderModel order = new();
privatebool orderConfirmed = false;
// Computed property — recalculates every render cycle automaticallyprivateint notesRemaining => 200 - (order.Notes?.Length ?? 0);
// OnValidSubmit only fires when ALL DataAnnotations passprivateasyncTaskHandleValidSubmit()
{
// In a real app you'd call an API here
await Task.Delay(500); // Simulate a network call
orderConfirmed = true;
}
}
// --- OrderModel.cs ---usingSystem.ComponentModel.DataAnnotations;
publicclassOrderModel
{
[Required(ErrorMessage = "Name is required")]
[StringLength(100, ErrorMessage = "Name too long")]
publicstringCustomerName { get; set; } = string.Empty;
publicstring? Notes { get; set; }
[Range(1, 99, ErrorMessage = "Quantity must be between 1 and 99")]
publicintQuantity { get; set; } = 1;
}
Output
When user types in Name field and clicks Place Order with empty name:
Name is required
When form is valid and submitted:
Order placed for Jane Smith! Qty: 3
As user types in Notes textarea (live):
Order Notes (183 chars remaining) <- updates on every keystroke
Watch Out: @bind vs @bind-Value
Use @bind on native HTML elements like <input> and <textarea>. Use @bind-Value (capital V) on Blazor component inputs like <InputText> and <InputNumber>. Mixing them up causes a silent compile warning and the two-way sync breaks — your model updates but the UI doesn't reflect changes made in code.
Production Insight
Using @bind:event="oninput" for a large form with many fields can cause noticeable lag because every keystroke triggers a full render cycle.
If you have 20+ input fields, consider debouncing the updates or using onchange for most fields.
Rule: use oninput only for live-feedback fields like search autocomplete or character counts.
Key Takeaway
@bind is syntactic sugar for value + onchange.
Use @bind:event="oninput" for keystroke-level reactivity.
EditForm + DataAnnotations = validation without JavaScript.
Performance trap: too many oninput bindings can slow rendering.
Blazor Server vs Blazor WebAssembly — Choosing the Right Hosting Model
This is the question every Blazor developer faces first and gets wrong most often. Both hosting models use identical component syntax, so the choice is about execution environment and trade-offs, not about learning different APIs.
Blazor Server runs your C# components on the server. When a user clicks a button, a SignalR message travels from the browser to the server, the C# handler runs, the new virtual DOM diff is calculated on the server, and only the minimal HTML patch is sent back to the browser. The browser itself is just a thin rendering surface. This means startup is near-instant (no big download), you can access databases and file systems directly from component code, and your app works on browsers that don't support WebAssembly. The cost is latency sensitivity — every interaction needs a round-trip, and a server outage affects every connected user simultaneously.
Blazor WebAssembly (WASM) downloads the entire .NET runtime and your compiled DLLs to the browser on first load. After that, all component logic runs locally — zero server round-trips for UI interactions, offline capability, and it can be hosted as static files on a CDN. The trade-off is a larger initial download (typically 2-5 MB compressed) and no direct database access from component code.
A third option, Blazor United (now called Blazor Web App with Auto render mode in .NET 8+), starts components as Server for instant interactivity and then seamlessly transitions to WASM once the runtime downloads in the background — giving you the best of both.
WeatherDashboard.razorCSHARP
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
@* WeatherDashboard.razor — works identically in both Server and WASM hosting *@
@* The component code is the same; only the Program.cs setup differs *@
@page "/weather"
@inject IWeatherServiceWeatherService @* Injected service — works in both models *@
<h2>WeatherDashboard</h2>
@if (isLoading)
{
<p>Loading weather data...</p> @* Shown during async fetch *@
}
elseif (forecasts == null || !forecasts.Any())
{
<p>No forecast data available.</p>
}
else
{
<table class="weather-table">
<thead>
<tr><th>Date</th><th>Temp (°C)</th><th>Summary</th></tr>
</thead>
<tbody>
@foreach (var forecast in forecasts)
{
<tr>
<td>@forecast.Date.ToShortDateString()</td>
<td class="@GetTempCssClass(forecast.TemperatureC)">
@forecast.TemperatureC
</td>
<td>@forecast.Summary</td>
</tr>
}
</tbody>
</table>
}
<button @onclick="RefreshForecasts" disabled="@isLoading">
@(isLoading ? "Refreshing..." : "Refresh")
</button>
@code {
privateList<WeatherForecast>? forecasts;
privatebool isLoading = true;
// OnInitializedAsync is the correct hook for async data loading// It fires after the first render, preventing the UI from blockingprotectedoverrideasyncTaskOnInitializedAsync()
{
awaitLoadForecastsAsync();
}
privateasyncTaskRefreshForecasts()
{
isLoading = true;
// StateHasChanged() is NOT needed here — Blazor tracks event handlers automaticallyawaitLoadForecastsAsync();
}
privateasyncTaskLoadForecastsAsync()
{
isLoading = true;
forecasts = awaitWeatherService.GetForecastAsync(DateTime.Today, days: 5);
isLoading = false;
// For Blazor Server: the SignalR diff is sent to browser automatically after this// For Blazor WASM: the WASM runtime re-renders locally after this
}
// Helper to apply a CSS class based on temperature valueprivatestringGetTempCssClass(int tempC) => tempC switch
{
<= 0 => "temp-freezing",
<= 15 => "temp-cold",
<= 25 => "temp-mild",
_ => "temp-hot"
};
}
// --- WeatherForecast.cs ---public record WeatherForecast(DateOnlyDate, intTemperatureC, stringSummary);
Output
Initial render:
Loading weather data...
After data loads:
Weather Dashboard
Date Temp(°C) Summary
01/06/2025 22 Mild
02/06/2025 -3 Freezing <- gets CSS class 'temp-freezing'
03/06/2025 28 Hot <- gets CSS class 'temp-hot'
04/06/2025 12 Cold
05/06/2025 19 Mild
[Refresh] button
Interview Gold: The Hosting Model Question
Interviewers love asking 'When would you NOT use Blazor Server?' The honest answer: when your users have high-latency connections (mobile networks in remote areas), when you expect thousands of simultaneous users and can't afford per-connection server memory, or when you need offline support. These are real architectural trade-offs, not hypotheticals.
Production Insight
Blazor Server's per-user memory is often underestimated. Each SignalR circuit holds about 200-400 KB just for the circuit, plus state.
For 10,000 concurrent users, that's 2-4 GB just for overhead — before any business data.
Rule: profile your app's memory per circuit with dotnet counters before scaling; WASM is cheaper at scale for public apps.
Key Takeaway
Server and WASM share component code — hosting model is a deployment decision, not a coding one.
Server trades per-user memory for near-zero startup latency.
WASM trades initial download for zero latency after load.
Auto mode in .NET 8+ gives best of both for new apps.
Dependency Injection and Service Lifetimes in Blazor Components
Blazor is built on top of ASP.NET Core's dependency injection container, so you get the same AddScoped, AddTransient, and AddSingleton lifetimes — but their behaviour in Blazor is subtly different from MVC and it catches people out.
In Blazor Server, a Scoped service lives for the duration of the SignalR circuit (the user's connection), not just a single HTTP request. This means a scoped service is effectively per-user and can hold state across multiple component renders and navigations — useful for shopping carts or user preferences. A Singleton is shared across all users on the server, so be careful with mutable state there.
In Blazor WebAssembly there's only one user per browser tab, so Scoped and Singleton behave identically in practice — they both live for the app's lifetime.
The @inject directive is how you pull services into a component. You can also use the [Inject] attribute in the @code block for constructor-style injection. The critical rule: never do real work in a component's constructor. Always use OnInitializedAsync for anything that involves services, because the DI container has fully resolved all dependencies by the time that lifecycle hook fires.
ShoppingCartSidebar.razorCSHARP
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
@* ShoppingCartSidebar.razor *@
@* Demonstrates @inject, a scoped service, and reacting to external state changes *@
@inject ICartServiceCartService @* Scoped: one instance per SignalR circuit *@
@inject NavigationManagerNavManager @* Built-inBlazor service forURL navigation *@
@implements IDisposable @* We subscribe to an event, so we must unsubscribe *@
<div class="cart-sidebar">
<h4>YourCart (@cartItemCount items)</h4>
@foreach (var item in cartItems)
{
<div class="cart-item">
<span>@item.ProductName</span>
<span>x@item.Quantity</span>
<button @onclick="() => RemoveItem(item.ProductId)">Remove</button>
</div>
}
<p class="cart-total">Total: @cartTotal.ToString("C")</p>
<button @onclick="GoToCheckout"class="btn-checkout">Checkout</button>
</div>
@code {
privateList<CartItem> cartItems = new();
// Computed properties — Blazor recalculates these each render, no manual sync neededprivateint cartItemCount => cartItems.Count;
privatedecimal cartTotal => cartItems.Sum(i => i.LineTotal);
protectedoverrideasyncTaskOnInitializedAsync()
{
// Load initial cart state from the service
cartItems = awaitCartService.GetItemsAsync();
// Subscribe to cart change events from other components (e.g., ProductCard)// This allows the sidebar to update when ANY component adds a productCartService.OnCartChanged += HandleCartChanged;
}
// This handler is called by the service when cart changes from OUTSIDE this componentprivateasyncvoidHandleCartChanged()
{
cartItems = awaitCartService.GetItemsAsync();
// InvokeAsync ensures StateHasChanged is called on the correct sync context// This is CRITICAL when the callback comes from a background thread or another componentawaitInvokeAsync(StateHasChanged);
}
privateasyncTaskRemoveItem(int productId)
{
awaitCartService.RemoveItemAsync(productId);
// CartService will fire OnCartChanged, which calls HandleCartChanged above
}
privatevoidGoToCheckout()
{
NavManager.NavigateTo("/checkout");
}
// IDisposable — always unsubscribe from events to prevent memory leakspublicvoidDispose()
{
CartService.OnCartChanged -= HandleCartChanged;
}
}
// --- ICartService.cs ---publicinterfaceICartService
{
eventActionOnCartChanged;
Task<List<CartItem>> GetItemsAsync();
TaskRemoveItemAsync(int productId);
TaskAddItemAsync(ProductModel product);
}
// --- CartItem.cs ---public record CartItem(intProductId, stringProductName, intQuantity, decimalUnitPrice)
{
publicdecimalLineTotal => Quantity * UnitPrice;
}
Output
Cart sidebar renders:
Your Cart (2 items)
-------------------
Mechanical Keyboard x1 [Remove]
USB-C Hub x2 [Remove]
-------------------
Total: $189.97
[Checkout]
After clicking Remove on Mechanical Keyboard:
Your Cart (1 items)
-------------------
USB-C Hub x2 [Remove]
-------------------
Total: $59.98
[Checkout]
Watch Out: Thread Context and StateHasChanged
If you call StateHasChanged directly inside an async callback that wasn't initiated by a Blazor event (like a Timer tick or a SignalR hub message), you'll get a runtime exception or a silent no-op. Always wrap it as 'await InvokeAsync(StateHasChanged)' — this marshals the call back to Blazor's sync context and is the correct pattern 100% of the time.
Production Insight
Memory leak from event subscriptions is the #1 DI-related bug in Blazor Server. Each time a user opens a page with a component that subscribes to an event on a singleton service, the component's reference is kept alive — the circuit survives even after navigation.
Fix: always implement IDisposable and unsubscribe, as shown above.
Rule: if you use += on an event, you must use -=.
Key Takeaway
Scoped in Blazor Server = per-circuit (per-user), not per-request.
WASM: scoped and singleton behave the same.
Always use InvokeAsync(StateHasChanged) from external callbacks.
Always implement IDisposable when subscribing to events.
JavaScript Interop: When Blazor Needs the Browser APIs
Blazor covers 95% of UI needs in pure C#, but browsers have APIs that .NET doesn't expose natively: clipboard access, geolocation, camera/microphone, third-party JS libraries like Chart.js or Stripe elements. For these cases, Blazor provides JavaScript interop via the IJSRuntime service.
The pattern is simple: inject IJSRuntime into your component, then call InvokeAsync<T> to call a JavaScript function and get a result. You can also pass .NET object references to JavaScript and call back from JS to C# using DotNetObjectReference. This is how you integrate any JS library without leaving the Blazor ecosystem.
A common pitfall: forgetting that JavaScript interop calls in Blazor Server are serialized over SignalR — they add network latency. In WASM, they're synchronous calls within the same runtime. Always minimize the number of JS interop calls per render.
Another gotcha: JavaScript functions are called asynchronously. If you need to call JS during component initialization, use OnInitializedAsync and await the call. Do not block the constructor or OnInitialized with synchronous .Result — it will deadlock Blazor Server.
ClipboardCopy.razorCSHARP
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
@* ClipboardCopy.razor — uses JavaScript interop to copy text to clipboard *@
@* DemonstratesIJSRuntime injection and calling a JS function *@
@inject IJSRuntimeJS
<button @onclick="CopyToClipboard">
@(copied ? "Copied!" : "Copy Code")
</button>
@code {
[Parameter] publicstringTextToCopy { get; set; } = string.Empty;
privatebool copied = false;
privateasyncTaskCopyToClipboard()
{
// navigator.clipboard.writeText is available in modern browsersawaitJS.InvokeVoidAsync("navigator.clipboard.writeText", TextToCopy);
copied = true;
// Reset the message after 2 secondsawaitTask.Delay(2000);
copied = false;
}
}
// Alternative: define a JS function in wwwroot/scripts/app.js and call it by name:// await JS.InvokeVoidAsync("copyToClipboard", TextToCopy);// JavaScript function in app.js:// window.copyToClipboard = (text) => navigator.clipboard.writeText(text);
Output
When button is clicked:
- The method calls navigator.clipboard.writeText via JS interop
- The button shows 'Copied!' for 2 seconds, then reverts to 'Copy Code'
- Works in both Server and WASM modes (with same code)
Pro Tip: Always Wrap JS Calls in try-catch
JavaScript interop can fail silently if the JS function throws an exception or if the browser doesn't support the API. Always wrap InvokeAsync in a try-catch block and handle the error gracefully — show a fallback UI or log to your monitoring system. The clipboard API, for example, requires HTTPS or localhost.
Production Insight
In Blazor Server, every JS interop call is a SignalR round-trip. If you call JS in a tight loop (e.g., formatting 100 list items), you add ~100ms per call — easily noticeable lag.
Batch JS calls where possible: create a single JS function that handles multiple operations.
Rule: keep JS interop calls per user interaction below 5, and never inside a rendering loop.
Key Takeaway
Use IJSRuntime.InvokeAsync for browser APIs not available in .NET.
Blazor Server adds network latency per call — batch when possible.
Always handle JS interop failures with try-catch.
For complex integrations, consider wrapping the JS library in a small JavaScript module and calling it via interop.
● Production incidentPOST-MORTEMseverity: high
Production Outage: Blazor Server Circuit Holds After DB Failover
Symptom
Users see 'Connection lost' messages and cannot interact with the app. The app is still running, SignalR connections are up, but no data refreshes.
Assumption
The database query will throw an exception which Blazor will handle gracefully and show an error page.
Root cause
Blazor Server components use scoped DbContext instances. After a database failover, the DbContext's internal connection pool returns a stale connection. The query silently hangs for 30 seconds (connection timeout), but Blazor's event handler never completes — the circuit stays in a pending state. No error is logged because the timeout exception is swallowed in a fire-and-forget task.
Fix
Implement a retry policy in the DbContext factory using Polly. Add a CancellationToken parameter to all async API calls in components and pass it with a 5-second timeout. In Blazor Server, scoped services live for the entire circuit, so any long-lived DbContext needs explicit connection validation before each query.
Key lesson
In Blazor Server, scoped services live across multiple renders — don't assume they reconnect automatically after transient failures.
Always use CancellationToken with async calls in Blazor components to prevent hanging circuits.
Add a health check endpoint that validates the SignalR circuit and database connectivity, and alert if >5% of circuits are in pending state.
Production debug guideSymptom → Action guide for the most common Blazor Server production problems4 entries
Symptom · 01
Users see 'Reconnecting...' message repeatedly
→
Fix
Check SignalR connection. Run docker logs on the SignalR hub server. Look for Microsoft.AspNetCore.SignalR warnings. Verify WebSocket connections are stable and not blocked by proxy/firewall.
Symptom · 02
Component renders old data after refresh
→
Fix
Check if the component is using OnInitializedAsync correctly. The method is called each time the component is rendered, including after user navigation. If you cache data in a scoped service, ensure it's cleared when the user's circuit reconnects.
Symptom · 03
StateHasChanged() called but UI doesn't update
→
Fix
Confirm you are calling StateHasChanged inside a Blazor event handler or lifecycle method. If called from an external event (timer, service callback), wrap it in await InvokeAsync(StateHasChanged). Otherwise the update is silently ignored.
Symptom · 04
Blazor Server app uses too much memory per user
→
Fix
Check scoped service lifetimes. Any service registered as Scoped in Blazor Server lives for the entire SignalR circuit. If you inject a large data context or cache, it stays in memory for every user. Move to transient for per-call operations or implement IDisposable to release resources.
★ Blazor Server Debugging Quick ReferenceCommands and checks to diagnose the most common Blazor Server issues in production.
SignalR circuit drops frequently−
Immediate action
Check WebSocket connectivity between client and server
Commands
Open browser DevTools → Network → WS tab. Filter by 'negotiate'. Look for 101 status code.
On server: `kubectl logs deployment/blazor-server -n production | grep "SignalR"`
Check if StateHasChanged is called on correct thread
Commands
Add a console log before StateHasChanged: `Console.WriteLine("StateHasChanged triggered from: " + Environment.CurrentManagedThreadId)`
Inspect the caller: if it's a Timer callback or event handler, wrap StateHasChanged with `await InvokeAsync(StateHasChanged)`
Fix now
Wrap all external callbacks with InvokeAsync(StateHasChanged)
Blazor WebAssembly fails on first load+
Immediate action
Check browser console for `.dll` download errors
Commands
Open DevTools → Network tab, filter by `.dll`. Look for 404 or CORS errors.
Verify that the static files middleware is configured: `app.UseBlazorFrameworkFiles()`
Fix now
Add app.UseStaticFiles() before app.MapFallbackToPage("/_Host")
Blazor Hosting Models at a Glance
Feature / Aspect
Blazor Server
Blazor WebAssembly
Where C# code runs
On the server (IIS, Kestrel)
In the browser (WebAssembly runtime)
First load time
Near-instant — no DLL download
Slower — downloads ~2–5 MB of .NET runtime
UI interaction latency
Network round-trip per event
Zero latency — runs locally
Database access
Direct — EF Core works in components
Indirect — must call an HTTP API
Offline support
None — requires server connection
Full — runs without a server after load
Scalability
Memory per active user on server
Scales to CDN — server-side stateless
Debugging
Visual Studio debugger works normally
Browser DevTools + VS WASM debugger
Suitable for
Line-of-business internal tools
Public SPAs, PWAs, offline apps
SignalR dependency
Required — circuit drops = app freezes
Not required for UI interactions
.NET 8 Auto mode
Starts as Server, migrates to WASM
Starts as Server, migrates to WASM
Key takeaways
1
A .razor component is a self-contained unit of UI
markup, logic, and events in one file. This is not just convenience, it's the architecture: components compose into trees, data flows down via [Parameter], and events bubble up via EventCallback.
2
Two-way binding with @bind is syntactic sugar for wiring up both a value attribute and a change event. Use @bind:event='oninput' when you need keystroke-level reactivity (live search, character counters), and leave it as the default 'onchange' for everything else.
3
Blazor Server and Blazor WebAssembly use identical component syntax
the hosting model is a deployment and architecture decision, not a coding decision. The main trade-off is latency vs. server memory: WASM trades initial download size for zero interaction latency; Server trades per-user memory for instant startup.
4
Always use InvokeAsync(StateHasChanged)
never plain StateHasChanged() — when triggering a re-render from a callback, timer, or background task. And always implement IDisposable to unsubscribe from events. These two rules eliminate the most common Blazor bugs in production.
5
JavaScript interop is necessary for browser APIs, but minimize calls per interaction and always handle failures with try-catch. In Blazor Server, each interop call adds network latency
batch calls when possible.
Common mistakes to avoid
4 patterns
×
Calling StateHasChanged after every await
Symptom
Double-renders, flickering UI, and occasionally a threading exception in Blazor Server (invalid cross-thread access).
Fix
Blazor automatically re-renders after any event handler or lifecycle method completes. Only call StateHasChanged explicitly when a state change happens outside of Blazor's control, such as in a Timer callback, a background Task, or a SignalR hub message handler. Everywhere else, delete that call.
×
Fetching data in OnInitialized instead of OnInitializedAsync
Symptom
The component renders with empty data even though the API call succeeded, or you see 'cannot access disposed object' exceptions.
Fix
If your data fetch is async (any Task-returning method), you must use the async version: OnInitializedAsync. Using the sync version and calling .Result or .GetAwaiter().GetResult() deadlocks Blazor Server's synchronisation context. Always await async calls inside OnInitializedAsync.
×
Not implementing IDisposable when subscribing to events or timers
Symptom
Memory leaks, components that keep responding to events after being navigated away from, or ghost UI updates modifying unmounted components.
Fix
Any component that subscribes to a C# event, starts a System.Timers.Timer, or registers a callback with an injected service must implement IDisposable. In the Dispose() method, unsubscribe every event and stop every timer. In .razor files, declare this with '@implements IDisposable' at the top and add a Dispose() method in the @code block.
×
Using Blazor Server for a public-facing consumer app without proper capacity planning
Symptom
App becomes unresponsive after a small marketing campaign drives 500 concurrent users — server memory spikes and circuits start dropping.
Fix
Estimate memory per circuit (profile with dotnet counters), calculate max users per server instance, and use WASM or Auto mode for public-facing apps. Blazor Server is best for internal line-of-business apps with <1000 concurrent users per server.
INTERVIEW PREP · PRACTICE MODE
Interview Questions on This Topic
Q01SENIOR
What is the difference between Blazor Server and Blazor WebAssembly, and...
Q02SENIOR
Explain how Blazor's component rendering pipeline works — what triggers ...
Q03SENIOR
If a Blazor Server app has 10,000 concurrent users, what are the memory ...
Q01 of 03SENIOR
What is the difference between Blazor Server and Blazor WebAssembly, and what are the specific production scenarios where you would choose one over the other?
ANSWER
Blazor Server runs C# on the server with UI updates streamed over SignalR. Blazor WebAssembly downloads the .NET runtime and runs C# in the browser. Choose Server for internal LOB apps where startup speed is critical and server resource is abundant. Choose WebAssembly for public SPAs, offline-capable apps, or when scaling to thousands of users without per-connection server memory. A third option is Auto mode (.NET 8+), which starts as Server and transitions to WASM once the runtime is cached.
Q02 of 03SENIOR
Explain how Blazor's component rendering pipeline works — what triggers a re-render, when does StateHasChanged need to be called explicitly, and what is the role of ShouldRender()?
ANSWER
A re-render is triggered automatically after any Blazor event handler (button click, form submission) completes. It also triggers after lifecycle methods like OnInitializedAsync or OnParametersSetAsync. StateHasChanged must be called explicitly only when state changes outside of Blazor's event pipeline — for example, in a Timer callback, a service event, or a background task. ShouldRender() can be overridden to return false and skip the render cycle. This optimization is useful when a component re-renders frequently but the visual output doesn't change (e.g., a component that only updates a timestamp every second).
Q03 of 03SENIOR
If a Blazor Server app has 10,000 concurrent users, what are the memory and scalability implications of using Scoped services, and how would you architect around that constraint?
ANSWER
Each Blazor Server circuit holds a scope. If a scoped service holds a large data context or cache, that memory is duplicated per user. For 10,000 users, even 1 MB per circuit is 10 GB server memory. The solution: keep scoped services lightweight — prefer transient services for heavy operations. Use a distributed cache (Redis) for per-user state that survives reconnects. Consider using Auto mode or pure WASM to offload the per-circuit overhead to the client. Also monitor the number of circuits with dotnet counters and set a maximum per-server circuit limit.
01
What is the difference between Blazor Server and Blazor WebAssembly, and what are the specific production scenarios where you would choose one over the other?
SENIOR
02
Explain how Blazor's component rendering pipeline works — what triggers a re-render, when does StateHasChanged need to be called explicitly, and what is the role of ShouldRender()?
SENIOR
03
If a Blazor Server app has 10,000 concurrent users, what are the memory and scalability implications of using Scoped services, and how would you architect around that constraint?
SENIOR
FAQ · 5 QUESTIONS
Frequently Asked Questions
01
Do I still need JavaScript when using Blazor?
For the vast majority of interactive UI work — forms, events, state, API calls — you don't need JavaScript at all. You'll only reach for JavaScript interop (via IJSRuntime) when you need browser APIs that .NET doesn't expose natively, like accessing the clipboard, calling a third-party JS library, or measuring DOM element dimensions. Blazor has a clean IJSRuntime.InvokeAsync API for exactly these cases.
Was this helpful?
02
Is Blazor WebAssembly slower than Blazor Server for page interactions?
After the initial download, Blazor WebAssembly is actually faster for UI interactions because everything runs locally in the browser — there's no network round-trip per click. Blazor Server is faster to first interactive paint because there's no download, but every subsequent interaction pays a network latency cost. For users on poor connections, Blazor Server's per-click latency can make the app feel sluggish.
Was this helpful?
03
Can I use Blazor components inside an existing MVC or Razor Pages app?
Yes, and this is a great migration strategy. ASP.NET Core supports embedding Blazor Server components directly in Razor Pages using the component tag helper: '<component type='typeof(MyBlazorComponent)' render-mode='ServerPrerendered' />'. You can adopt Blazor incrementally, converting interactive widgets one at a time rather than rewriting the whole app, as long as you add the Blazor hub middleware in Program.cs.
Was this helpful?
04
How do I debug a Blazor Server circuit that keeps disconnecting?
First, check the browser console for 'Connection disconnected' errors. Then enable SignalR logging on the server: 'services.AddSignalR(o => o.EnableDetailedErrors = true)'. Check the server's CPU and memory — if it's pegged, circuits will drop. Also check for WebSocket proxy issues (some load balancers don't support WebSocket). If the app is behind a reverse proxy, ensure it's configured to forward the WebSocket upgrade header.
Was this helpful?
05
What is the best way to handle authentication in Blazor?
Blazor leverages ASP.NET Core's existing authentication middleware. For Blazor Server, use cookie authentication — the SignalR circuit inherits the user's context. For Blazor WebAssembly, use bearer token authentication with JWT. The recommended approach is to use the AuthenticationStateProvider that comes with Microsoft.AspNetCore.Components.Authorization, and protect routes with AuthorizeView component or [Authorize] attribute.