I want to be able to create "reports" as regular MVVM views, so to test this idea I created the following view. It just consists of a bound textblock, an ItemsControl (bound to a collection of a few hundred strings), and a second text block:

<UserControl ...>
    <UserControl.Resources>
        <DataTemplate x:Key="myListItemTemplate">
            <TextBlock Text="{Binding}"
                       Foreground="Blue" />
        </DataTemplate>
    </UserControl.Resources>

    <FlowDocument x:Name="flowDoc">
        <BlockUIContainer>
            <StackPanel Orientation="Vertical">
                <TextBlock Text="{Binding Message}" />
                <ItemsControl ItemsSource="{Binding SomeList}"
                              ItemTemplate="{StaticResource myListItemTemplate}" />
                <TextBlock Text="THE END" />
            </StackPanel>
        </BlockUIContainer>
    </FlowDocument>
</UserControl>

I print the view using a DocumentPaginator like this:

private void Print(IPrintableView view)
    {
        var dlg = new PrintDialog();
        if (!dlg.ShowDialog().GetValueOrDefault())
        {
            return;
        }

        var paginator = new MyDocumentPaginator(
            view.FlowDocument,
            new Size(dlg.PrintableAreaWidth, dlg.PrintableAreaHeight),
            new Size(DefaultMarginWidthDpi, DefaultMarginHeightDpi));

        dlg.PrintDocument(paginator, "My print job");
    }

Unsurprisingly the document isn't being paginated, and produce a 1-page report that gets truncated partway through the list. (I don't believe my document paginator implementation is important here, which simply adds a header and footer to each page, and I see the same issue if I use the FlowDocument's own FlowDocumentPaginator).
As I now understand it, document paginators will only break on " Block " controls, so I modified the xaml to wrap each control in a BlockUIContainer :

<UserControl ...>
    <UserControl.Resources>
        <DataTemplate x:Key="myListItemTemplate">
            <TextBlock Text="{Binding}"
                       Foreground="Blue" />
        </DataTemplate>
    </UserControl.Resources>

    <FlowDocument x:Name="flowDoc">
        <BlockUIContainer>
            <TextBlock Text="{Binding Message}" />
        </BlockUIContainer>
        <BlockUIContainer>
            <ItemsControl ItemsSource="{Binding SomeList}"
                          ItemTemplate="{StaticResource myListItemTemplate}" />
        </BlockUIContainer>
        <BlockUIContainer>
            <TextBlock Text="THE END" />
        </BlockUIContainer>
    </FlowDocument>
</UserControl>

Here, a page break now occurs after the first TextBlock, with the list starting on page 2 (but still being truncated at the end of that page), and the second textblock appearing on page 3.
I assume the paginator is measuring and rendering the entire ItemsControl as a whole, so I then tried placing each list item inside a BlockUIContainer via the ItemContainerStyle:

<ItemsControl.ItemContainerStyle>
    <Style TargetType="ContentPresenter">
        <Setter Property="ContentTemplate">
            <Setter.Value>
                <DataTemplate>
                    <BlockUIContainer>
                        <ContentPresenter Content="{Binding}" />
                    </BlockUIContainer>
                </DataTemplate>
            </Setter.Value>
        </Setter>
    </Style>
</ItemsControl.ItemContainerStyle>

This made no difference though. Is there a way to get this working? Am I even approaching this in the right way? Placing every UI control inside a "block" seems very cumbersome, especially when it the time comes to implement a real report containing a lot of complexity. The real reports won't necessarily be list based either, and are more likely to contain a mixture of controls - text, images, lists, etc. in a fairly free-style layout (more web page than banded report).