Question 1

How do I use StrongInject with ASP.NET Core?

Accepted Answer

Integrate by implementing IContainer<T> for controllers or using modules, as shown in the ASP.NET Core sample project; you'll need to resolve controllers as top-level services while minimizing their number for non-invasive design.

Question 2

StrongInject vs Microsoft.Extensions.DependencyInjection: which should I choose?

Accepted Answer

Choose StrongInject for compile-time safety and performance in reflection-sensitive environments, but prefer Microsoft's DI for its maturity, broader ecosystem, and simpler setup in convention-based projects.

Question 3

How to register a decorator for logging or timing?

Accepted Answer

Use the [RegisterDecorator] attribute or a decorator factory method, as demonstrated with ServiceTimingDecorator, which wraps services to intercept calls without modifying original implementations.

Question 4

Does StrongInject support circular dependencies?

Accepted Answer

The README doesn't explicitly address circular dependencies; likely, they are discouraged due to compile-time checks, but you can use delegates or Owned<T> to break cycles manually.

Question 5

How to handle async disposal in my services?

Accepted Answer

Implement IAsyncDisposable on your types, and StrongInject will call DisposeAsync when using RunAsync or ResolveAsync, ensuring proper cleanup of async resources as per the disposal section.

Question 6

Can I resolve all implementations of an interface?

Accepted Answer

Yes, register multiple types as the same interface and resolve an array of that interface; StrongInject will collect all instances, with deduplication for duplicate registrations.

StrongInject

What is StrongInject?

Overview

Use Cases

Best For

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions