Castle Windsor?

Current License: CC BY-SA 3.0

9 events

when toggle format	what		by	license	comment
Apr 4, 2016 at 15:57	history	bounty ended	B. Clay Shannon-B. Crow Raven
Jan 13, 2014 at 20:25	comment	added	B. Clay Shannon-B. Crow Raven		I would rather just be able to quickly "swap out" a test vs. a "real" (production) concrete class.
Jan 13, 2014 at 20:02	comment	added	Joshua Dutton		I'm not sure what you mean by "test implementation" unless you're referring to automates tests (unit tests), in which case CW should not be responsible for providing it. Instead, look at a mocking framework such as Moq.
Jan 13, 2014 at 16:37	comment	added	B. Clay Shannon-B. Crow Raven		Thanks; I'll czech that link again. I will want two always, a "test" one and the real one for each case. I want to easily switch between "use the test implementation" and "use the production implementation." If it's not easy to do that, the viability of DI and/or CW is reduced considerably; for me, anyway.
Jan 11, 2014 at 21:21	comment	added	Joshua Dutton		If you only have one implementation to be used at a time, I would say delete the old binding and create a new one. If you're worried about somehow losing the old binding, it should be in your source control system. If you want multiple implementations working at the same time, you'll need to specify conditional bindings. See the link I posted at the end of my answer.
Jan 9, 2014 at 18:03	comment	added	B. Clay Shannon-B. Crow Raven		So how do you tell Castle Windsor: For now, use this concrete class instead of that one? Is it a matter of temporarily commenting out the implementation that you don't want to be used, or...???
Jan 9, 2014 at 17:50	vote	accept	B. Clay Shannon-B. Crow Raven
Jan 9, 2014 at 2:18	review	First posts
Jan 9, 2014 at 7:26
Jan 9, 2014 at 2:02	history	answered	Joshua Dutton	CC BY-SA 3.0