Vxpsd.Write(objNewPage) ', objPrintTicket) ObjPrintTicket.Duplexing = Duplexing.Unknown ObjPrintTicket.Duplexing = Duplexing.TwoSidedLongEdge
ObjPrintTicket.Duplexing = Duplexing.TwoSidedShortEdge ObjPrintTicket.Duplexing = Duplexing.OneSided ObjNewPage = objMarkupPage.Apply(objXPSPage)ĭim objPrintTicket As New ' The next line adds a FixedPage and applys it and an "overlay" into a ContainerVisual I hope that this helps.ĭim vxpsd As .SerializerWriterCollator Although I am having the problem mentioned eariler about opening files over 30,000 pages. When I am printing large files I am not seeing the increase in memory. Not very funny you can guess yourself, as I need to print up to 50,000 pages for example.Īlso the heavy RAM usage ofcourse drops down the printing-speed the more it eats up (also that damn "c:\temp\ouput.xps"-port is a performance killer - but I have to use it as something like the StartDoc-Api is missing in XPS-PrintPath). On my test app I just printed one fixedPage/Visual (without merging it with another visual) and I saw memory increased by ~5MB each time I pressed the button.
(even a Microsoft support guy said he can reproduce the behaviour, but he had no clue why it is like that.)
Microsoft xps document writer missing free#
I have also checked if I could free some objects on my own (or try to force the GC), but the most objects doesn't have a dispose() method, so I assume there must be a bug in XPS not cleaning up properly after printing each page.
then I just have loaded each FixedPage, merged it with another Visual (as some kind of overlay) and printed it via the visuals-batchwriter on a legacy printer. it was a simple word-documents, which I have printed for my test to XPS before. No it wasn't graphics intense pages - just some tables and text.
0 kommentar(er)
