Reading — Blazor, Held Together

Blazor, Held TogetherState & Rendering · Rule 5

State & Rendering

Rule 5Chapter II

Dispose what you subscribe.

Why this rule exists

A component that subscribes to a service event and skips IDisposable leaks itself on every navigation. Server-side, that is a per-circuit memory leak that compounds with every user.

Blazor, Held Together

In practice

Any += in a component demands @implements IDisposable and a matching -= in Dispose. Code-review for the pair, not just the subscription.

Keep reading

8 of 12 · 64%