NuGet Gallery Feed for IoCThis is a IoC container based on Dependency Injection. As dependencies are
controlled with attributes, you do not need any code to register, lookup,
or wire object instances.
It is self contained by defining attributes in your classes. Configuration can
also be externalized with a declarative XML configuration.
On top, there is a continuously growing "Enterprise Features Layer" which
offers functionality like asynchronous task scheduling or validation api.
See the project web page for an introduction and examples.https://www.nuget.org/packages/IoC/2018-11-30T01:44:42Zhttps://api.nuget.org/v3-flatcontainer/ioc/2.2.0.2/iconhttps://www.nuget.org/packages/IoC/2.2.0.2IoC 2.2.0.22016-03-04T09:50:15Z2018-11-30T01:44:38Zmaikhellerhttps://www.nuget.org/profiles/maikhellerThis is a IoC container based on Dependency Injection. As dependencies are
controlled with attributes, you do not need any code to register, lookup,
or wire object instances.
It is self contained by defining attributes in your classes. Configuration can
also be externalized with a declarative XML configuration.
On top, there is a continuously growing "Enterprise Features Layer" which
offers functionality like asynchronous task scheduling or validation api.
See the project web page for an introduction and examples.https://www.nuget.org/packages/IoC/2.2.0.1IoC 2.2.0.12016-01-29T10:44:16Z2018-11-30T01:44:42Zmaikhellerhttps://www.nuget.org/profiles/maikhellerThis is a IoC container based on Dependency Injection. As dependencies are
controlled with attributes, you do not need any code to register, lookup,
or wire object instances.
It is self contained by defining attributes in your classes. Configuration can
also be externalized with a declarative XML configuration.
On top, there is a continuously growing "Enterprise Features Layer" which
offers functionality like asynchronous task scheduling or validation api.
See the project web page for an introduction and examples.https://www.nuget.org/packages/IoC/2.2.0IoC 2.2.0.02016-01-25T10:02:41Z2018-11-30T01:44:38Zmaikhellerhttps://www.nuget.org/profiles/maikhellerThis is a IoC container based on Dependency Injection. As dependencies are
controlled with attributes, you do not need any code to register, lookup,
or wire object instances.
It is self contained by defining attributes in your classes. Configuration can
also be externalized with a declarative XML configuration.
On top, there is a continuously growing "Enterprise Features Layer" which
offers functionality like asynchronous task scheduling or validation api.
See the project web page for an introduction and examples.https://www.nuget.org/packages/IoC/2.1.0.1IoC 2.1.0.12015-09-08T07:25:35Z2018-11-30T01:44:38Zmaikhellerhttps://www.nuget.org/profiles/maikhellerThis is a IoC container based on Dependency Injection. As dependencies are
controlled with attributes, you do not need any code to register, lookup,
or wire object instances.
It is self contained by defining attributes in your classes. Configuration can
also be externalized with a declarative XML configuration.
On top, there is a continuously growing "Enterprise Features Layer" which
offers functionality like asynchronous task scheduling or validation api.
See the project web page for an introduction and examples.https://www.nuget.org/packages/IoC/2.1.0IoC 2.1.0.02015-06-24T21:07:07Z2018-11-30T01:44:39Zmaikhellerhttps://www.nuget.org/profiles/maikhellerThis is a IoC container based on Dependency Injection. As dependencies are
controlled with attributes, you do not need any code to register, lookup,
or wire object instances.
It is self contained by defining attributes in your classes. Configuration can
also be externalized with a declarative XML configuration.
On top, there is a continuously growing "Enterprise Features Layer" which
offers functionality like asynchronous task scheduling or validation api.
See the project web page for an introduction and examples.https://www.nuget.org/packages/IoC/2.0.0.3IoC 2.0.0.32015-06-03T09:09:48Z2018-11-30T01:44:34Zmaikhellerhttps://www.nuget.org/profiles/maikhellerIn contrast to existing IoC container, this one is very simple to use and introduces nearly no constraints.
It is self contained by defining attributes in your classes or can be externalized with a declarative XML configuration.
See the project web page for an introduction and examples.https://www.nuget.org/packages/IoC/2.0.0.2IoC 2.0.0.22015-06-02T10:52:07Z2018-11-30T01:44:34Zmaikhellerhttps://www.nuget.org/profiles/maikhellerIn contrast to existing IoC container, this one is very simple to use and introduces nearly no constraints.
It is self contained by defining attributes in your classes or can be externalized with a declarative XML configuration.
See the project web page for an introduction and examples.https://www.nuget.org/packages/IoC/2.0.0.1IoC 2.0.0.12015-06-01T11:12:47Z2018-11-30T01:44:35Zmaikhellerhttps://www.nuget.org/profiles/maikhellerIn contrast to existing IoC container, this one is very simple to use and introduces nearly no constraints.
As a service, your class can be injected as a dependency into other beans (service or consumer). Following this concepts,
you will automatically get testable code.
There are some best practices which should be followed when using IoC in general and this framework in special.
They will be documented on the project site in near future.https://www.nuget.org/packages/IoC/2.0.0IoC 2.0.0.02015-05-21T21:37:07Z2018-11-30T01:44:34Zmaikhellerhttps://www.nuget.org/profiles/maikhellerInversion of Control container