How to call Task from another Task.

[FlorianWDP]

As the title says, i want to use a Task as an entry point, which parses all my projects and then calls another Task for each project.
I want to trigger the chain of dependencies on the Task that is called.

[TaskName("PublishAll")]
    public class PublishAllTask : FrostingTask<BuildContext>
    {
        public override void Run(BuildContext context)
        {
            PublishTask publishSingleTask;
            if (context.IsTagBuild)
            {
                publishSingleTask = new ReleasePublishTask();
            } 
            else
            {
                publishSingleTask = new CiPublishTask();
            }

            foreach (var project in context.GetFiles(...))
            {
                context.ProjectName = project./.../;
                
                publishSingleTask.Run(context); //only call the Run method and does not resolve [IsDependentOn] 
            }
        }
    }

[pascalberger]

What's the reason you try to split this across multiple tasks instead of handling it inside a single task?

[TaskName("PublishAll")]
public class PublishAllTask : FrostingTask<BuildContext>
{
    public override void Run(BuildContext context)
    {
        foreach (var project in context.GetFiles(...))
        {
            PublishProject(project)
        }
    }

    private void PublishProject(BuildContext context, FilePath project)
    {
        if (context.IsTagBuild)
        {
            PublishProjectRelease(context, project);
        } 
        else
        {
            PublishProjectCi(context, project);
        }
    }

    private void PublishProjectRelease(BuildContext context, FilePath project)
    {
    }

    private void PublishProjectCi(BuildContext context, FilePath project)
    {
    }
}

[EdLichtman]

I'm still working through stuff myself, but couldn't you just pass the task in through the dependency injection framework via the constructor?

Or, alternatively, take the logic of the actual publish out of the task itself, and use the task as a form of abstraction, then you can invoke the other task's logic via the logic runner that's no longer in the task.