Is it considered bad form to register components in Windsor without specifying an interface? i.e. container.Register(Component.For<MyClass>().LifeStyle.Transient);
I am migrating my mvc web app to use Nhibernate Facility to manage Nhibernate sessions. I am encountering this strange problem;
I am calling Kernel.RemoveComponent on my Windsor container and it is returning false. I know the component is present (I have verified by calling GetHandler with the same key and it returns the expec
I\'m trying to set up some Moq repositories to test my service with Castle Windsor as my IOC.Mu service depends on IFoo, so I\'m creating a moq instance 开发者_如何学编程that implements IFoo and injec
I\'m trying to use Windsor as a factory to provide specification implementations based on subtypes of XAbstractBase (an abstract message base class in my case).
I am injecting HttpContextBase into a caching class. HttpContextBase is registered as PerWebRequest. I interact with the caching class on each web request and this works fine, but I also need to initi
I’m fairly new to IoC and perhaps my understanding of generics and inheritance is not strong开发者_Python百科 enough for what I’m trying to do. You might find this to be a mess. I have a generic Rep
How can I use my Windsor container to check if an instance (not just a component) has been registered?
windsorContainer.Register( Component.For<ClassWithReferenceToDisposableService>() .LifeStyle.Transient
I have the following component mapping in Windsor xml: <component id=\"dataSession.DbConnection\" service=\"System.Data.IDbConnection, System.Data, Version=2.0.0.0, Culture=neutral, PublicKeyToken