I recently ran into a requirement to show a nested list of items in a menu for a “code explorer” component:

There’s no concrete limit to how deep this list can go (each item can have its own list of items and so on and so forth).

Here’s the data that drives this UI:

public class ExampleFolderDTO
    public NodeDTO RootNode { get; set; }

    public class NodeDTO
        public string Name { get; set; }
        public string Slug { get; set; }
        public List<NodeDTO> Nodes { get; set; } = new();

Notice how each instance of NodeDTO can have its own list of NodeDTO, hence the potentially infinite tree depth.

So how can we render this in Blazor?

Well it turns out Blazor can handle a little bit of recursion, making this relatively straightforward.

First we’ll want a root component, to act as the starting point for the TreeView.

    <Node CourseNode="courseDetails.Root" OnNodeSelected="OnNodeSelected"/>
@code {

    private GetCourseResponse courseDetails;
    protected override async Task OnInitializedAsync()
        courseDetails = await Api.GetCourse(new GetCourseRequest { Course = Course });

GetCourseResponse contains the root node (the toppest of the top level nodes!)

public class GetCourseResponse {

    public CourseNodeDTO Root { get; set; }


All the magic happens in the Node component.


<Button @onclick="() => OnNodeSelected.InvokeAsync(CourseNode)">

<ul class="ml-6">
    @foreach (var node in CourseNode.Nodes)
        <li class="list-none">
            <Node CourseNode="@node" OnNodeSelected="@OnNodeSelected"/>
@code {
    [Parameter, EditorRequired]
    public GetCourseResponse.CourseNodeDTO CourseNode { get; set; }

    public EventCallback<GetCourseResponse.CourseNodeDTO> OnNodeSelected { get; set; }


The first step is to render the UI for the current node (in this case, a button).

The next step is to loop over each of the sub nodes and render instances of the Node component for each one.

With that, we have a potentially infinite depth Tree View component.

From here we can extend this to handle things like showing different icons for different node types, simply by making changes to that Node component.

Source code, step-by-step tutorials, videos and more

I've compiled a whole load of useful tutorials, source code for articles (like this one) and mini video series to help you push through all the noise and build better ASP.NET web applications, faster.

Drop your email in the box below to get new posts first, and instant access to 'the vault'.

I respect your email privacy. Unsubscribe with one click.


Next up

Good (Blazor) Components are… ?
Components, done “right” carry tremendous potential to speed up your web development, but get it wrong and you’ll miss out on all the potential benefits
What happens when you navigate to the “same page” in Blazor?
When you navigate to the same component in Blazor it will bypass some of the component lifecycle events
Need your Blazor sibling components to talk to each other?
How to handle Component A needs to talk to Component B challenges in Blazor