前端框架选型是企业提升开发效率与用户体验的关键因素
1775
2022-11-05
Blazorise是一个建立在Blazor和CSS框架(如Bootstrap、Bulma和Material)之上的组件库
Components for Blazor
Blazorise is a component library built on top of Blazor and CSS frameworks like Bootstrap, Bulma and Material.
Demos
Blazor WebAssembly
Bootstrap DemoMaterial DemoBulma DemoeFrolic DemoAntDesign Demo
Blazor Server
Bootstrap Demo
Note: This project is still experimental so it's possible that some components will be removed or refactored.
Releases and Roadmap
Documentation
For full documentation, please visit the Blazorise official documentation page.
Continuing reading below for a quick start guide.
Prerequisites
Before you continue, please make sure you have the latest version of Visual Studio and .Net Core installed. Visit an official Blazor site to learn more.
Installations
There are currently 5 different NuGet packages for each of the supported CSS frameworks. Available packages are:
- Blazorise.Bootstrap- Blazorise.Bulma- Blazorise.Material- Blazorise.AntDesign- Blazorise.Frolic
This guide will show you how to setup Blazorise with Bootstrap and FontAwesome icons. To setup Blazorise for other CSS frameworks, please refer the Usage page in the documentation.
1. NuGet packages
First step is to install a Bootstrap provider for Blazorise:
Install-Package Blazorise.Bootstrap
And FontAwesome icon package:
Install-Package Blazorise.Icons.FontAwesome
2. Source files
The next step is to define links to Bootstrap and FontAwesome CSS or js files. If you're using Blazor WebAssembly project template, those links will go to the index.html located inside of wwwroot folder. Otherwise, if you're using a Blazor Server project template you will place the links into the _Host.cshtml.
In this step we're also going to define the links for Blazorise content files that comes with nuget packages. You must follow the naming convention _content/{LIBRARY.NAME}/{FILE.NAME}.
NOTE When Blazor project is created it will also include it's own Bootstrap and FontAwesome files that can sometime be of older versions. To ensure we're using the appropriate Bootstrap and FontAwesome files, you need to remove them or replace them with the links from above. If you forget to remove them it's possible that some of components will not work as expected.
3. Using's
In your main _Imports.razor add:
@using Blazorise
4. Registrations
Starting from .Net Core 3.2 there was some changes regarding the setup process for Blazor WebAssembly project types. Specifically the Startup.cs file is removed and all registrations are now done in the Program.cs.
Depending on the hosting model of your Blazor project you only need to apply either step 4.a or 4.b. You should not include both of them as that is generally not supported.
To Learn more about the different project types you can go to the official documentation.
4.a Blazor WebAssembly
This step is mandatory for Blazor WebAssembly(client-side) and also for ASP.NET Core hosted project types. You should place the code into the Program.cs of your client project.
// other usingsusing Blazorise;using Blazorise.Bootstrap;using Blazorise.Icons.FontAwesome;public class Program{ public static async Task Main( string[] args ) { var builder = WebAssemblyHostBuilder.CreateDefault( args ); builder.Services .AddBlazorise( options => { options.ChangeTextOnKeyPress = true; } ) .AddBootstrapProviders() .AddFontAwesomeIcons(); builder.Services.AddSingleton( new HttpClient { BaseAddress = new Uri( builder.HostEnvironment.BaseAddress ) } ); builder.RootComponents.Add
4.b Blazor Server
This step is going only into the Startup.cs of your Blazor Server project.
// other usingsusing Blazorise;using Blazorise.Bootstrap;using Blazorise.Icons.FontAwesome;public class Startup{ public void ConfigureServices( IServiceCollection services ) { services .AddBlazorise( options => { options.ChangeTextOnKeyPress = true; // optional } ) .AddBootstrapProviders() .AddFontAwesomeIcons(); // other services } public void Configure( IComponentsApplicationBuilder app ) { // other settings app.UseRouting(); app.ApplicationServices .UseBootstrapProviders() .UseFontAwesomeIcons(); app.UseEndpoints( endpoints => { endpoints.MapBlazorHub(); endpoints.MapFallbackToPage( "/_Host" ); } ); }}
Usage
@page "/counter"
Try Preview
If you're willing to try preview versions of Blazorise all you need to do is to setup Visual Studio so it knows how to use Blazorise MyGet feed. The easies way to do this is to create NuGet.config file and place it into your solution root folder. Then you copy the following content and paste it to the NuGet.config.
Now you will be able to get preview versions of Blazorise with the latest changes and bug fixes.
版权声明:本文内容由网络用户投稿,版权归原作者所有,本站不拥有其著作权,亦不承担相应法律责任。如果您发现本站中有涉嫌抄袭或描述失实的内容,请联系我们jiasou666@gmail.com 处理,核实后本网站将在24小时内删除侵权内容。
发表评论
暂时没有评论,来抢沙发吧~