Scrutor
FluentValidation.Blazor
Our great sponsors
Scrutor | FluentValidation.Blazor | |
---|---|---|
16 | 1 | |
3,417 | 233 | |
- | - | |
0.0 | 0.0 | |
about 1 month ago | almost 2 years ago | |
C# | C# | |
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.
Scrutor
- Reflection -> Source Generated
-
Why asp.net core is not popular like Spring boot or nodejs, although it's better than both in all aspects?
You can with MS's default DI as well via scrutor.
- C# Design Patterns: Implementing the decorator pattern
-
Migrating to .Net Core MVC from .Net framework 4.8
if you are heavily invested in autofac you can replace the build in DI with another container. at this point i don't think it is that necessary. especially if you use scrutor. it gives your some nice assembly scanning registration that autofac/simple injector give https://github.com/khellang/Scrutor
-
ModuleLoader vs Reference
If you wouldn't mind, I have one additional question. If I wouldn't bother to remove this loading, how could one add that as service when using DI? I have found tool called Scrutor (https://github.com/khellang/Scrutor), is it something commonly used in situation like this?
-
Would you use an attribute that registers your interface/classes with .nets IoC container?
I much prefer using Scrutor and asbly scanning myself. https://github.com/khellang/Scrutor
-
Dependency Injection
you can also use Scrutor to get closer to Autofac functionality https://github.com/khellang/Scrutor
-
You Probably Don't Need to Worry About MediatR
That can't be the only justification, because you can easily register services using reflection without using MediatR.
-
A new small opensource library - Autojector.
I might suggest additional registration time extensions to modify the behavior as needed on classes. Take a look at Scrutor for some inspiration on API specifically.
-
6 .NET Myths Dispelled — Celebrating (Almost) 21 Years of .NET
There is a package that simplifies it for you if you want. But not everybody agrees that automatic registration is good pattern, so you have a choice.
FluentValidation.Blazor
-
Blazor Validation Conditional Logic
Use FluentValidation and a library like this to integrate it with Blazor: https://github.com/ryanelian/FluentValidation.Blazor. You can inject any service into the validator so it will be easy to read the configuration during validation.
What are some alternatives?
Autofac - An addictive .NET IoC container
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.
Lamar - Fast Inversion of Control Tool and Successor to StructureMap
cqrs-clean-eventual-consistency - CQRS, using Clean Architecture, multiple databases and Eventual Consistency
Microsoft.Extensions.DependencyInjection
TheLastTime - C# .NET 5 Blazor WebAssembly Progressive Web Application that tracks when was the last time you did something
Simple Injector - An easy, flexible, and fast Dependency Injection library that promotes best practice to steer developers towards the pit of success.
Blazorise - Blazorise is a component library built on top of Blazor with support for CSS frameworks like Bootstrap, Tailwind, Bulma, AntDesign, and Material.
Unity - This repository contains all relevant information about Unity Container suit
CSLA .NET - A home for your business logic in any .NET application.
DryIoc - DryIoc is fast, small, full-featured IoC Container for .NET
Castle Windsor - Castle Windsor is a best of breed, mature Inversion of Control container available for .NET