AdaptiveClient
Autofac.Extensions.DependencyInjection
Our great sponsors
AdaptiveClient | Autofac.Extensions.DependencyInjection | |
---|---|---|
12 | 1 | |
47 | 183 | |
- | 1.1% | |
0.0 | 7.7 | |
3 months ago | 14 days ago | |
C# | C# | |
GNU Lesser General Public License v3.0 only | 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.
AdaptiveClient
-
Any suggestions on a good place to learn n-tier?
I suggest AdaptiveClient as a simple approach to solving this problem. It uses standard dependency injection concepts to allow the developer to separate the service layer into logical business classes and access them as a collection via the AdaptiveClient object.
-
Managing DbContext in EFCore6 (the right way)
AdaptiveClient makes it easy to write granular services and inject shared dbContext.
-
Microsoft.Extensions.DependencyInjection to inject ViewModels into Views in AvaloniaUI app?
I wrote a small library called AdaptiveClient that works well with WPF apps. Have not tried it on an Avalonia app yet - but I will be doing so in the next week or so.
-
EF Core multiple providers with multiple databases
You may want to check out a small library I wrote called Adaptive Client. It does what you want and greatly simplifies the process.
-
Pass a different parameter every time a Transient service is requested from the .NET Core DI container
AdaptiveClient uses Autofac keyed registrations but abstracts the dirty work away.
-
Entity Framework Core transaction across multiple services
You can get AdaptiveClient here.
-
Modular Architecture in ASP.NET Core - Building Better Monoliths
I didn't read OP's entire article (sorry I've been working for 12 hours) but it looks like he is on the right track. I wrote a small library that (I think) ties nice nicely to what he proposes: AdaptiveClient. You can use this library to write loosely coupled components (not a monolith) using dependency injection, and DRY and SOLID design principals.
-
How dependency injection might hurt your modular monolith
DI works. It adds complexity but it's worth it. The question of how to write granular, interdependent, testable services is a valid one. There are many dead-ends - for example how to wrap multiple service calls in a transaction. I wrote a small library called AdaptiveClient that attempts to answer these questions and simplify some of the complexity introduced by DI. Would love to hear your comments.
-
Dependency Injection with Entity Framework in .Net Framework for unit testing purposes
I wrote a small library to assist with this very problem. AdaptiveClient allows you to write granular services and inject DbContext. The same instance of DbContext is injected into all services so one service can call another and calls can be wrapped in transactions.
-
Refactoring n-tier application towards vertical slices/DDD-esque architecture: Double dispatch and cyclic dependencies
On a different but somewhat related note, you may run into a situation where you have services that are dependent on each other. This will give some DI containers fits. Look at AdaptiveClient for an easy way to resolve this.
Autofac.Extensions.DependencyInjection
-
Modularize ASP.NET DI configurations using Autofac
Autofacs integration with Microsofts DependencyInjection (https://github.com/autofac/Autofac.Extensions.DependencyInjection) adds an PopulateServices extension that allows to add all services in an IServiceCollection to the Autofac configuration.
What are some alternatives?
Caliburn.Micro - A small, yet powerful framework, designed for building applications across all XAML platforms. Its strong support for MV* patterns will enable you to build your solution quickly, without the need to sacrifice code quality or testability.
Autofac - An addictive .NET IoC container
AdaptiveClient.EntityFramework.Zamagon - Demo application for AdaptiveClient.EntityFrameworkCore
DryIoc - DryIoc is fast, small, full-featured IoC Container for .NET
SmartStoreNET - Open Source ASP.NET MVC Enterprise eCommerce Shopping Cart Solution
AdaptiveClient.EntityFrameworkCore - Utility classes and methods for using AdaptiveClient to work with DBContext and other Entity Framework Core objects. Build loosely coupled services, readily accessible via a lightweight façade. Easily build your service layer to use multiple providers (MSSQL, MySQL, SQLite) with no additional infrastructure. Use connection string objects to as keys to resolve specific implementations of DbContext for migrations and testing.
AdaptiveClient.SimpleConsoleDemo - Demonstration of how to use AdaptiveClient using a simple console application.