TrBlazorEx
CSLA .NET
Our great sponsors
| TrBlazorEx | CSLA .NET | |
|---|---|---|
| 1 | 6 | |
| 7 | 1,218 | |
| - | 1.9% | |
| 0.0 | 9.7 | |
| 6 months ago | 4 days ago | |
| C# | C# | |
| - | 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.
TrBlazorEx
-
Switch from Blazor Server to WASM?
u/beer0clock my suggestion would be to Create the UI in a separate project (razor class library), do the DB calls from that library using an API project and call that UI project from either Blazor server or Blazor WASM project. This way you can Switch anytime to new project type and will be future ready for using the same UI in even desktop or mobile app using MAUI Blazor. you can checkout my this (https://github.com/techierathore/TrBlazorEx) code where I have used this approach and written blog about it and this (https://github.com/techierathore/Xpenser ) project which is a full-fledged application using the same approach.
CSLA .NET
- How can a rich domain model be implemented in practice using EF Core?
-
Advice on cross platform project architecture
I've heard (no first hand experience) that the csla .net framework is meant to address this particular problem https://cslanet.com/. Rocky did an interview on dotnet rocks and it seemed like a tool worth looking into.
- My new job uses CSLA. I have no idea what is going on or how it works. I want to learn but all the sources I find are super old (5-10 years YouTube videos) and aren’t really helpful when beginning. Help how do I learn?
-
Switch from Blazor Server to WASM?
Put your blazor components in its own project (Visual Studio Razor component library) and you can then use them from either Blazor server or WASM. I've been doing that along with using CSLA which really makes it simple to switch from one to the other. CSLA itself has somewhat of a steep learning curve, bit you should be able to get a general idea of how to setup you project for not server and WASM from their Blazor example.
What are some alternatives?
Xpenser - This is my Live Streaming Project
ASP.NET Boilerplate - ASP.NET Boilerplate - Web Application Framework
Introducing .NET Multi-platform App UI (MAUI) - .NET MAUI is the .NET Multi-platform App UI, a framework for building native device applications spanning mobile, tablet, and desktop.
Microdot Framework - Microdot: An open source .NET microservices framework
Uno Platform - Build Mobile, Desktop and WebAssembly apps with C# and XAML. Today. Open source and professionally supported.
peasy - A business logic micro-framework for .NET and .NET Core
Orleans - Cloud Native application framework for .NET
Spring.Net - Spring Framework for .NET
ABP - Open Source Web Application Framework for ASP.NET Core. Offers an opinionated architecture to build enterprise software solutions with best practices on top of the .NET and the ASP.NET Core platforms. Provides the fundamental infrastructure, production-ready startup templates, application modules, UI themes, tooling, guides and documentation.
ASP.NET MVC Boilerplate Framework - .NET Core Extensions and Helper NuGet packages.
CoreFX - This repo is used for servicing PR's for .NET Core 2.1 and 3.1. Please visit us at https://github.com/dotnet/runtime
Prism - Prism is a framework for building loosely coupled, maintainable, and testable XAML applications in WPF, Xamarin Forms, and Uno / Win UI Applications..