Guidelines for printing

Applies to Windows only

Follow these guidelines when allowing users to print content from your Windows Store apps.

To learn how to add print capabilities to your app, see Quickstart: Printing from your app (Windows Store apps using JavaScript and HTML) or Quickstart: Printing from your app (Windows Store apps using C#/VB/C++ and XAML).

Dos and don'ts

  • Display an error message when a user enters invalid info in the print window. Be sure to specify a corrective action and limit error messages to two lines or less.
  • Don't use a print button in your app unless it's necessary for a specific task. In general, users should print using the Devices charm. However, in some circumstances, adding a print button might simplify a user's experience. For example, if a user expects to see a button to print a boarding pass after checking in to an airline, using the print charm might complicate the task.
  • Don't change the order of the settings shown in the print window. Although the order of the settings shown to the user is customizable, retain the default order of settings to maintain a consistent experience for users. For example, the Copies settings are listed first in the default print experience; users expect this listing order in your app’s print experience too.
  • Don't add more printer settings to the print window unless absolutely necessary. Instead, allow printer manufacturers to handle the addition of printer-specific settings. If the manufacturer provides printer-specific settings, users can click More Settings in the print window to display additional settings (assuming that the user has installed the Windows Store device app that enables this display).

For developers

  • Do the least amount of work possible to create the print task in the PrintTaskRequested event handler. Save more expensive work for when the PrintTaskSourceRequestedHandler is called to retrieve the printable content.
  • Don’t register the PrintTaskRequested event on pages of your app that don’t support printing. When PrintTaskRequested is registered, Window assumes that printing is supported and will let users try to print. For example, if your news app doesn’t support printing from its landing page, but does support printing from content pages, PrintTaskRequested shouldn’t be registered when the landing page is in view.

Note  Blob contents can only be printed in full fidelity when you use a reusable URL. For more information, see Accessing the file system efficiently.

If you'd like to learn how to add printing to your app, see Quickstart: Printing from your app (Windows Store apps using JavaScript and HTML) or Quickstart: Printing from your app (Windows Store apps using C#/VB/C++ and XAML). For detailed overview of this topic, download the Developing Windows Store device apps for printers whitepaper.

Related topics

For developers (HTML)
Quickstart: Printing from your app
For developers (XAML)
Quickstart: Printing from your app
Sample
Print sample app
Reference
PrintManager
PrintTask
PrintTaskOptions
PrintTaskRequested
PrintTaskSourceRequestedHandler

 

 

Show:
© 2014 Microsoft