5

From Sitecore documentation: Pipelines define a sequence of processors that implement a function, such as defining the Sitecore context for an HTTP request or generating a list of messages in the Content Editor. Pipelines assist with encapsulation, flexible configuration, separation of concerns, testability and other objectives. Each processor in a ...


4

As has been pointed out in other answers, <processors> are used primarily for UI-related activities. They must be executed via Sitecore.Pipelines.PipelineFactory and Sitecore.Pipelines.Pipeline instead of Sitecore.Pipelines.CorePipeline. Functionally, the main difference appears to be that these UI pipelines have the ability to suspend while waiting ...


4

Sitecore separates the pipelines into two groups: 1. Those defined within the /configuration/sitecore/pipelines- [These pipelines tend to define system processes.] Examples: <initialize>:Initializes the Sitecore application. <preprocessRequest>: This is invoked for each HTTP request managed by ASP.NET. It is more common to use the pipeline for ...


2

You've not shared the actual classes in question, so I have to extrapolate. But if you have public abstract ClassA { public ClassA(IDependency dependencyOne) { ... } } public ClassB : ClassA { public ClassB(IDependency dependencyOne, string connectionStringName) : base(dependencyone) { ... } } Then this would be ...


Only top voted, non community-wiki answers of a minimum length are eligible