When is using DI and optionally a IoC framework a step too far?
Consider a logging system – used absolutely everywhere in your codebase.
Dependency injection ; good practices to reduce boilerplate code
I have a simple question, and I’m not even sure it has an answer but let’s try.
I’m coding in C++, and using dependancy injection to avoid global state. This works quite well, and I don’t run in unexpected/undefined behaviours very often.
DI: Can a stable dependency have a volatile dependency?
I’ve recently been reading through Mark Seemann’s Dependency Injection in .NET and have been attempting to apply some of what I’ve learned in a new project I’m working on, and I’m stumped on a particular scenario trying to determine what dependencies I should and should not inject. I’ve read several other questions on SO and elsewhere that discuss similar scenarios but in a roundabout manner, and I think I’ve narrowed the underlying conceptual question to that which is in the title:
Does following TDD inevitably lead to DI?
I learned to do Test Driven Development (TDD), Dependency Injection (DI) and Inversion of Control (IoC) all at the same time. When I write code using TDD I always end up using DI in my class’s constructors. I am wondering if this is because of how I learned to do TDD, or if this is a natural side-effect of TDD.
Who should initialize dependencies in a TDD application?
I’m trying to learn implementing TDD with mocking/fake objects. One of the questions I have is how to initialize a dependency in an application which implements TDD? An example from this article
Beginning Mocking With Moq 3 shows:
Difference between spring setter and interface injection?
I know how constructor and setter injection works in spring.
Dependency injection with n-tier Entity Framework solution
I am currently designing an n-tier solution which is using Entity Framework 5 (.net 4) as its data access strategy, but am concerned about how to incorporate dependency injection to make it testable / flexible.
How to use DI and DI containers
I am building a small PHP mvc framework (yes, yet another one), mostly for learning purposes, and I am trying to do it the right way, so I’d like to use a DI container, but I am not asking which one to use but rather how to use one.
How to use DI and DI containers
I am building a small PHP mvc framework (yes, yet another one), mostly for learning purposes, and I am trying to do it the right way, so I’d like to use a DI container, but I am not asking which one to use but rather how to use one.
Dependency injection and IOC containers in a closed project
Does it make sense to assemble my project with dependency injection containers if I am the only one who will use the code of that project?