<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://powershell.com/cs/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>The Lonely Administrator : Pipeline, Scripting</title><link>http://powershell.com/cs/blogs/lonelyadministrator/archive/tags/Pipeline/Scripting/default.aspx</link><description>Tags: Pipeline, Scripting</description><dc:language>en</dc:language><generator>CommunityServer 2008.5 (Build: 30929.2835)</generator><item><title>Why Doesn’t My Pipeline Work?</title><link>http://powershell.com/cs/blogs/lonelyadministrator/archive/2013/05/07/why-doesn-t-my-pipeline-work.aspx</link><pubDate>Tue, 07 May 2013 13:01:35 GMT</pubDate><guid isPermaLink="false">f421715f-7aba-45f0-8a8d-44de5318a3a7:23309</guid><dc:creator>The Lonely Administrator</dc:creator><slash:comments>0</slash:comments><wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://powershell.com/cs/blogs/lonelyadministrator/rsscomments.aspx?PostID=23309</wfw:commentRss><comments>http://powershell.com/cs/blogs/lonelyadministrator/archive/2013/05/07/why-doesn-t-my-pipeline-work.aspx#comments</comments><description>I saw a little discussion thread on Twitter this morning which I felt needed a little more room to explain. Plus since we&amp;#8217;re in ScriptingGames season beginners might like a few pointers. I always talk about PowerShell, objects and the pipeline....(&lt;a href="http://powershell.com/cs/blogs/lonelyadministrator/archive/2013/05/07/why-doesn-t-my-pipeline-work.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://powershell.com/cs/aggbug.aspx?PostID=23309" width="1" height="1"&gt;</description><category domain="http://powershell.com/cs/blogs/lonelyadministrator/archive/tags/Scripting/default.aspx">Scripting</category><category domain="http://powershell.com/cs/blogs/lonelyadministrator/archive/tags/PowerShell/default.aspx">PowerShell</category><category domain="http://powershell.com/cs/blogs/lonelyadministrator/archive/tags/Best+Practices/default.aspx">Best Practices</category><category domain="http://powershell.com/cs/blogs/lonelyadministrator/archive/tags/Pipeline/default.aspx">Pipeline</category><category domain="http://powershell.com/cs/blogs/lonelyadministrator/archive/tags/ForEach/default.aspx">ForEach</category></item><item><title>Rename Hashtable Key Revised</title><link>http://powershell.com/cs/blogs/lonelyadministrator/archive/2013/01/24/rename-hashtable-key-revised.aspx</link><pubDate>Thu, 24 Jan 2013 14:54:16 GMT</pubDate><guid isPermaLink="false">f421715f-7aba-45f0-8a8d-44de5318a3a7:21231</guid><dc:creator>The Lonely Administrator</dc:creator><slash:comments>0</slash:comments><wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://powershell.com/cs/blogs/lonelyadministrator/rsscomments.aspx?PostID=21231</wfw:commentRss><comments>http://powershell.com/cs/blogs/lonelyadministrator/archive/2013/01/24/rename-hashtable-key-revised.aspx#comments</comments><description>Last week I posted an advanced PowerShell function to rename a hashtable key. As usual, the more I worked with it the more I realized it was missing something &amp;#8211; namely the ability the take a pipelined object. My original version assumed you had...(&lt;a href="http://powershell.com/cs/blogs/lonelyadministrator/archive/2013/01/24/rename-hashtable-key-revised.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://powershell.com/cs/aggbug.aspx?PostID=21231" width="1" height="1"&gt;</description><category domain="http://powershell.com/cs/blogs/lonelyadministrator/archive/tags/Scripting/default.aspx">Scripting</category><category domain="http://powershell.com/cs/blogs/lonelyadministrator/archive/tags/PowerShell/default.aspx">PowerShell</category><category domain="http://powershell.com/cs/blogs/lonelyadministrator/archive/tags/Pipeline/default.aspx">Pipeline</category><category domain="http://powershell.com/cs/blogs/lonelyadministrator/archive/tags/parameter/default.aspx">parameter</category><category domain="http://powershell.com/cs/blogs/lonelyadministrator/archive/tags/hashtable/default.aspx">hashtable</category></item><item><title>Pipeline Power</title><link>http://powershell.com/cs/blogs/lonelyadministrator/archive/2012/04/04/pipeline-power.aspx</link><pubDate>Wed, 04 Apr 2012 18:57:24 GMT</pubDate><guid isPermaLink="false">f421715f-7aba-45f0-8a8d-44de5318a3a7:15800</guid><dc:creator>The Lonely Administrator</dc:creator><slash:comments>0</slash:comments><wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://powershell.com/cs/blogs/lonelyadministrator/rsscomments.aspx?PostID=15800</wfw:commentRss><comments>http://powershell.com/cs/blogs/lonelyadministrator/archive/2012/04/04/pipeline-power.aspx#comments</comments><description>Last week I came across a blog post that had a decent example using PowerShell and PowerCLI to get the disk location for all virtual machines. The posted code works and does display the information you might be after. $myVMs &amp;#8230; Continue reading &amp;#8594;...(&lt;a href="http://powershell.com/cs/blogs/lonelyadministrator/archive/2012/04/04/pipeline-power.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://powershell.com/cs/aggbug.aspx?PostID=15800" width="1" height="1"&gt;</description><category domain="http://powershell.com/cs/blogs/lonelyadministrator/archive/tags/Scripting/default.aspx">Scripting</category><category domain="http://powershell.com/cs/blogs/lonelyadministrator/archive/tags/PowerShell/default.aspx">PowerShell</category><category domain="http://powershell.com/cs/blogs/lonelyadministrator/archive/tags/PowerCLI/default.aspx">PowerCLI</category><category domain="http://powershell.com/cs/blogs/lonelyadministrator/archive/tags/Pipeline/default.aspx">Pipeline</category><category domain="http://powershell.com/cs/blogs/lonelyadministrator/archive/tags/objects/default.aspx">objects</category><category domain="http://powershell.com/cs/blogs/lonelyadministrator/archive/tags/ForEach/default.aspx">ForEach</category><category domain="http://powershell.com/cs/blogs/lonelyadministrator/archive/tags/VMware/default.aspx">VMware</category><category domain="http://powershell.com/cs/blogs/lonelyadministrator/archive/tags/PowerCIi/default.aspx">PowerCIi</category></item><item><title>Have Your Output and Variable Too</title><link>http://powershell.com/cs/blogs/lonelyadministrator/archive/2012/03/29/have-your-output-and-variable-too.aspx</link><pubDate>Thu, 29 Mar 2012 14:52:00 GMT</pubDate><guid isPermaLink="false">f421715f-7aba-45f0-8a8d-44de5318a3a7:15677</guid><dc:creator>The Lonely Administrator</dc:creator><slash:comments>0</slash:comments><wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://powershell.com/cs/blogs/lonelyadministrator/rsscomments.aspx?PostID=15677</wfw:commentRss><comments>http://powershell.com/cs/blogs/lonelyadministrator/archive/2012/03/29/have-your-output-and-variable-too.aspx#comments</comments><description>There&amp;#8217;s a relatively useful suggestion floating around on Twitter on how to save results of PowerShell command to a variable and see the results at the same time. PS C:\&amp;#62; ($data=get-process) I&amp;#8217;ll admit this is a clever technique: you get...(&lt;a href="http://powershell.com/cs/blogs/lonelyadministrator/archive/2012/03/29/have-your-output-and-variable-too.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://powershell.com/cs/aggbug.aspx?PostID=15677" width="1" height="1"&gt;</description><category domain="http://powershell.com/cs/blogs/lonelyadministrator/archive/tags/Scripting/default.aspx">Scripting</category><category domain="http://powershell.com/cs/blogs/lonelyadministrator/archive/tags/PowerShell/default.aspx">PowerShell</category><category domain="http://powershell.com/cs/blogs/lonelyadministrator/archive/tags/Pipeline/default.aspx">Pipeline</category><category domain="http://powershell.com/cs/blogs/lonelyadministrator/archive/tags/Tee-Object/default.aspx">Tee-Object</category></item><item><title>Friday Fun – Get Ranked Object</title><link>http://powershell.com/cs/blogs/lonelyadministrator/archive/2011/12/23/friday-fun-get-ranked-object.aspx</link><pubDate>Fri, 23 Dec 2011 17:25:22 GMT</pubDate><guid isPermaLink="false">f421715f-7aba-45f0-8a8d-44de5318a3a7:13732</guid><dc:creator>The Lonely Administrator</dc:creator><slash:comments>0</slash:comments><wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://powershell.com/cs/blogs/lonelyadministrator/rsscomments.aspx?PostID=13732</wfw:commentRss><comments>http://powershell.com/cs/blogs/lonelyadministrator/archive/2011/12/23/friday-fun-get-ranked-object.aspx#comments</comments><description>Earlier this week on Google Plus, Hal Rottenberg posted a PowerShell idea he had. His goal was to identify a group of objects that would be statistically significant. For example, given a collection of files, group the files by size &amp;#8230; Continue reading...(&lt;a href="http://powershell.com/cs/blogs/lonelyadministrator/archive/2011/12/23/friday-fun-get-ranked-object.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://powershell.com/cs/aggbug.aspx?PostID=13732" width="1" height="1"&gt;</description><category domain="http://powershell.com/cs/blogs/lonelyadministrator/archive/tags/functions/default.aspx">functions</category><category domain="http://powershell.com/cs/blogs/lonelyadministrator/archive/tags/Scripting/default.aspx">Scripting</category><category domain="http://powershell.com/cs/blogs/lonelyadministrator/archive/tags/PowerShell/default.aspx">PowerShell</category><category domain="http://powershell.com/cs/blogs/lonelyadministrator/archive/tags/Pipeline/default.aspx">Pipeline</category><category domain="http://powershell.com/cs/blogs/lonelyadministrator/archive/tags/objects/default.aspx">objects</category><category domain="http://powershell.com/cs/blogs/lonelyadministrator/archive/tags/math/default.aspx">math</category></item><item><title>Finding Files in the Path – A Pipeline Perk</title><link>http://powershell.com/cs/blogs/lonelyadministrator/archive/2011/11/17/finding-files-in-the-path-a-pipeline-perk.aspx</link><pubDate>Thu, 17 Nov 2011 15:11:36 GMT</pubDate><guid isPermaLink="false">f421715f-7aba-45f0-8a8d-44de5318a3a7:13276</guid><dc:creator>The Lonely Administrator</dc:creator><slash:comments>0</slash:comments><wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://powershell.com/cs/blogs/lonelyadministrator/rsscomments.aspx?PostID=13276</wfw:commentRss><comments>http://powershell.com/cs/blogs/lonelyadministrator/archive/2011/11/17/finding-files-in-the-path-a-pipeline-perk.aspx#comments</comments><description>I&amp;#8217;ve been chipping in on a forum post about finding if a given file exists in any folder within the system environmental %PATH% variable using Windows PowerShell. There are several ways you might approach this. But the best way in &amp;#8230;... [[...(&lt;a href="http://powershell.com/cs/blogs/lonelyadministrator/archive/2011/11/17/finding-files-in-the-path-a-pipeline-perk.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://powershell.com/cs/aggbug.aspx?PostID=13276" width="1" height="1"&gt;</description><category domain="http://powershell.com/cs/blogs/lonelyadministrator/archive/tags/Scripting/default.aspx">Scripting</category><category domain="http://powershell.com/cs/blogs/lonelyadministrator/archive/tags/PowerShell/default.aspx">PowerShell</category><category domain="http://powershell.com/cs/blogs/lonelyadministrator/archive/tags/Pipeline/default.aspx">Pipeline</category><category domain="http://powershell.com/cs/blogs/lonelyadministrator/archive/tags/filtering/default.aspx">filtering</category><category domain="http://powershell.com/cs/blogs/lonelyadministrator/archive/tags/Test-Path/default.aspx">Test-Path</category><category domain="http://powershell.com/cs/blogs/lonelyadministrator/archive/tags/Join-Path/default.aspx">Join-Path</category></item></channel></rss>