IoC for Infrastructure wiring.
C#
Switch branches/tags
Nothing to show
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Failed to load latest commit information.
.nuget
CH.IoC.Fake
CH.IoC.Infrastructure.Wiring
CH.IoC.Infrastructure
CH.IoC.Test
CH.IoC.TestBoot
CH.IoC.TestHost.Interface
CH.IoC.TestHost
CH.IoC.TestIsolated.0
CH.IoC.TestIsolated.1
CH.IoC.TestIsolated.2
CH.IoC.TestLog.0
CH.IoC.TestLog.1
CH.IoC.TestLog.2
CH.IoC.TestLog.Interface
CH.IoC.TestPlugin.Interface
CH.IoC.TestPlugin
CH.IoC.TestSrv.Interface
.gitignore
AssemblyVersion.exe
CH.IoC.sln
CH.IoC.sln.DotSettings
README.md
version.txt

README.md

#ch-ioc

IoC for Infrastructure wiring.

One use of IoC containers for wiring up the infrastructure of a program at startup. These projects aim to make that setting up infrasture easier.

Infrasture classes used to be implemented as static classes, and would directly reference each other. This makes testing infrastructure difficult as there was no way to decouple the components and mock their dependents.

Using IoC we can build a container (a resolver) of instances for our infrasture and have each infrastructure class implement an interface and take into its constrcutor the interfaces of the other infrastructure classes it uses. Now to test an infrastructure class we can create an instance of it using mocks for the other infrastructure systems it uses.

We also want to be able to address multiple sub-systems that provide a common interface. Plugins (think photoshop) fall into this category, as they are loaded once at start up. If a constructure takes in an IEnumerable<interface_type> it will get an enumerable of all the infrastucture components that implement the interface_type (arrays also work). The bootstrapping code that builds the container will scan the executable directory for all dll's matching a list of prefixes and load them, so plugins can be dropped into place.

Example Usage: See the CH.Ioc.Test projects for an example of how this should be used.

Note: The TestHost and TestPlugin output paths are set to build to the Test project's bin directory so the components will be loaded dynamically.

CH.IoC.Infrastructure

Provides a Resolver class. This should be constructed once during your programs bootstrapping process, and disposed of once during your program shutdown. Programs should have a main interface (host, etc.) that they resolve and pass off execution too. The components in the infracture should have no knowledge of the resolver since the resolver doesn't provide support for life times. (For lifetimes that are one-per-resolver add an infrastructure component that is a factory for those objects.)

Only the program's main assembly should reference this assembly.

CH.IoC.Infrastructure.Wiring

All infrastructure components should reference this assembly, and not the Infrastructure assembly. Classes that want to be wired by default (non-test environments) as their interfaces (yes, all of them) should be marked with the Wire attribute. You can provide a list of types to the attribute if you don't want all the interfaced wired.

CH.IoC.Test...

These assemblies are a test/example of how to use the system.

Note: Since there are no direct dependencies between .Test and .TestHost and .TestPlugin you must build .TestHost and .TestPlugin explicitly before running .Test. This is by design, since we want to decouple the execution environment from the concrete components it executes.