lynMarkdigRenderTest69 1.0.0

Welcome to the build wiki!

.NET Core 2.1 Dependency Injection framework

Maintainability

Community

Welcome to #build #slack

Channels

#slack

Repository

build

Docs

wiki

v1.0.0.12

• Added runtime default checks to avoid System.MissingMethodException and System.Reflection.AmbiguousMatchException.

v1.0.0.11

• Added automatic type attribute overwrite optional parameter to the build system
• By default, type runtime attributes overrides each other and optionally can be turned off. Exception will be trown.

Example:

[MyFun]
interface IMyFunRuleSet2
{
    [MyFunDependency(RuntimeInstance.Singleton)]
    SqlDataRepository Rule(int repositoryId);
}

[MyFun]
interface IMyFunRuleSet2_Overwrite
{
    [MyFunDependency(RuntimeInstance.Singleton)]
    SqlDataRepository Rule(int repositoryId);
}

v1.0.0.10

• Added method CanRegisterParameter to ITypeFilter to control parameter registration

v1.0.0.9

• Added public sealed classes TypeDependencyObject, TypeInjectionObject

v1.0.0.8

• Added totally customizable type system
• Added ability to use interfaces as first-class objects

Examples

Customizable type system

• You can use interfaces as first-class objects instead of classes fot typeholders attributes
• Using interfaces as first-class objects, you will be able to eliminate the need to inject attributes into existing code
• By implemeting type system interfaces, you will get a fully customzable type system, easily
• Registration is bound to interfaces only, which can have a several metods named "Rule" (it is evil, i knew it)
• Type is being instantiatied is actually a return parameter of "Rule" method
• Arguments passed to the constructor is simply arguments of that particular rule
• You definetly can break some more rules, just do not try to build inconsistent type system.

Definition:

interface IMyFunRuleSet
{
    Type1 Rule(Arg1 arg1, Arg2 arg2);
}

class Type1
{
    public Type1(Arg1 arg1, Arg2 arg2)
    {
        Arg1 = arg1;
        Arg2 = arg2;
    }

    public Arg1 Arg1 { get; }

    public Arg2 Arg2 { get; }
}

Usage:

var container = new Container(new MyFunTypeConstructor(), new MyFunTypeFilter(), new MyFunTypeParser(), new MyFunTypeResolver());
container.RegisterType<IMyFunRuleSet>();
var type1 = container.CreateInstance("Build.Interfaces.Tests.Type1(Build.Interfaces.Tests.Arg1,Build.Interfaces.Tests.Arg2)");
Assert.NotNull(type1);

Features

• Declarative metadata attribute driven initialization
• Lazy type resolution and initialization (supports pure dependency decoupling anti-pattern)
• Circular references detection
• Singleton initialization
• Automated and manual type registration
• Type aliases
• External assembly types

Goal

The goal of development of this framework is to build automation of complex types initialization. Build can use declarative approach to define dependencies between types and their requirements. Constructor injection uses type resolution to resolve devendencies

Continious Integration

CircleCI TravisCI

Academic papers:

Dependency Injection for Programming by Optimization, Zoltan A. Kocsis and Jerry Swan

1. School of Mathematics, University of Manchester, Oxford Road, Manchester M13 9PL, UK. zoltan.kocsis@postgrad.manchester.ac.uk
2. Computer Science, University of York, Deramore Lane, York, YO10 5GH, UK.

Links

Dependency injection in ASP.NET Core

Inversion of Control Containers and the Dependency Injection pattern

Donate

Please, feel free to donate me 5$ to expand project development (wiki, samples, etc.)