Open-Source Projects

Here you can find an updated list of my open-source projects, in no particular order.

Name Description Location
DomainEvents Domain Events for .NET. https://github.com/rjperes/DomainEvents
EFSoftDeletes A collection of APIs for easing soft-deletes with EF Core. https://github.com/rjperes/EFSoftDeletes
ExtendedServiceProvider A wrapper for the .NET service provider offering additional features. https://github.com/rjperes/ExtendedServiceProvider
FluidCore FluidCore is an elastic object implementation for .NET. https://github.com/rjperes/FluidCore
HttpClientCache An in-memory cache for the HTTP Client. https://github.com/rjperes/HttpClientCache
Interpose.Core Interpose.Core is a framework for doing dynamic interception of .NET code (Aspect-Oriented Programming). https://github.com/rjperes/Interpose.Core
LinqQueryCache LinqQueryCache is an in-memory cache for LINQ queries. https://github.com/rjperes/LinqQueryCache
Postal.NET Postal.NET is a .NET library for writing decoupled applications. https://github.com/rjperes/Postal.NET
Search.NET A .NET proxy for search engines. https://github.com/rjperes/NetSearch
SharedFlat SharedFlat is a multitenancy library for .NET. https://github.com/rjperes/SharedFlat


Comments

Post a Comment

Popular posts from this blog

Domain Events with .NET

Introduction Domain Events  is a pattern and concept made popular by Domain Driven Design . A Domain Event is something that happened on your system and you want interested-parties to know about. It is a way to publish information in a decoupled, usually asynchronous, way. A publisher publishes (raises) an event, and interested subscribers receive a notification and act accordingly. A subscriber can also be a publisher, of course. In this post I'm going to present a Domain Events library for .NET. It's not the first time that I write about decoupling messages and subscribers in an application, I implemented a few years ago the Postal.NET library which does something similar. Mind you, there are many implementations out there, MediatR coming first to my mind, but this is mine. I obviously got some ideas from other implementations, but mine is substantially different from all the others. Concepts First, a few concepts: An event is just some class that implements IDomainEvent A
Read more

Domain Events with .NET - New Features

Introduction You may remember my post on the Domain Events framework I created, a few days ago. Well, I've been working on it, cleaning things a bit, correcting a few bugs, and I introduced two new features/concept:  Event interceptors can now return a boolean from the BeforePublish event in order to cancel the publication of the event Event transformers Changes to Event Interceptors The changes to the IDomainEventInterceptor / IDomainEventInterceptor<TEvent> interface look like this: public interface IDomainEventInterceptor { ValueTask<bool> BeforePublish(IDomainEvent @event, CancellationToken cancellationToken = default); Task AfterPublish(IDomainEvent @event, CancellationToken cancellationToken = default); } public interface IDomainEventInterceptor<TEvent> where TEvent : IDomainEvent { ValueTask<bool> BeforePublish(TEvent @event, CancellationToken cancellationToken = default); Task AfterPublish(TEvent @event, CancellationToken cancellat
Read more

Named HttpClient Registrations

Introduction You're most likely familiar with HttpClient and its recommended usage , which involves calling one of the overloads of AddHttpClient . One thing that you may or may not have noticed is, even though you call the overload that takes a name for the client, it is not registered in the dependency injection (DI) container as such. So I went out to fix this! So, what we want is that any named clients can be also registered with the DI container, which will allow us to retrieve them by the service type and key: var googleClient = serviceProvider.GetRequiredKeyedService<HttpClient>("Google"); or: public IActionResult Index([FromKeyedServices("Google")] HttpClient googleClient) { ... } So, as of now, the only way to obtain the named client is by using  IHttpClientFactory 's CreateClient method: var googleClient = serviceProvider.GetRequiredService<IHttpClientFactory>().CreateClient("Google"); Which is fine, but just takes some extr
Read more