330 likes | 1.41k Views
HW-238T. Connecting printing devices to Windows using v4 printer drivers. Justin Hutchings Program Manager Frank Gorgenyi Software Development Engineer Microsoft Corporation. Agenda. Using a v4 print driver to customize the print experience v4 print drivers in the enterprise
E N D
HW-238T Connecting printing devices to Windows using v4 printer drivers Justin Hutchings Program Manager Frank Gorgenyi Software Development Engineer Microsoft Corporation
Agenda • Using a v4 print driver to customize the print experience • v4 print drivers in the enterprise • Developing a v4 print driver • You’ll leave with examples of how to: • Use a v4 print driver to showcase the unique value of your device • Build a high quality v4 print driver
V4 print drivers provide the best print experience on Windows 8.
Building a Metro style printer experience v4 app + + Metro style printer app A great device! v4 print driver Device Metadata
Building a desktop printer experience v4 app + + printer extension A great device! v4 print driver
demo Printer extension
What you just saw • NET 4.0 application supporting printer preferences • Uses PrintTicket/PrintCapabilities for features • Uses Bidi for ink status • .
V4 print drivers make it easier and faster to manage print servers.
V4 print drivers reduce IT management costs • IT admins spend less time managing print servers • v4 print drivers share to all supported Windows clients • No cross-architecture driver management • Printer extensions distributed like any other software • Uses familiar tools for print queue management • Print Management Console • PowerShell
V4 print driver performance improvements • Reduced installation time • Reduced file I/O • Reduced disk footprint • Eliminated driver file name collisions • Faster sharing with enhanced Point and Print
demo Enhanced Point and Print Server: Windows Developer Preview Client: Windows 7 SP1
Architecture of a v4 print driver App that prints Spooler Printer UI Configuration Rendering Device Connectivity
Architecture of a v4 Print Driver App that prints Spooler Printer UI Printer Extension Metro Style Device App Configuration Rendering XPS Rendering Filters Configuration (GPD/PPD) AutoConfig (GDL) DevMode Map (XML) Constraints (JavaScript) New Device Connectivity Existing DriverEvents (XML) Bidi Extension (XML) Bidi Extension (JavaScript) Printer Microsoft
Benefits of the v4 architecture • Interfaces use XML at all layers simplifying development • PrintTicket/PrintCapabilities • Bidi • XPS • Printer UI is built using standard, app toolkits minimizing specialized knowledge • Data-driven configuration allows printer sharing without cross-architecture driver management
Simplified driver rendering • Metro style apps generate XPS • Built-in rendering support for PCL6 and PostScript • Improved rendering performance and fidelity with XPS Rasterization Service • GPU Acceleration • High precision color formats
3 simple steps to building a v4 print driver Setup • INF • V4 Manifest.INI Configuration • GPD or PPD file Rendering • Print Filter Pipeline Configuration • XPS Rendering Filter • Print Filter Pipeline Configuration
Visual Studio 11 Developer Preview integration • Tight VS11 integration makes it easy to write v4 drivers • Printer Driver Wizard walks you through the process • Templates help you get started • XPS rendering filters • JavaScript constraints • Bidi extension files
Summary • V4 print drivers provide the best print experience on Windows 8 • V4 print drivers enable enhanced point and print, eliminate cross-architecture management and reduce IT management costs • Developing v4 print drivers is easy with a simplified architecture and Visual Studio support
Related sessions • [Hands on Lab] Developing v4 print drivers • [HW-652T] Building a great Metro style device app for your printer • [PLAT-679T] Building Metro style apps that print • [HW-980P] How to retrieve configuration and status information from USB printers in Windows 8
Further reading and documentation • Developing v4 Print Drivers • MSDN: V4 Print Driver Interfaces and Enumerations • Windows Hardware Development • Authoring a Metro style Device App for Printing • The Device Software Lifecycle – Deployment, Acquisition, Uninstall and Update Process • Windows Dev Center home • Contact info – prninfo@microsoft.com
thank you Feedback and questions http://forums.dev.windows.com Session feedbackhttp://bldw.in/SessionFeedback
© 2011 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.