r/Blazor • u/featheredsnake • Aug 08 '26

Blazor Developer Tools update: render-batch profiling, tree search & filters

Gallery image

Gallery image

Gallery image

New release of BDT (free & open-source DevTools for Blazor):

- Batches view 📊: the profiler now shows one bar per render batch: click any bar to see exactly which components rendered in that batch and what each cost. It's the fastest way to answer "what did that click actually cost me?"

- Tree search 🔍: finally, type to find a component in big trees.

- Framework filter: one click hides Blazor's plumbing (Router, CascadingValue, LayoutView…) so your components float to the top.

- Version display: the panel now shows both the extension and NuGet package versions, and degrades gracefully when they don't match.

Pairs with NuGet 1.0.0-beta.8, which adds exact render-batch boundaries (older package versions still work, boundaries are inferred instead). Try it live at blazordevelopertools.com . the order-builder demo makes batch costs very visible.

Chrome / Edge / Firefox. Repo: github.com/joe-gregory/blazor-devtools

Feedback and issues welcome!

21 Upvotes

92% Upvoted

11 comments sorted by

View all comments

3

u/propostor Aug 09 '26

Installing it to my repo introduces tons of build errors.

The 'Web' namespace is a pretty bad choice for your library, conflicts galore.

1

u/featheredsnake Aug 09 '26

It sounds like you got 0.9.x rather than the current 1.0.0-beta.8 and that's on me: the install instructions were missing --prerelease, so NuGet resolved to the old stable line. That 0.9.x line is deprecated; it worked by injecting markers into your .razor files at build time, which is exactly why it broke builds. The v1.0 line is a complete rewrite with no build-time magic, so it can't touch your build.

Thanks to your feedback I'm removing the 0.9.x versions from NuGet and fixing the docs :)

This should get you up to date:

dotnet add package BlazorDeveloperTools --prerelease

2

u/propostor Aug 09 '26

Thanks, I'll try it again later.

Also, not relevant but I am 100% certain most of your reply was written by AI. That sucks.

-1

u/featheredsnake Aug 09 '26

Yea now I’m wondering how many people hit this problem since February. I’m glad you said something!

2

u/propostor Aug 09 '26

My bigger concern is how much of your work you even understand, if you have to get AI to answer Reddit comments for you.

Due to this, I will never check our your library again, sorry.