So to just clarify for others who might be in my same learning phase:
I could have just added <RadzenDialog></RadzenDialog> to the markup portion of Home.razor where I was testing this component. Which makes sense, since that would declare an instance of the class RadzenDialog in that page.
But Paul's approach with adding <RadzenComponents @rendermode="InteractiveServer" /> confuses me on how it works - since there is no specific RadzenDialog reference in that snippet. Still learning but I'll get there.
Thanks again for all the help on this forum! You contributors show much more patience than I typically see in other forums.
The code below is the complete listing for the RadzenComponents component. It basically does what @enchev had already stated for RadzenDialog, but also ensures that the other UI elements are registered on the page.
<RadzenDialog @attributes="Attributes" />
<RadzenNotification @attributes="Attributes" />
<RadzenContextMenu @attributes="Attributes" />
<RadzenTooltip @attributes="Attributes" />
<RadzenChartTooltip @attributes="Attributes" />
@code {
///
/// Specifies additional custom attributes that will be rendered by the component.
///
/// The attributes.
[Parameter(CaptureUnmatchedValues = true)]
public IReadOnlyDictionary<string, object>? Attributes { get; set; }
}
You can either clone or download the complete source for the Radzen components from the above link. This, in itself, can be a great help in understanding how the library hangs together.