This help article describes the structure and architecture of the typical Radzen Blazor application.
The Radzen Blazor applications has two top-level directories:
meta directory contains JSON files that describe the application structure - data sources, pages, assets.
server directory contains the server-side Blazor application. Radzen generates the contents of the
server directory from
meta directory JSON files.
The Radzen Blazor application follows the default .NET Core CLI Blazor template guidelines. Sample app showing the free Blazor Components can be found here: https://blazor.radzen.com/.
Blazor is in official preview and so is the current Radzen support. Feature parity with Radzen Angular applications will be reached once Microsoft releases Blazor officially.
Every Radzen page outpus two files in their own directory:
<page-name>.razor- the template of the page which contains the HTML markup of the UI components. This file is generated always. Any changes made to it by the user will be overwritten.
<page-name>.razor.cs- C# partial class that implements custom logic. This file is generated only once. Any changes made to it by the user will NOT be overwritten.
<page-name>.razor.designer.cs- C# class that implements the Blazor component - handles UI component events (e.g. button clicks), loads data, etc. This file is generated always. Any changes made to it by the user will be overwritten.
Blazor applications FAQ
Here is a quick FAQ regarding Blazor support in Radzen:
Does Radzen support client-side or server-side Blazor?
Radzen currently supports server-side Blazor because Microsoft will release it first.
Can I migrate my existing Radzen Angular application to Blazor?
Not yet. Your current Radzen application is probably relying on features that are not available yet.
What UI components are you using in Radzen Blazor applications?
We are developing a brand new suite of native Blazor components. Native means that we don’t wrap existing JS libraries - everything is 100% Blazor code compatible with Blazor data-binding, templates and event handling.
When will component X be available in Radzen Blazor applications?
We will gradually implement the remaining components from the Radzen toolbox.
Most of the generated classes are partial to allow for customization via partial methods. More info is available in the customization help article.