.NET Standard 2.0 library with helpers to convert your POCO objects to Azure Table Storage objects of type `ITableEntity` or `DynamicTableEntity` and vice versa. It supports saving complex classes by converting not natively supported property types into JSON strings. There is no need to have dedicated properties called PartitionKey and RowKey. Just decorate your properties with the `[PartitionKey]` and `[RowKey]` attributes. There is also an optional `[ETag]` attribute to read the ETag and ensure optimistic concurrency when writing it back. You can decorate a property with the `[Timestamp]` attribute to read the auto-generated time stamp from your table entity.
DynamicObjectProxy that lets you intercept any methods of any object and adding decorations. Inspired by CBO Extender by Gary H. Guo
HybridCache-backed default IHandlerCache for Elarion handler result caching ([Cacheable]/[CacheInvalidate]). Opt-in via AddElarionHandlerCaching; referencing this package is what pulls Microsoft.Extensions.Caching.Hybrid, keeping Elarion core dependency-light (the IHandlerCache seam and the cache decorators live in Elarion.Abstractions).
SimpleRules.Net is a rules engine that works based on attributes decorated on the properties of a class
Allows to inject properties of classes by using annotations. Decorate any public, protected or private property with [FromAutofac] and EasyPropInject resolves it from the Autofac container while the component is activated. Property metadata is cached per type and written through emitted setters, so injection costs close to nothing after the first resolve.
This packages registers DataContract mapped files in order to be persisted in mongodb (as decorated in DataContract/Member).
The current repository allows you to maintain your start-up project class cleanly, and organize solution structure more clearly, simply readable, and reusable. And with the possibility to order initialize and use it or not. Using this functionality allows you to safely add new dependence, adjust existing or remove/relocate it without pain and with a few adjustments.
EF Core transaction/unit-of-work boundary for Elarion: an IUnitOfWork over a DbContext transaction (with PostgreSQL lock_timeout and savepoint support) that the framework transaction and idempotency decorators compose on.
A decorator for command-query architecture, which adds support for OpenTelemetry tracing.
Decorate your POCOs with attributes for easy usage with Azure.Data.Tables
Package which allows to add the Memory Caching Decorator and contains the base classes necessary for it's customization. Minded helps to implement a clean architecture, offering the scaffolding necessary to implement patterns like Mediator, Decorator, Command and Query and more. Encapsulate all your business logic in Commands and Queries, the rest will be dealt by the framework.
Provides core functionalities for handling AJAX form submissions with zero or more files, and report back data upload progress. It supports automatic form (UI) generation from metadata-decorated .NET object models. It also supports easy integration of Google's reCAPTCHA technology and the Quill Rich Text Editor (https://quilljs.com).
Decoration extensions for Microsoft.Extensions.DependencyInjection. This is a stripped-down version of Scrutor (by Kristian Hellang), containing only decoration functionality.
Microsoft/Polly-backed default IResiliencePipelineRunner for Elarion ([Resilient] handlers and deferred scheduler retries). Opt-in via AddElarionResilience; referencing this package is what pulls Microsoft.Extensions.Resilience, keeping Elarion core dependency-light (the resilience seam, the decorator, and the lightweight policy catalog live in Elarion.Abstractions and Elarion core).
Annotations for decorate Proxy Generator
Minded helps to implement a clean architecture, offering the scaffholding necessary to implement patterns like Mediator, Decorator, Command and Query and more. Encapsuplate all your business logic in Commands and Queries, the rest will be dealth by the framework.
Flexible dependency injection extensions for convention-based service registration, attribute-based service registration, custom automatic service registration and decorator pattern
ExcelBuilder.Ceragon creates excel tables based on a generic collection that is decorated with a custom data type. Attribute classes are used to style tables
Library that can generate WPF Forms using decoration tags
Command Line GUI includes a command line arguments parser library Fonlow.CommandLineGui.Core.dll for constructing .NET command line programs with complex arguments. You define a data model class decorated by some attributes for representing arguments. The core library will parse the command line arguments and populate the Plain Old CLR Object which is the router of the functionality of your command line program. And the Core library may also generates CLI help page as illustrated in https://a.fsdn.com/con/app/proj/commandlinegui/screenshots/Standard.PNG/182/137 Command Line GUI is a host program that generates GUI for existing command line programs. .NET command line programs constructed through the core library could become a plugin of Command Line GUI and have the GUI generated. You may use the core library to wrap existing command line programs like Robocopy, and the wrapper may become a plugin, thus a native command line program could easily have a GUI.
Pure Render Decorator (pure-render-decorator) binding library for Bridge.NET projects.
This first version contains a WPF Custom Control, which can be used to visualize an AutomationML Object and selected descendants in a WPF TreeView. The TreeView Nodes are decorated with Icons which are specific for each CAEX-Element.
Infrastructure glue for the Stratara framework — authorization decorators, configuration providers, and DI composition helpers that wire Mediator, Outbox, Identity, and EF Core into a hosted app.
Test infrastructure for Microsoft Agent Framework Workflows. Fluent fixture base with assertion builders, an execution-environment parametric axis, and ANcpLua-authored facades over MAF Workflows internals (facade / decorator / railway / fluent / extension methods) — designed for expressiveness and loose coupling, not a 1:1 mirror of upstream.
This library provides a basic implementation of the decorator factory.
Autobind Decorator (autobind-decorator) binding library for Bridge.NET projects.
An extension for Microsoft.Extensions.DependencyInjection allowing classes to be decorated with [Service] for quick and easy dependency registration.
A retry decorator for the Klinked.Cqrs library that makes it easy to add retry logic to all commands, events, and queries. This library allows you to specify a retry policy using Polly.
Source generator for decorator pattern boilerplate code in C#. When implementing the decorator pattern in C#, it requires adding boilerplate code for every interface that needs to support decorators, namely the abstract class. Boilerplate is tedious to write and error-prone. This source generator solves this problem by automatically generating the abstract class. It only needs to be told which interfaces it should generate the abstract class for.
Built-in node library for Paradise.BT behavior trees (Sequence, Selector, Parallel, decorators, delegate-backed actions, delay timer).
Assembly to allow logging via Attributes Logging for a class is enabled by decorating it with the [Loggable] attribute and deriving from ContextBoundObject. Another option is to derive from LoggableObject. The [Log] attribute will enable logging with de Default logger. The DefaultMessageLogger and DefaultExceptionLogger in Loggers can be replaced with custom implementations. The [LogWith(Type)] allowes to specify a logger type that should be used for logging the method. A Custom Logger specified by this attribute must have a parameterless constructor. Both Attributes can be used as class / method attributes. When used as class attributes loggers will be called for every external call to the object. It is possible to combine both variants. If the logger implements MethodLogger method entry and leaving will be logged. If the logger implements ExceptionLogger than all exception will be logged. It is possible to implement both interfaces and enable standard and exception logging with just 1 attribute. It is possible to specify multiple loggers In order to create complex Loggers (with parameters / Properties to be provided) you can provide an own ObjectResolver (Loggers.LoggerResolver). e.g. for using a Dependency-Injection container or service locator
Package to automatically inject attribute decorated services into IOC Container.