The resource processor now indirectly consumes ISettingsManager (Because the new Configurable Content Provider needs it). But that failed because the settings manager is declared later in the DI setup. Ideally ordering like this doesnt matter with DI but there are some custom injection mappings happening that cause things to resolve before the whole thing is setup. Easiest thing to do was move its declaration so it's after the settings manager declaration.