tags-strapi-purplerhino
MatBlazor
Our great sponsors
tags-strapi-purplerhino | MatBlazor | |
---|---|---|
1 | 5 | |
2 | 2,816 | |
- | - | |
10.0 | 0.6 | |
over 1 year ago | about 1 month ago | |
HTML | HTML | |
MIT License | MIT License |
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.
tags-strapi-purplerhino
-
How to Build a Blog App Using Blazor WASM and Strapi
You can download the source code implementation from Github. Let me know if you have any comments, queries, or suggestions. The Strapi Team is always available to assist you.
MatBlazor
- 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?
Templates - Ready to use Blazor Templates in different styles and layout with all the basic setup already done for MudBlazor.
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.
Strapi - 🚀 Strapi is the leading open-source headless CMS. It’s 100% JavaScript/TypeScript, fully customizable and developer-first.
material-design-lite - Material Design Components in HTML/CSS/JS
BlazorWebFormsComponents - A collection of Blazor components that emulate the ASP.NET Web Forms controls of the same name
windy-ui - A Tailwind CSS based component library for Blazor. Inspired by Tailwind UI.
Tailwind CSS - A utility-first CSS framework for rapid UI development.
blazor-office-addin - A sample Office Add-In based on Blazor Server
strapi-plugin-transformer - A plugin for Strapi Headless CMS that provides the ability to transform the API request or response.
react-material
angular-starter - :rocket: Angular 17 Starter with Storybook, Transloco, Jest, TestCafe, Docker, ESLint, Material & Prettier :rocket:
BlazorAndTailwind - Tips and notes about Blazor and Tailwind