Tips, Expertise, Articles and Advice from the Pro's for Your Website or Blog to Succeed
Blazor has experimental support for shared components. Developers can build application-agnostic Blazor components and, when packed with a Blazor shared components library, these components can be shared between Blazor applications. This blog post shows how to build shared Blazor components.
This blog post was written when the following prerequisites were valid:
Telerik UI for Blazor is a brand new library of UI components for the Razor Components and Blazor frameworks. Even though Telerik UI for Blazor is in an "Early Preview" stage it ships with one of the most popular and versatile UI components, the data grid. The data grid features out-of-the-box functionality like paging, sorting, templates, and themes. In this article, we will focus on how to get started with the grid's basic features.
Since the ASP.NET Preview is are moving at a rapid pace, it's best to update your bits. Make sure you're on the current version of Razor Components (server-side) and Blazor (client-side) since we'll be working with both. Detailed installation instructions for both frameworks can be found on the Blazor getting started page.
In some child and parent component situations it would be good if you could render, or at least get access to, an instance of a Razor Component.
Given the following scenario where we try to render an instance of the Counter component inside the Index component:
In this article, we will learn how to deploy a Blazor application on Firebase. We will create a client-side application using Blazor and host it on Firebase. This application will not have any server-side code or web API logic. We will use Visual Studio 2017 to build and publish the application.
You need to install the following prerequisites to create a Blazor application.