System.Windows.Xps Namespace ()

Switch View :
ScriptFree
.NET Framework Class Library
System.Windows.Xps Namespace

Provides classes that write XPS documents to a data store or print queue.

The XpsDocumentWriter class provides the Write and WriteAsync methods that output XPS documents to a data store or print queue. Separate groups of write methods are provided for different content types including DocumentPaginator, Visual, FixedPage, FixedDocument, and FixedDocumentSequence. The XpsDocumentWriter methods enable you to also include a PrintTicket with the document, plus pass additional information to the handlers of the WritingCompleted, WritingProgressChanged, and WritingPrintTicketRequired events.

For more information about XPS see the XML Paper Specification (XPS) available for download at http://go.microsoft.com/fwlink/?LinkID=65761.

Classes

  Class Description
Public class VisualsToXpsDocument Provides methods for writing Visual objects to XML Paper Specification (XPS) documents or to a print queue in batch mode. 
Public class XpsDocumentWriter Provides methods to write to an XPS document or print queue.  
Public class XpsException Serves as the base class for exceptions that are thrown by the XML Paper Specification (XPS) packaging and serialization APIs. 
Public class XpsPackagingException The exception that is thrown when reading, writing to, registering, or accessing in some other way an XpsDocument.
Public class XpsSerializationException The exception that is thrown for XML Paper Specification (XPS) document serialization errors. 
Public class XpsWriterException The exception that is thrown when a method of either an XpsDocumentWriter or a VisualsToXpsDocument object is called that is incompatible with the current state of the object.
Enumerations

  Enumeration Description
Public enumeration XpsDocumentNotificationLevel Indicates whether a write operation to an XML Paper Specification (XPS) document or a print queue sends back page-by-page and document-by-document progress notifications.
See Also

Reference

Other Resources

Community Content

Haastastic
Why doesn't MS provide a better XPS API?
I am creating a web-based mail merge application.  XPS seemed like it would be a good option, considering the quality of support MS provides to its developers.  I was wrong.  The learning curve for the current API is much steeper than it should be.  Why must I write XML?  Why aren't their text and image objects that take care of the xml for me?  Wake up!