Pragmatik Dev · Dependency injection · Unity 6000.x
Fast DI for scene-first Unity projects.
Attribute-first wiring for MonoBehaviour-heavy projects:
declare [Inject(Scopes…)] on fields and resolve via hierarchy walks, scene registries
or global singletons.
Billing, VAT, and refunds are handled by Unity per Asset Store policy.
Why teams choose a lightweight DI
Attributes and scoped lifetimes without committing to an installer-heavy container for every prototype.
Scene-native mental model
Scene services are discovered where they live; additive loads map naturally to per-scene backing stores.
Editor guardrails
Validate the whole active scene, toggle verbose resolve tracing, and drop a diagnostics host when you need visibility.
Test Driven Development
Write your code using industry standard methodologies that are widely used
Public API (high level)
Inherit from InjectableBehaviour (using PragmatikDev.FastDI;, [DefaultExecutionOrder(-32000)] built-in) and tag fields with [Inject(Scopes.Scene)] (etc.). Injections are idempotent: already-assigned serialized references are left untouched.
Scopes.Hierarchy— walk self, parents, then descendants for Components / interfaces.Scopes.Scene— singleton-per-scene backing store with MonoBehaviour discovery or POCOnew().Scopes.Singleton— shared CLR bucket keyed by type; register withRegisterSingletonService<T>.SceneInjection.RegisterSingletonService<T>(...)/RegisterSceneService<T>(...)for explicit service overrides.
Detailed footguns (execution order clashes, DontDestroyOnLoad, additive scenes, domain reload) live in package DOCUMENTATION.md beside the distributor notes in Portfolio/products/fast-di.md.
Suggested workflow after purchase
From zero to confidently merged pull request:
1. Import the package
Copy Assets/PragmatikDev/FastDI/ into your project. Optionally enable PragmatikDev.FastDI.TutorialFlat for reference MonoBehaviours and checked-in tutorial scenes.
2. Build a sandbox scene
Follow Feature tutorials — each section lists manual Hierarchy steps plus code. Optionally mirror FastDiDemoShowcase types from the Tutorials asmdef for a Scene + GameObjectSingleton smoke test.
3. Wire + validate
Press Play locally, hit Validate Active Scene, migrate one vertical slice using InjectableBehaviour, then iterate.
FAQ
Where do I purchase?
Use the Unity Asset Store buttons on this page. When the listing URL is configured, the primary button opens the official product page; until then you can follow the publisher link to browse other assets.
Which Unity versions are supported?
Target support is Unity 6 (6000.x). Always check the package’s Store compatibility list before upgrading a production project.
How does this compare to larger DI libraries?
Fast DI optimizes for scene-local clarity and low ceremony. Larger frameworks offer broader feature sets — pick based on shipping constraints, team size, and appetite for tooling complexity.
How do I run the automated tests?
Open Unity’s Test Runner window, select PragmatikDev.FastDI.Tests.EditMode and PragmatikDev.FastDI.Tests.PlayMode, then run all. CI can invoke the same assemblies via Unity’s batch test runner.
Ready to wire smarter scenes?
Grab the Asset Store listing when live, or explore the publisher catalog today.
Billing, VAT, and refunds are handled by Unity per Asset Store policy.