<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.technet.com/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>PowerShell Not your Father’s Command Line Part 9 of 31: Another Side of PowerShell Profiles</title><link>http://blogs.technet.com/b/matthewms/archive/2011/05/09/powershell-not-your-father-s-command-line-part-9-of-31-another-side-of-powershell-profiles.aspx</link><description>In some previous posts we talked about how to add functionality through importing modules , or adding aliases and functions &amp;#160; This allowed you to temporarily configure your PowerShell session to work the way you needed for that session. However,</description><dc:language>en-US</dc:language><generator>Telligent Evolution Platform Developer Build (Build: 5.6.50428.7875)</generator></channel></rss>