Injectors generated by Source Generators not used when using multiple assemblies

[timlindeberg]

Hello! Thanks for the great work on VContainer!

I've encountered an issue using the VContainer.SourceGenerator.dll source generator together with multiple assemblies.

I can see that the injectors are being generated properly. However, in our project we use multiple assemblies with one top level assembly responsible for defining the LifetimeScope and registering all the dependencies. Since it's this assembly that contain all the builder.Register<T> statements, the Injectors get put into this assembly. When VContainer then tries to find the generated injector it can't find it and falls back to using the reflection injector since it only looks in the assembly where T is defined:

VContainer/VContainer/Assets/VContainer/Runtime/Internal/InjectorCache.cs

Line 16 in 0093a45

var generatedType = key.Assembly.GetType($"{key.FullName}GeneratedInjector", false);

This basically means that if you register dependencies in one assembly from another assembly it will never use the generated injectors. For us this means we can't really use the source generators since we need to be able to register and define dependencies in different assemblies.

[stroibot]

I seem to have kinda similar problems
I have multiple assemblies, noticed that only one source is generated

[playside-heath]

Same issue, we've noticed when we turn code stripping to high, even though source is being generated, it's not being used since it's in the wrong assembly. Effectively the source generator doesn't work at all for us since we split almost everything into its own assembly.