vcontainer

VContainer enables Unity dependency injection without singletons by using hierarchical LifetimeScope composition. You register explicit interface-to-implementation bindings and scoped resolutions, ensuring plain C# systems and MonoBehaviours receive dependencies automatically across parent-child scopes.

The difference is that constructor injection applies to plain C# classes for explicit dependencies, while method injection using the [Inject] attribute applies to MonoBehaviour components. This distinction keeps dependencies explicit and makes components loosely connected and easier to test.

You configure scene-specific service overrides by composing dependencies with a parent-child LifetimeScope structure. Register project-wide services like audio and analytics at a root scope, then safely override them with scene-specific score or spawn systems in child scopes.

Yes, VContainer supports configurable composition allowing you to register existing instances like ScriptableObject data and create runtime objects via factories. This ensures consistent lifecycles and explicit registration of lifetimes across your Unity application architecture.

VContainer works with both plain C# systems and MonoBehaviour components. It applies constructor injection for plain C# classes and method injection with lifecycle entry points for MonoBehaviour components, keeping dependencies explicit across your Unity architecture.

Brittle Unity coupling occurs when components are tightly connected without managed dependency injection. VContainer solves this by providing a lightweight approach using hierarchical LifetimeScope composition and explicit bindings, keeping components loosely connected and easier to test.