ioc-castle-windsor

AMIR BARYLKO

ADVANCED IOC
WINDSOR
CASTLE

DOT NET UG
NOV 2011

Amir Barylko - Advanced IoC MavenThought Inc.

FIRST STEPS
Why IoC containers
Registering Components
LifeStyles
Naming


WHY USE IOC

• Manage creation and disposing objects
• Avoid hardcoding dependencies
• Dependency injection
• Dynamically conﬁgure instances
• Additional features

REGISTRATION

• In order to resolve instances, we need to register them
Container.Register(
// Movie class registered
Component.For<Movie>(),

// IMovie implementation registered
Component.For<IMovie>().ImplementedBy<Movie>()
);


GENERICS

•What If I want to register a generic class?
container.Register(

Component

.For(typeof(IRepository<>)

.ImplementedBy(typeof(NHRepository<>)

);


DEPENDENCIES
Component
.For<IMovieFactory>()
.ImplementedBy<NHMovieFactory>(),

Component
.For<IMovieRepository>()
.ImplementedBy<SimpleMovieRepository>()

public class SimpleMovieRepository : IMovieRepository
{
public SimpleMovieRepository(IMovieFactory factory)
{
_factory = factory;
}
}


LIFESTYLE

• Singleton vs Transient

• Which one is the default? And for other IoC tools?

container.Register(
Component.For<IMovie>()
.ImplementedBy<Movie>()
.LifeStyle.Transient
);


RELEASING

• Do I need to release the instances?


NAMING

• Who’s the one resolved?
container.Register(
Component
.For<IMovie>()
.ImplementedBy<Movie>(),
Component
.For<IMovie>()
.ImplementedBy<RottenTomatoesMovie>()
);


NAMING II

• Assign unique names to registration
container.Register(
...

Component
.For<IMovie>()
.ImplementedBy<RottenTomatoesMovie>()
.Named("RT")
);

container.Resolve<IMovie>("RT");


JOGGING
Installers
Using Conventions
Depend On


INSTALLERS

• Where do we put the registration code?

• Encapsulation

• Partition logic

• Easy to maintain


INSTALLER EXAMPLE
container.Install(
new EntitiesInstaller(),
new RepositoriesInstaller(),

// or use FromAssembly!
FromAssembly.This(),
FromAssembly.Named("MavenThought...."),
FromAssembly.Containing<ServicesInstaller>(),
FromAssembly.InDirectory(new AssemblyFilter("...")),
FromAssembly.Instance(this.GetPluginAssembly())
);


XML CONFIG
var res = new AssemblyResource("assembly://.../
ioc.xml")

container.Install(
Configuration.FromAppConfig(),
Configuration.FromXmlFile("ioc.xml"),
Configuration.FromXml(res)
);


CONVENTIONS
Classes

.FromAssemblyContaining<IMovie>()

.BasedOn<IMovie>()

.WithService.Base() // Register the service

.LifestyleTransient() // Transient lifestyle


CONFIGURE COMPONENTS
Classes

.FromAssemblyContaining<IMovie>()

.BasedOn<IMovie>()

.LifestyleTransient()

// Using naming to identify instances

.Configure(r => r.Named(r.Implementation.Name))


DEPENDS ON
var rtKey = @"the key goes here";
container.Register(
Component
.ImplementedBy<RottenTomatoesFactory>()
.DependsOn(Property.ForKey("apiKey").Eq(rtKey))
);

.DependsOn(new { apiKey = rtKey } ) // using anonymous class

.DependsOn(
new Dictionary<string,string>{
{"APIKey", twitterApiKey}}) // using dictionary


SERVICE OVERRIDE
container.Register(
  Component
.ImplementedBy<IMDBMovieFactory>()
.Named(“imdbFactory”)

  Component
.For<IMovieRepository>()
.ImplementedBy<SimpleMovieRepository>()
     .DependsOn(Dependency.OnComponent("factory", "imdbFactory"))
);


RUN FOREST! RUN!
Startable Facility
Interface Based Factories
Castle AOP


STARTABLE FACILITY

• Allows objects to be started when they are created

• And stopped when they are released

• Start and stop methods have to be public, void and no
parameters

• You can use it with POCO objects specifying which method
to use to start and stop


STARTABLE CLASS
public interface IStartable
{
void Start();
void Stop();
}

var container = new WindsorContainer()
.AddFacility<StartableFacility>()
.Register(
Component
.For<IThing>()
.ImplementedBy<StartableThing>()
);


FACTORIES

• Common pattern to create objects

• But the IoC is some kind of factory too...

• Each factory should use the IoC then....

• Unless we use Windsor!!!!


TYPED FACTORIES

• Create a factory based on an interface

• Methods that return values are Resolve methods

• Methods that are void are Release methods

• Collection methods resolve to multiple components


REGISTER FACTORY
Kernel.AddFacility<TypedFactoryFacility>();

Register(
Component
.For<IMovie>()
.ImplementedBy<NHMovie>()
.LifeStyle.Transient,

Component.For<IMovieFactory>().AsFactory()
);


CASTLE AOP

• Inject code around methods

• Cross cutting concerns

• Avoid mixing modelling and usage

• Avoid littering the code with new requirements


INTERCEPTORS
Register(
Component
.For<LoggingInterceptor>()
Component
.For<IMovie>()
.ImplementedBy<NHMovie>()
.Interceptors(InterceptorReference
.ForType<LoggingInterceptor>()).Anywhere
);


LOGGING
public class LoggingInterceptor : IInterceptor
{
public void Intercept(IInvocation invocation)
{
Debug.WriteLine("Before execution");
invocation.Proceed();
Debug.WriteLine("After execution");
}
}


NOTIFY PROPERTY CHANGED
Register(
Component
.For<NotifyPropertyChangedInterceptor>()
Component
.For<IMovieViewModel>()
.ImplementedBy<MovieViewModel>()
.Interceptors(InterceptorReference
.ForType<NotifyPropertyChangedInterceptor>())
.Anywhere
);


QUESTIONS?

Amir Barylko - TDD MavenThought Inc.

RESOURCES

• Contact: amir@barylko.com, @abarylko

• Code & Slides: http://www.orthocoders.com/presentations

• Castle Project Doc: http://docs.castleproject.org


ioc-castle-windsor

Recommandé

Recommandé

Contenu connexe

Tendances

Tendances (9)

En vedette

En vedette (7)

Similaire à ioc-castle-windsor

Similaire à ioc-castle-windsor (20)

Plus de Amir Barylko

Plus de Amir Barylko (20)

Dernier

Dernier (20)

ioc-castle-windsor