Pass sequence of steps (methods) to window (wpf)

Next, Paul, what I understand is that you want a reusable canvas, I'll try to give you a light to give you continuity.

First, let me take your question below:

  

I would like to know if the BackgroundWorker would work, or if it would have to use a task, etc ... thanks for any help!

As Stephen Cleary explains in his Blog: link

  

BackgroundWorker is a type that should not be used in new code. Everything it can do, Task.Run can do better; and Task.Run can do a lot of things that BackgroundWorker can not!

Reading the article becomes clearer that the BackgroundWorker can, and should, be replaced by the Task. Remembering that the article is from 2013, it has been mentioned for 4 years.

On your issue, I made the following resolution:

I created a UserControl containing:

UserControl1.xaml

<Grid>
    <Label Content="OPERANDO" HorizontalAlignment="Center" FontSize="20"/>
    <ScrollViewer ScrollViewer.VerticalScrollBarVisibility="Auto" Margin="40">
        <StackPanel x:Name="spResultado" Background="White">

        </StackPanel>
    </ScrollViewer>
</Grid>

The UserControl code

UserControl1.cs

 public partial class UserControl1 : UserControl
{
    public UserControl1()
    {
        InitializeComponent();
    }

    public async Task<bool> ExecutaAcao(Func<bool> Acao)
    {
        Task<bool> task = new Task<bool>(Acao);
        task.Start();
        await task;
        return task.Result;
    }

    public void InformaAcao(string value)
    {
        TextBlock txt = new TextBlock { Text = value };
        spResultado.Children.Add(txt);
    }

    public void ExibeResultado(string value)
    {
        TextBlock txt = new TextBlock { Text = value, Foreground = Brushes.Green };
        spResultado.Children.Add(txt);
    }

}

Our UserControl is ready to receive the information (remembering that this is just an example).

The idea is to put that UserControl where you need it and pass the information for it to process.

In the Interface your Window add it:

Window.xaml

<local:UserControl1 x:Name="UserControl1"/>

In the code of your Window it looks like this:

Window.cs

 //CRIA UM FUNC QUE RETORNARÁ TRUE OU FALSO PARA 
        Func<bool> baixaArquivos = new Func<bool>(() =>
        {
            // SEU PROCEDIMENTO AQUI
            // REMOVER ESSE THREAD.SLEEP, COLOQUEI ELE APENAS PARA SEGURAR O PROCESSO POR 5s
            System.Threading.Thread.Sleep(5000);
            // CASO SEU PROCEDIMENTO TEVE SUCESSO, RETORNE TRUE
            return true;
        });

        Func<bool> removeArquivos = new Func<bool>(() =>
        {
            System.Threading.Thread.Sleep(5000);
            return true;
        });
        Func<bool> instalaSistema = new Func<bool>(() =>
        {
            System.Threading.Thread.Sleep(5000);
            return true;
        });

        //INFORMA O USUARIO SOBRE QUAL PROCESSO ESTÁ SENDO EXECUTADO
        UserControl1.InformaAcao("Inicia processo de download do arquivo");
        //EXECUTA DE MANEIRA ASSINCRÓNICA A FUNC CRIADA ACIMA E RETORNA O STATUS
        if (await UserControl1.ExecutaAcao(baixaArquivos) == true) { UserControl1.ExibeResultado("Sucesso no download"); } else { MessageBox.Show("Erro na operação"); return; }


        UserControl1.InformaAcao("Remove antigos arquivos");
        if (await UserControl1.ExecutaAcao(removeArquivos) == true) { UserControl1.ExibeResultado("Sucesso na remoção dos arquivos"); } else { MessageBox.Show("Erro na operação"); return; }
        UserControl1.InformaAcao("Instalando novo sistema");
        if (await UserControl1.ExecutaAcao(instalaSistema) == true) { UserControl1.ExibeResultado("Sucesso ao instalar sistema"); } else { MessageBox.Show("Erro na operação"); return; }

This was just an example, there are other ways to do this. You can do with or without UserControl , it is your criterion. You can also pass Action or something else in place of Func.

Any questions just ask. Good Luck