Automating the world one-liner at a time…
I originally published Ben Pearce's PowerShell Cheat sheet in Word 2007 format.
Given that I posted it a week before the Office 2007 launch, it turned out that not many people could read that so I posted it in PDF format as well.
It now turns out that the corporate direction is to use XPS (I'm told that XPS viewers are readily available).
Attached is an XPS version.
I'm hoping that I can stop there and avoid publishing it in TROFF, TEX, SMGL, DECWriter, or any other formats. J
Jeffrey Snover [MSFT]Windows PowerShell/MMC ArchitectVisit the Windows PowerShell Team blog at: http://blogs.msdn.com/PowerShellVisit the Windows PowerShell ScriptCenter at: http://www.microsoft.com/technet/scriptcenter/hubs/msh.mspx
You should sign your XPS docs so they can be more easily saved.
PingBack from http://blog.stevex.net/index.php/2007/01/31/microsoft-pushing-xps/
>You should sign your XPS docs so they can be more easily saved.
Or just leave it at PDF.
Everyone can read PDF. Why does Microsoft have to reinvent the wheel all the time?
> It now turns out that the corporate direction is to
> use XPS (I'm told that XPS viewers are readily available).
I can see the viewers listed here:
I'm a Windows admin but I read my RSS feeds on a Mac ('cause it was RSS-friendly long before Windows and old habits are hard to break). Since my installed version Office for the Mac (2004) doesn't support XPS either, your blog/RSS attachment causes me to go through a number of hoops to get it over to my Windows workstation (running Office 2007 by the way).
Should have stuck with the PDF.
> It now turns out that the corporate direction
> is to use XPS
Yes, well, the corporate direction in this case is stupid. XPS has zero advantage over PDF for this purpose, and reduces interoperability significantly.
What is wrong with a web page? Why the need to publish in proprietary formats? Everyone regarding of OS can likely access it. Interesting how backwards and forwards compatible the web is ;)
Thanks. Been wanting that.
Thanks for posting it in alternative formats.
I've got a question, is there anyway to output directly to XPS in powershell? I've been piping output to Out-Printer -Name "Microsoft XPS Document Writer" for now, but it seems like an odd way to do it.
site http://larondawenner.indiegroup.com/ home domain website