locked
xml winrt printing

    Question

  • Windows 8 winrt .net printing is XAML based. 

    You create a PrintDocument and AddPages which are rooted at UIElement.

    This would persume that all pages could be held in memory or is UIElement able to dynamically load and unload?   Looks like its build to for games only or a tiny Windows Store App that would print maybe a couple of pages.

    It looks like only the Direct2D printing in C++/CX is able to handle 10000+ page documents where in old way of printing in GDI/GDI++ (Win32) we could always print pages in a non-retained manner.  Not so from Winrt .NET implementation.

    I'm I missing something here?

    You cannot create you own IPrintDocumentSource full implementation in WinRT .NET as some of the required interfaces are not WinRT interfaces such as:

    IPrintDocumentPageSource

    IPrintPreviewPageCollection

    http://msdn.microsoft.com/en-us/library/windows/desktop/hh448420(v=vs.85).aspx

    Any thoughts out there on this issue?

    Wednesday, June 5, 2013 2:27 PM

All replies

  • Hi PEERNET Inc. _,

    Based on your description, I'll move this thread to Building Windows Store apps with C++ to get more response. There will be more experts to help you.

    Thanks for your understanding.

    Best regards,


    Chester Hong
    MSDN Community Support | Feedback to us
    Develop and promote your apps in Windows Store
    Please remember to mark the replies as answers if they help and unmark them if they provide no help.

    Thursday, June 6, 2013 9:10 PM