Projects

octanesandbox

Sample reference projects involving Winforms, Castle, IoC, ActiveRecord, Rhino, and others

ninject-contrib

A collection of community-created extensions and examples related to the Ninject dependency injection project.

wigloo

A new application framework for building Web applications using an MVC or MVP approach. It manages the lifecycles of the application components automatically using the design pattern IOC also known as "Inversion of Control". The developer interacts with components by retrieving and storing ... [More] them from and into the different context such as Session context, Request Context, Applictaion Context... Using Castle Winstor container and inspired by JBoss Seam. [Less]

pinsor

Project GoalsCut down lines of code for Python work. Ease use of S.O.L.I.D. principles when working with Python. Give Python and dynamic languages an IoC container that is based on more recent implementations. IntroductionIf you know what an IoC container isPinsor aims for convention over ... [More] configuration and what configuration is needed is done only in code. It also is able to be used with minimal modification to existing source code. Extensibility will be achieved through "facilities" that tie together the core container and additional functionality. Finally, limited AoP support will help remove the need to spread decorators over methods and match by rule, or specific reference to a classes method. If you do not know what an IoC(Inversion Of Control) container isI'm pretty convinced Inversion Of Control is a term used to scare off developers new to the concept. It's also related to a term you'll hear bandied about a lot called Dependency Injection Principle or DIP (sometimes just called DI), this also is designed to scare people. End of the day Pinsor is designed to have you use less lines of code usually by resolving your dependencies for you (see samples). This also has the nice side effect of making your code easier to change and easier to configure. You may use the container as much or as little as you want in your project, what matters is you use it in a way to save yourself some typing and maintenance pain, if it's not doing that for you, no one will think less of you if you remove it from your code. If You still want to know what does Inversion Of Control/Dependency Injection mean?You're a glutton for punishment but I was there once myself. I know now this is actually a deceptively simple concept that's been made out to be a lot more than it is. Martin Fowler has the most thorough explanation I've found and I can't hope to compete, but here is where I originally learned about the concept. If you're interested I have summary as I see it. Other Links Of InterestProject Road Map Code Samples Gettting Started [Less]

castleautogen

AutoGen for Castle is an implementation of the abstract factory pattern for Castle Windsor. It is not to be confused with the existing abstract factory facility in Castle, which allows Castle to use abstract factories. Rather, it allows the automatic generation of abstract factories on the basis ... [More] of the behaviour of the kernel. It is similar to the TypedFactoryFacility within Windsor, but goes further. For instance, assume an Interface and an implementation public interface IExample {} public class Example : IExample {}These are registered in the obvious way. var container = new WindsorContainer(); container.Register( Component .For() .ImplementedBy() .LifeStyle.Transient);Now, you can define an interface specifying your interaction with the container. public interface IFactory { IExample CreateExample(); }Finally, you just call AutoGen and it generates the code: var factory = container.AutoGen(); var result = factory.CreateExample(); Assert.That(result is Example);Alternatively, if you wanted to inject the factory into another class, you can register it as follows: container.Register( Component .For() .AutoGen() );The basic motivation of this is that it enables you to specify your exact interaction with the container, and remove references to the container from your own code. Features: Full support for parameters, passing through to constructors. Supports key parameters, both to specify the key of the return value, and to specify the key of a parameter. Supports injection of abstract factories into the container Supports Castle fluent configuration style Requires no changes to Castle: just use your own builds. Uses simple non-invasive convention based system for ease of use. Attribute based system for those who need more control. Can implement the Common Service Locator in one line. The one line, incidentally, is as follows: var csl = container.AutoGen(typeof(ActivationException))Limitations: No support for curried factories. No diagnosis of mapping problems over and above Castle's own. Disposal is not proxied when the service type is a concrete class. You shouldn't be declaring concrete service types anyway. [Less]

AgentMulder

Agent Mulder plugin for ReSharper provides navigation to and finding usages of types registered or resolved via Dependency Injection (DI) containers.