Skip to content

Split the IoC installer into one for each project #5140

Open
@MDoerner

Description

@MDoerner

Currently, we have one monolithic IoC installer in Rubberduck.Main. Let us split it into separate ones for each project. Then the main IoC installer can use the individual ones to load the assembly specific types. The overall conventions would stay in the main IoC and be used from there.

This change would put the special registrations closer to the code they belong to and allow to load only parts of the registration in places like the API. (This would still require a shortened version of the overall conventions, though.)

The downside would be that there is no longer one place to look for all registrations.

Metadata

Metadata

Assignees

No one assigned

    Labels

    development-issueIssues encountered while developing RD, not in RD itselftechnical-debtThis makes development harder or is leftover from a PullRequest. Needs to be adressed at some point.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions