windy-ui
A Tailwind CSS based component library for Blazor. Inspired by Tailwind UI. (by techgems)
MatBlazor
Material Design components for Blazor and Razor Components (by SamProf)
Our great sponsors
windy-ui | MatBlazor | |
---|---|---|
3 | 5 | |
46 | 2,816 | |
- | - | |
0.0 | 0.6 | |
over 2 years ago | about 2 months ago | |
HTML | HTML | |
GNU General Public License v3.0 only | MIT License |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
windy-ui
Posts with mentions or reviews of windy-ui.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2021-12-25.
- Anyone have tried using TailwindUI components in their Blazor projects?
-
Building rich web UIs with little Javascript (not Blazor)
Blazor is awesome, but it has it's downsides and not every situation or company is ready to switch to it nor do they need to (and I say this as the builder of a UI library for Blazor). This approach is a good alternative for when SPAs are not an option for whatever reason it may be.
-
Introducing Windy UI
Windy UI is strongly inspired in Tailwind UI. There is no publicly available Nuget package yet, but there will be soon. For now, you can look at it here.
MatBlazor
Posts with mentions or reviews of MatBlazor.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-02-08.
- Using React components in Blazor apps?
- Best way to show an alert/notification without needing close button?
- Dotnet 6 and Material Design for Bootstrap?
-
Route components in separate project for Blazor WASM .NET 5. !
Hello! I've planned out my project solution such that I own my views separate from my client application. Unfortunately, after upgrading to .NET 5.0 I'm no longer able to reference projects with my views. My setup is like how it is done here: MatBlazor/src at master · SamProf/MatBlazor (github.com) Views are shared between the Blazor Server and Blazor Client projects - both components and routing components (pages). I'm getting the following error: BLAZORSDK1001 The project references the ASP.NET Core shared framework, which is not supported by Blazor WebAssembly apps. Remove the framework reference if directly ⠀referenced, or the package reference that adds the framework reference. REDACTED C:\Program Files\dotnet\sdk\5.0.103\Sdks\Microsoft.NET.Sdk.BlazorWebAssembly\targets\Microsoft.NET.Sdk.BlazorWebAssembly.Current.targets 635 * Is it even possible to accomplish this for the new WASM Blazor version? * If yes, how can I accomplish this? WASM Client and routable components project settings
-
Route components in separate project for Blazor WASM .NET 5.0
No, but you can use the MatBlazor/src/MatBlazor.Demo.ClientApp at master · SamProf/MatBlazor (github.com) project as reference. My project is based on the same concept. After migrating the client application to .NET 5, you should get the error
What are some alternatives?
When comparing windy-ui and MatBlazor you can also consider the following projects:
export-data-to-excel-in-blazor - This repository contains examples of exporting data from a data table to Excel in Blazor applications using Syncfusion Excel (XlsIO) library.
MudBlazor - Blazor Component Library based on Material design with an emphasis on ease of use. Mainly written in C# with Javascript kept to a bare minimum it empowers .NET developers to easily debug it if needed.