<?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 : PowerShell, Variable</title><link>http://powershell.com/cs/blogs/lonelyadministrator/archive/tags/PowerShell/Variable/default.aspx</link><description>Tags: PowerShell, Variable</description><dc:language>en</dc:language><generator>CommunityServer 2008.5 (Build: 30929.2835)</generator><item><title>Get My Variable Revisited</title><link>http://powershell.com/cs/blogs/lonelyadministrator/archive/2012/05/29/get-my-variable-revisited.aspx</link><pubDate>Tue, 29 May 2012 13:16:27 GMT</pubDate><guid isPermaLink="false">f421715f-7aba-45f0-8a8d-44de5318a3a7:16760</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=16760</wfw:commentRss><comments>http://powershell.com/cs/blogs/lonelyadministrator/archive/2012/05/29/get-my-variable-revisited.aspx#comments</comments><description>Last year I wrote a few articles on working with variables. One task I needed was to identify the variables that I had created in a given PowerShell session with a function I wrote called Get-MyVariable. I also posted an &amp;#8230; Continue reading &amp;#8594;...(&lt;a href="http://powershell.com/cs/blogs/lonelyadministrator/archive/2012/05/29/get-my-variable-revisited.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://powershell.com/cs/aggbug.aspx?PostID=16760" 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/Variable/default.aspx">Variable</category></item><item><title>Friday Fun What’s My Variable</title><link>http://powershell.com/cs/blogs/lonelyadministrator/archive/2012/01/06/friday-fun-what-s-my-variable.aspx</link><pubDate>Fri, 06 Jan 2012 16:32:25 GMT</pubDate><guid isPermaLink="false">f421715f-7aba-45f0-8a8d-44de5318a3a7:13907</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=13907</wfw:commentRss><comments>http://powershell.com/cs/blogs/lonelyadministrator/archive/2012/01/06/friday-fun-what-s-my-variable.aspx#comments</comments><description>I use scriptblocks quite a bit in my PowerShell work, often saved as variables. These are handy for commands you want to run again, but don&amp;#8217;t necessarily need to turn into permanent functions. $freec=&amp;#123;&amp;#40;get-wmiobject win32_logicaldisk -filter...(&lt;a href="http://powershell.com/cs/blogs/lonelyadministrator/archive/2012/01/06/friday-fun-what-s-my-variable.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://powershell.com/cs/aggbug.aspx?PostID=13907" width="1" height="1"&gt;</description><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/Friday+Fun/default.aspx">Friday Fun</category><category domain="http://powershell.com/cs/blogs/lonelyadministrator/archive/tags/FridayFun/default.aspx">FridayFun</category><category domain="http://powershell.com/cs/blogs/lonelyadministrator/archive/tags/Variable/default.aspx">Variable</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/Type/default.aspx">Type</category><category domain="http://powershell.com/cs/blogs/lonelyadministrator/archive/tags/Get-variable/default.aspx">Get-variable</category></item><item><title>Create a Read-Only PowerShell Session</title><link>http://powershell.com/cs/blogs/lonelyadministrator/archive/2011/09/01/create-a-read-only-powershell-session.aspx</link><pubDate>Thu, 01 Sep 2011 14:10:29 GMT</pubDate><guid isPermaLink="false">f421715f-7aba-45f0-8a8d-44de5318a3a7:12095</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=12095</wfw:commentRss><comments>http://powershell.com/cs/blogs/lonelyadministrator/archive/2011/09/01/create-a-read-only-powershell-session.aspx#comments</comments><description>In my PowerShell training class this week, I was demonstrating how to take advantage of the -Whatif and -Confirm parameters. These parameters exist (or should) for any cmdlet that changes the environment such as stopping a service, killing a process &amp;#8230;...(&lt;a href="http://powershell.com/cs/blogs/lonelyadministrator/archive/2011/09/01/create-a-read-only-powershell-session.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://powershell.com/cs/aggbug.aspx?PostID=12095" width="1" height="1"&gt;</description><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/PowerShell+v2.0/default.aspx">PowerShell v2.0</category><category domain="http://powershell.com/cs/blogs/lonelyadministrator/archive/tags/Variable/default.aspx">Variable</category></item><item><title>Warning Signs</title><link>http://powershell.com/cs/blogs/lonelyadministrator/archive/2011/05/11/warning-signs.aspx</link><pubDate>Wed, 11 May 2011 12:14:36 GMT</pubDate><guid isPermaLink="false">f421715f-7aba-45f0-8a8d-44de5318a3a7:10356</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=10356</wfw:commentRss><comments>http://powershell.com/cs/blogs/lonelyadministrator/archive/2011/05/11/warning-signs.aspx#comments</comments><description>I was working on a project with an advanced PowerShell function. One of the goals was to take advantage of the common parameters like -ErrorVariable and -WarningVariable so that when you run the function you can save errors and warnings &amp;#8230; Continue...(&lt;a href="http://powershell.com/cs/blogs/lonelyadministrator/archive/2011/05/11/warning-signs.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://powershell.com/cs/aggbug.aspx?PostID=10356" 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/Function/default.aspx">Function</category><category domain="http://powershell.com/cs/blogs/lonelyadministrator/archive/tags/PowerShell+v2.0/default.aspx">PowerShell v2.0</category><category domain="http://powershell.com/cs/blogs/lonelyadministrator/archive/tags/Write-Warning/default.aspx">Write-Warning</category><category domain="http://powershell.com/cs/blogs/lonelyadministrator/archive/tags/Variable/default.aspx">Variable</category></item></channel></rss>