<?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 12 of 31: PowerShell and The Registry</title><link>http://blogs.technet.com/b/matthewms/archive/2011/05/12/powershell-not-your-father-s-command-line-part-12-of-31-powershell-and-the-registry.aspx</link><description>In yesterday’s post we took a look a quick look at providers .&amp;#160; In this post we are going to take a look at the registry.&amp;#160; Before I begin with this post I do have to give you the standard warning.&amp;#160; Working with and modifying the registry</description><dc:language>en-US</dc:language><generator>Telligent Evolution Platform Developer Build (Build: 5.6.50428.7875)</generator></channel></rss>