Register implementations in diferent projects

[fredericoregateiro]

Hi,
I'm trying to use Pure.DI in a Avalonia multitarget project, where some interfaces are implemented on each corresponding project.

One example, I create a IBiometricAuth interface in the shared project, and I create a BiometricAuth implementation in the Android project and other BiometricAuth implementation in the desktop project.

Is this even possible to achieve with Pure.DI?

[NikolayPianikov]

@fredericoregateiro, yes, of course, you can use Pure.DI to work with multiple projects and assemblies simultaneously. You can specify any types in the bindings, regardless of their location.

Perhaps your question is about where to setup DI and about reusing settings between assemblies or projects? If so, the answer is as follows:

• It's best to configure DI directly in the application's root project (Shell), please see details below. The type access modifier must support this.

• All DI configuration is performed at compile time, so all this metadata is not used at runtime, and this information can even be removed from runtime (for example, using the Conditional attribute on the composition class). Reuse is possible, for example, by copying the DI configuration file to the desired project. Reuse is also possible through libraries packaged in NuGet packages. Please see this example.

Quote from the book "Dependency Injection" by Mark Seemann:

When you write loosely coupled code, you create many classes to create an applica-
tion. It can be tempting to compose these classes at many different locations in order
to create small subsystems, but that limits your ability to INTERCEPT those systems to
modify their behavior. Instead, you should compose classes in one single area of your
application.
When you look at CONSTRUCTOR INJECTION in isolation, you may wonder, doesn't
it defer the decision about selecting a DEPENDENCY to another place? Yes, it does, and
that's a good thing. This means that you get a central place where you can connect col-
laborating classes.

[fredericoregateiro]

@NikolayPianikov Thanks for the rapid response.

I've looked at the example, that's a clever trick, using the file as a link, something I hadn't thought of.

My problem with this kind of project is that i need to use the implementations on the library, but they only exists in the Android or Desktop projects.
I've created a small project here can you take a look?

Thanks

[NikolayPianikov]

@fredericoregateiro sorry for the delay in responding. The problem is that the direction of dependencies for projects does not match the direction of dependencies for DI settings. Fixed in this PR.

[fredericoregateiro]

@NikolayPianikov thanks for all the help.
I really need to get my head on the use files as links on other projects.