Freigeben über

XPS & OPC Support in Windows 7

  • Artikel

Last week at PDC and this week at WinHEC we’re talking for the first time about investments we’re making in Windows 7 to better support XPS and OPC.

  • New Win32 APIs for XPS
  • New Win32 APIs for OPC
  • New Win32 API to provide access to the XPS Print Path
  • New XPS Rasterization service for driver developers to use within the XPS Print Path filter pipeline
  • Enhanced user experience with XPS Documents

We’ll be talking more about, and digging into the details of, these new features over the coming weeks and months as we head towards Windows 7 beta. To get a preview you can check out the details from PDC and WinHEC that Adrian posted.

Comments

  • Anonymous
    November 06, 2008
    PingBack from http://www.tmao.info/xps-opc-support-in-windows-7/

  • Anonymous
    November 06, 2008
    Time stamp of digital cert is Oct 20, 2008 but I'm getting an error in the event log.  Product: XPS Essentials Pack -- Error 1722. There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor.  Action SCUpdateInstallAction, location: C:WINDOWSInstallerMSIBC3.tmp, command: /q /z

  • Anonymous
    November 07, 2008
    Jason, To better understand your error, could you please send to xpsinfo@microsoft.com the following information:

  1. Which operating system you were trying to install the XPS Essentials Pack on (including what Service Pack you're running)
  2. What language of the XPS Essentials Pack you were trying to download.
  3. Have you ever had a previous version of the XPS Essentials Pack installed on your machine?  If yes, do you know when one?
  4. If possible, please send us the install log. If running Vista, it's located here:  c:windowswindowsupdate.log If running XP, do the following: a. Opening a command prompt b. run -  <xpsep_setup.exe> /l* <logfile.log> <xpsep_setup.exe> is the setup name that you downloaded from the web site (you will need to change the command prompt directory to point to wherever this file is) <logfile.log> can be any filename that you want to put the log file, ususaly put c:xpsep.log   (ex. C:tempxpsep"XPSEP XP and Server 2003 32 bit.msi" /l*vx xpsep.ui.log) Thanks!

  • Anonymous
    November 10, 2008
    @Jason - great to hear you're up and running

  • Anonymous
    November 24, 2008
    Comme à l'accoutumé, voici une brochette de liens de la semaine sur Open XML. Posts techniques en vrac

  • Anonymous
    December 04, 2008
    How to print a xps file in windows xp/2k3/vista/2k8 through native code, I mean native c++ code? Does the new win32 XPS API in windows 7 work in winxp/2k3/vista/2k8? Will MS distribute a single pack which includes the XPS API?

  • Anonymous
    January 10, 2009
    The comment has been removed

  • Anonymous
    January 10, 2009
    The comment has been removed

  • Anonymous
    February 03, 2009
    @Algis "Unfortunatelly it asks for file name every time and no way to automate conversion of 100000 files." We enable custom development of XPS-based print drivers, including automating the save as process, via the WDK. See details in this post: http://blogs.msdn.com/adrianford/archive/2008/02/02/generating-xps-automagically.aspx

  • Anonymous
    February 03, 2009
    @yuguang The XPS Print API described in this post is only in Windows 7. You can still use the XPS Path Path from Win32 in previous versions of Windows, although it does require more work (code). One option is to use MXDC_ESCAPE [1] to pass XPS page content through to the print path, another is to submit an XPS file directly to the spooler [2]. Note that in both these cases you'll need to verify that the print queue is XPS (see GETTECHNOLOGY [3] for details) which is something that the XPS Print API on Windows 7 handles automatically. [1] http://msdn.microsoft.com/en-us/library/dd162739(VS.85).aspx [2] http://msdn.microsoft.com/en-us/library/dd162861(VS.85).aspx [3] http://msdn.microsoft.com/en-us/library/dd144931(VS.85).aspx

  • Anonymous
    February 15, 2009
    The comment has been removed

  • Anonymous
    February 16, 2009
    It may also be a bug in XPS viewer. Because it shows warning that certificate is expired, but it also shows correctly that the document was signed at the specific date, and at that date the certificate was valid, so must be no warnings. Timestamping is not needed if this is an XPS viewer bug, then I hope this will be corrected in Windows 7.

  • Anonymous
    February 16, 2009
    Hello Algis, Thank you for the great feedback; I'm glad to see you trying to use XPS in this way.  It would be fantastic to learn more about your scenarios and goals with XPS.  Could you share more information with us at xpsinfo@microsoft.com? In regards to timestamp support, this is something we are very much aware of.  Without timestamp server support it's not possible for the XPS Viewer to verify that an expired certificate was valid at the time of signing.  As a result these signatures become questionable, meaning that they are still valid signatures, but it's up to the user to make a trust decision about them.  The legality of signatures with or without timestamp support varies by region. I'm hopeful that we can improve this in the future, but I don't have a specific timeline or release for timestamp support.