<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/rss2full.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.feedburner.com/~d/styles/itemcontent.css"?><rss xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/" xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" version="2.0">
  <channel>
    <title>Most recent blog entries</title>
    <description>Read tips, tricks, advice, samples, and examples from the Windows PowerShell community - or start your own blog and share what you're learning!</description>
    <link>http://www.powershellcommunity.org/Blogs/CommunityBlogs.aspx</link>
    <language>en-US</language>
    <managingEditor>do-not-reply@powershellcommunity.org</managingEditor>
    <webMaster>do-not-reply@powershellcommunity.org</webMaster>
    <pubDate>Sun, 15 Nov 2009 04:01:31 GMT</pubDate>
    <lastBuildDate>Sun, 15 Nov 2009 04:01:31 GMT</lastBuildDate>
    <docs>http://backend.userland.com/rss</docs>
    <generator>Blog RSS Generator Version 3.4.0.39853</generator>
    <atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" href="http://feeds.feedburner.com/powershellcommunity" type="application/rss+xml" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com" /><item>
      <title>ShellTool’s Portable PowerShell – Description, Survey and Private Beta</title>
      <description>&lt;p&gt;&amp;#160;&lt;/p&gt;
&lt;div style="margin: 0in 0in 10pt"&gt;&lt;u&gt;What is it?&lt;/u&gt;&lt;/div&gt;
&lt;div style="margin: 0in 0in 10pt"&gt;Portable PowerShell is software that allows you to run PowerShell on machines that don’t have PowerShell installed that you can run from a Machine that doesn’t have PowerShell on it, from a USB stick, on a machine that has a different version of PowerShell, a preinstall environment like BartPE, or WinPE or when booted to a windows 7 recovery DVD....&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/powershellcommunity/~4/xcLFKB8G1zg" height="1" width="1"/&gt;</description>
      <link>http://feedproxy.google.com/~r/powershellcommunity/~3/xcLFKB8G1zg/Default.aspx</link>
      <comments>http://www.powershellcommunity.org/Blogs/CommunityBlogs/tabid/55/EntryID/97/Default.aspx#Comments</comments>
      <guid isPermaLink="false">http://www.powershellcommunity.org/Default.aspx?tabid=55&amp;EntryID=97</guid>
      <pubDate>Tue, 21 Jul 2009 05:28:00 GMT</pubDate>
      <slash:comments>0</slash:comments>
      <trackback:ping>http://www.powershellcommunity.org/DesktopModules/Blog/Trackback.aspx?id=97</trackback:ping>
    <feedburner:origLink>http://www.powershellcommunity.org/Default.aspx?tabid=55&amp;EntryID=97</feedburner:origLink></item>
    <item>
      <title>PowerShell Analyzer Refresh for PSV2 + CTP3 advanced function features.</title>
      <description>&lt;p&gt;Though we don’t have intentions to carry developing PowerShell Analyzer much in the future, there are a number of improvements in my personal fork, and we want to make sure that it keeps its shelf life by updating it for PowerShell V2. Surprisingly we are still getting hundreds of downloads a day so we want to make sure that those who prefer PSA can still keep using it and also take advantage of the features I use day in and day out. We’ll probably release some new builds within the next couple of weeks, but will post some screenshots and maybe videos until then. We hope that will minimal effort keep PSA the best free PowerShell tool. Read more below to see the screenshots and examples&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/powershellcommunity/~4/cJKdVGZmP9w" height="1" width="1"/&gt;</description>
      <link>http://feedproxy.google.com/~r/powershellcommunity/~3/cJKdVGZmP9w/Default.aspx</link>
      <comments>http://www.powershellcommunity.org/Blogs/CommunityBlogs/tabid/55/EntryID/96/Default.aspx#Comments</comments>
      <guid isPermaLink="false">http://www.powershellcommunity.org/Default.aspx?tabid=55&amp;EntryID=96</guid>
      <pubDate>Thu, 08 Jan 2009 08:53:00 GMT</pubDate>
      <slash:comments>0</slash:comments>
      <trackback:ping>http://www.powershellcommunity.org/DesktopModules/Blog/Trackback.aspx?id=96</trackback:ping>
    <feedburner:origLink>http://www.powershellcommunity.org/Default.aspx?tabid=55&amp;EntryID=96</feedburner:origLink></item>
    <item>
      <title>PowerShell Analyzer like execution hotkeys for PS CTP3 ISE.</title>
      <description>&lt;p&gt;PowerShell CTP3 ISE - Integrated Scripting environment has inherited many ideas and features from PowerShell analyzer including multiple runspaces,editors, a smaller immediate input area and output pane, however it doesn’t have the output visualizers of PSA nor the super fast RTS like execution control of PSA.&lt;/p&gt;
&lt;p&gt;However Microsoft in their wisdom has made ISE rather extensible through the $PSISE variable, and many people already have added some very cool functionality to ISE through these.&lt;/p&gt;
&lt;p&gt;When I first demo’d what was then MSH analyzer to Microsoft back in the first few months of 2006, the feature that seemed to stand out the most to the team was the ability to select an area of code and just run that. Thankfully that level of execution control is now in ISE as F6, but I wanted more, so i’m going to share with you a script that build a few months ago to add a couple of features.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;&lt;u&gt;F7 run the current physical line.&lt;/u&gt;&lt;img src="http://feeds.feedburner.com/~r/powershellcommunity/~4/psBHeD2So0c" height="1" width="1"/&gt;</description>
      <link>http://feedproxy.google.com/~r/powershellcommunity/~3/psBHeD2So0c/Default.aspx</link>
      <comments>http://www.powershellcommunity.org/Blogs/CommunityBlogs/tabid/55/EntryID/95/Default.aspx#Comments</comments>
      <guid isPermaLink="false">http://www.powershellcommunity.org/Default.aspx?tabid=55&amp;EntryID=95</guid>
      <pubDate>Sun, 04 Jan 2009 03:14:00 GMT</pubDate>
      <slash:comments>0</slash:comments>
      <trackback:ping>http://www.powershellcommunity.org/DesktopModules/Blog/Trackback.aspx?id=95</trackback:ping>
    <feedburner:origLink>http://www.powershellcommunity.org/Default.aspx?tabid=55&amp;EntryID=95</feedburner:origLink></item>
    <item>
      <title>Help us decide which PowerShell tool to release next.</title>
      <description>&lt;p&gt;SURVEY: &lt;a href="http://spreadsheets.google.com/viewform?key=pgTpVBomNgDwUA9uQNRKAbw&amp;amp;hl=en"&gt;http://spreadsheets.google.com/viewform?key=pgTpVBomNgDwUA9uQNRKAbw&amp;amp;hl=en&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Taking an app from an internal application to a shrink-wrap ready for &lt;br /&gt;
the masses state is a lot of work, and updating/supporting/marketting &lt;br /&gt;
a product even more so. So after the huge sucess of PowerShell Plus &lt;br /&gt;
which is now safe in Idera's hands we need your help to decide what we &lt;br /&gt;
are going to release next. We plan to release some free projects, even &lt;br /&gt;
some opensource apps, but will likely look at productizing a project &lt;br /&gt;
so we can continue to feed our families. Please take the time to take &lt;br /&gt;
our survey &lt;br /&gt;
&amp;#160;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/powershellcommunity/~4/KAMofhAlWmY" height="1" width="1"/&gt;</description>
      <link>http://feedproxy.google.com/~r/powershellcommunity/~3/KAMofhAlWmY/Default.aspx</link>
      <comments>http://www.powershellcommunity.org/Blogs/CommunityBlogs/tabid/55/EntryID/94/Default.aspx#Comments</comments>
      <guid isPermaLink="false">http://www.powershellcommunity.org/Default.aspx?tabid=55&amp;EntryID=94</guid>
      <pubDate>Sat, 20 Dec 2008 00:58:00 GMT</pubDate>
      <slash:comments>0</slash:comments>
      <trackback:ping>http://www.powershellcommunity.org/DesktopModules/Blog/Trackback.aspx?id=94</trackback:ping>
    <feedburner:origLink>http://www.powershellcommunity.org/Default.aspx?tabid=55&amp;EntryID=94</feedburner:origLink></item>
    <item>
      <title>PowerShell Usability Study</title>
      <description>&lt;p&gt;PowerShell Usability Study, July 22 to July 29, 2008 at Redmond, WA&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/powershellcommunity/~4/ozOjSgdOUXE" height="1" width="1"/&gt;</description>
      <link>http://feedproxy.google.com/~r/powershellcommunity/~3/ozOjSgdOUXE/Default.aspx</link>
      <comments>http://www.powershellcommunity.org/Blogs/CommunityBlogs/tabid/55/EntryID/93/Default.aspx#Comments</comments>
      <guid isPermaLink="false">http://www.powershellcommunity.org/Default.aspx?tabid=55&amp;EntryID=93</guid>
      <pubDate>Fri, 27 Jun 2008 12:52:00 GMT</pubDate>
      <slash:comments>0</slash:comments>
      <trackback:ping>http://www.powershellcommunity.org/DesktopModules/Blog/Trackback.aspx?id=93</trackback:ping>
    <feedburner:origLink>http://www.powershellcommunity.org/Default.aspx?tabid=55&amp;EntryID=93</feedburner:origLink></item>
    <item>
      <title>Portable PowerShell - v1 and v2 side by side - even on Server Core.</title>
      <description>&lt;p&gt;So I've loved portable apps from time memorial and have valued making my own apps as portable as possible - XCOPY friendly.
&lt;div class="wlWriterSmartContent" id="scid:5737277B-5D6D-4f48-ABFC-DD9C333F4C5D:5e95055d-a592-48bb-9238-9d72349b123f" style="padding-right: 0px; display: inline; padding-left: 0px; padding-bottom: 0px; margin: 0px; padding-top: 0px"&gt;&lt;embed src="http://www.vimeo.com/moogaloop.swf?clip_id=1185791&amp;amp;server=www.vimeo.com&amp;amp;show_title=1&amp;amp;show_byline=1&amp;amp;show_portrait=0&amp;amp;color=&amp;amp;fullscreen=1" width="320" height="200" type="application/x-shockwave-flash" allowscriptaccess="always" allowfullscreen="true" mce_src="http://www.vimeo.com/moogaloop.swf?clip_id=1185791&amp;amp;server=www.vimeo.com&amp;amp;show_title=1&amp;amp;show_byline=1&amp;amp;show_portrait=0&amp;amp;color=&amp;amp;fullscreen=1"&gt;&lt;/embed&gt;&lt;br /&gt;
&lt;a href=&amp;quot&lt;img src="http://feeds.feedburner.com/~r/powershellcommunity/~4/rXHIWY5FvAM" height="1" width="1"/&gt;</description>
      <link>http://feedproxy.google.com/~r/powershellcommunity/~3/rXHIWY5FvAM/Default.aspx</link>
      <comments>http://www.powershellcommunity.org/Blogs/CommunityBlogs/tabid/55/EntryID/92/Default.aspx#Comments</comments>
      <guid isPermaLink="false">http://www.powershellcommunity.org/Default.aspx?tabid=55&amp;EntryID=92</guid>
      <pubDate>Wed, 18 Jun 2008 05:15:00 GMT</pubDate>
      <slash:comments>3</slash:comments>
      <trackback:ping>http://www.powershellcommunity.org/DesktopModules/Blog/Trackback.aspx?id=92</trackback:ping>
    <feedburner:origLink>http://www.powershellcommunity.org/Default.aspx?tabid=55&amp;EntryID=92</feedburner:origLink></item>
    <item>
      <title>Fast New PSCustomObject.</title>
      <description>&lt;p&gt;Given the context on the last few posts. I've made a simple helper method in C# that can take a simple powershell hashtable and create a PSCustomObject based on it. Here is an example of how you can call it.&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/powershellcommunity/~4/O4-PwkKAHFI" height="1" width="1"/&gt;</description>
      <link>http://feedproxy.google.com/~r/powershellcommunity/~3/O4-PwkKAHFI/Default.aspx</link>
      <comments>http://www.powershellcommunity.org/Blogs/CommunityBlogs/tabid/55/EntryID/91/Default.aspx#Comments</comments>
      <guid isPermaLink="false">http://www.powershellcommunity.org/Default.aspx?tabid=55&amp;EntryID=91</guid>
      <pubDate>Wed, 18 Jun 2008 05:12:00 GMT</pubDate>
      <slash:comments>0</slash:comments>
      <trackback:ping>http://www.powershellcommunity.org/DesktopModules/Blog/Trackback.aspx?id=91</trackback:ping>
    <feedburner:origLink>http://www.powershellcommunity.org/Default.aspx?tabid=55&amp;EntryID=91</feedburner:origLink></item>
    <item>
      <title>generating a "PropertyBag" aka PScustomObject in C#</title>
      <description>&lt;p&gt;Based on the performance testing and work being done by &lt;a href="http://karlprosser.com/coder/2008/06/12/getting-serious-about-performance-in-powershell/"&gt;&lt;font color="#2153aa"&gt;myself&lt;/font&gt;&lt;/a&gt; , &lt;a href="http://thepowershellguy.com/blogs/posh/archive/2008/06/11/powershell-performance-series-part-1-warming-up.aspx"&gt;&lt;font color="#2153aa"&gt;mow&lt;/font&gt;&lt;/a&gt; , &lt;a href="http://bsonposh.com/"&gt;&lt;font color="#2153aa"&gt;Brandon Shell&lt;/font&gt;&lt;/a&gt; and others the question has come up what is the quickest way to generate a PSCustomObject, whether in script , on in C#, and how do you even do it in C#?&lt;/p&gt;
&lt;p&gt;Some typical ways of doing in PowerShell have been either something like the following trick:&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/powershellcommunity/~4/gq9w5-3OqhY" height="1" width="1"/&gt;</description>
      <link>http://feedproxy.google.com/~r/powershellcommunity/~3/gq9w5-3OqhY/Default.aspx</link>
      <comments>http://www.powershellcommunity.org/Blogs/CommunityBlogs/tabid/55/EntryID/90/Default.aspx#Comments</comments>
      <guid isPermaLink="false">http://www.powershellcommunity.org/Default.aspx?tabid=55&amp;EntryID=90</guid>
      <pubDate>Wed, 18 Jun 2008 05:08:00 GMT</pubDate>
      <slash:comments>0</slash:comments>
      <trackback:ping>http://www.powershellcommunity.org/DesktopModules/Blog/Trackback.aspx?id=90</trackback:ping>
    <feedburner:origLink>http://www.powershellcommunity.org/Default.aspx?tabid=55&amp;EntryID=90</feedburner:origLink></item>
    <item>
      <title>Getting serious about performance in PowerShell.</title>
      <description>&lt;p&gt;I've spend a lot of time in the past looking at the performance of PowerShell but have never gotten around to blogging about it. However it has become quite a hot button among MVPs and others in recent days and we've been busy testing and comparing the speeds different techniques in PowerShell in both V1 and V2.&lt;/p&gt;
&lt;p&gt;In V1 there seems to be extreme slowdowns when invoking cmdlet, functions, any type of scriptblock and when using the pipeline. If you...&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/powershellcommunity/~4/TUUXZ-EJS_g" height="1" width="1"/&gt;</description>
      <link>http://feedproxy.google.com/~r/powershellcommunity/~3/TUUXZ-EJS_g/Default.aspx</link>
      <comments>http://www.powershellcommunity.org/Blogs/CommunityBlogs/tabid/55/EntryID/89/Default.aspx#Comments</comments>
      <guid isPermaLink="false">http://www.powershellcommunity.org/Default.aspx?tabid=55&amp;EntryID=89</guid>
      <pubDate>Thu, 12 Jun 2008 05:23:00 GMT</pubDate>
      <slash:comments>0</slash:comments>
      <trackback:ping>http://www.powershellcommunity.org/DesktopModules/Blog/Trackback.aspx?id=89</trackback:ping>
    <feedburner:origLink>http://www.powershellcommunity.org/Default.aspx?tabid=55&amp;EntryID=89</feedburner:origLink></item>
    <item>
      <title>SnapInini - Lite portable SnapIns with no need of registration/installation.</title>
      <description>&lt;p&gt;One thing that has bothered me about true cmdlets in contrast scripts is that they lived in SnapIns and couldn't be deployed with xcopy as scripts can because SnapIns required Registration/Installation. I build my own way to deal with this need some time ago, and thought that I'd start a blog series covering it. I call them Snapininis or SnapIn-Lites. A good thing is you can achieve the same end result in PowerShell V2 with modules - but that is V2 and a while away from being released, and then even further away from being fully deployed.&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/powershellcommunity/~4/q0NycbdiD-M" height="1" width="1"/&gt;</description>
      <link>http://feedproxy.google.com/~r/powershellcommunity/~3/q0NycbdiD-M/Default.aspx</link>
      <comments>http://www.powershellcommunity.org/Blogs/CommunityBlogs/tabid/55/EntryID/88/Default.aspx#Comments</comments>
      <guid isPermaLink="false">http://www.powershellcommunity.org/Default.aspx?tabid=55&amp;EntryID=88</guid>
      <pubDate>Sat, 07 Jun 2008 08:32:00 GMT</pubDate>
      <slash:comments>0</slash:comments>
      <trackback:ping>http://www.powershellcommunity.org/DesktopModules/Blog/Trackback.aspx?id=88</trackback:ping>
    <feedburner:origLink>http://www.powershellcommunity.org/Default.aspx?tabid=55&amp;EntryID=88</feedburner:origLink></item>
    <item>
      <title>Determining what version of PowerShell your script is running in.</title>
      <description>&lt;p&gt;Many people recently have asked how to determine programatically what version of PowerShell their script is running in. Well in version two there is a $psversiontable variable, but this sadly isn't in V1. All is not lost though, as you can write a simple function to return a version object for v1. Below is a quick function that I wrote that I have been using for the last year or so.&amp;#160;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/powershellcommunity/~4/8hXoF-oDoag" height="1" width="1"/&gt;</description>
      <link>http://feedproxy.google.com/~r/powershellcommunity/~3/8hXoF-oDoag/Default.aspx</link>
      <comments>http://www.powershellcommunity.org/Blogs/CommunityBlogs/tabid/55/EntryID/87/Default.aspx#Comments</comments>
      <guid isPermaLink="false">http://www.powershellcommunity.org/Default.aspx?tabid=55&amp;EntryID=87</guid>
      <pubDate>Wed, 04 Jun 2008 06:40:00 GMT</pubDate>
      <slash:comments>0</slash:comments>
      <trackback:ping>http://www.powershellcommunity.org/DesktopModules/Blog/Trackback.aspx?id=87</trackback:ping>
    <feedburner:origLink>http://www.powershellcommunity.org/Default.aspx?tabid=55&amp;EntryID=87</feedburner:origLink></item>
    <item>
      <title>Win a Kindle</title>
      <description>&lt;p&gt;Here's my hands-on review of the Amazon Kindle, along with a chance for you to win your own!&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/powershellcommunity/~4/Mcgw9awbbxQ" height="1" width="1"/&gt;</description>
      <link>http://feedproxy.google.com/~r/powershellcommunity/~3/Mcgw9awbbxQ/Default.aspx</link>
      <author>don@sapien.com</author>
      <guid isPermaLink="false">http://www.powershellcommunity.org/Default.aspx?tabid=55&amp;EntryID=86</guid>
      <pubDate>Mon, 02 Jun 2008 16:01:00 GMT</pubDate>
      <trackback:ping>http://www.powershellcommunity.org/DesktopModules/Blog/Trackback.aspx?id=86</trackback:ping>
    <feedburner:origLink>http://www.powershellcommunity.org/Default.aspx?tabid=55&amp;EntryID=86</feedburner:origLink></item>
    <item>
      <title>-STA and WPF scripting</title>
      <description>&lt;p&gt;In this blog, I cover features in &lt;a href="http://www.powershell.com/download/psp1.zip"&gt;PowerShell Plus&lt;/a&gt;. &lt;strong&gt;Feature #7:&lt;/strong&gt; Support for -STA and Windows Presentation Foundation&lt;/p&gt;
&lt;p&gt;Check out the latest PS Team blog series covering WPF scripting in PS V2: &lt;a href="http://blogs.msdn.com/powershell/archive/2008/05/22/wpf-powershell-part-1-hello-world-welcome-to-the-week-of-wpf.aspx"&gt;http://blogs.msdn.com/powershell/archive/2008/05/22/wpf-powershell-part-1-hello-world-welcome-to-the-week-of-wpf.aspx&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;A lot of people are using PS V2 already, and so far PowerShell Plus has worked great with V1 and V2. And now it even supports "STA" single threaded appartment model! So you can use PS+ to write and debug WPF scripts, too!&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/powershellcommunity/~4/4GSwSgLdnWk" height="1" width="1"/&gt;</description>
      <link>http://feedproxy.google.com/~r/powershellcommunity/~3/4GSwSgLdnWk/Default.aspx</link>
      <author>tobias.weltner@scriptinternals.de</author>
      <comments>http://www.powershellcommunity.org/Blogs/CommunityBlogs/tabid/55/EntryID/85/Default.aspx#Comments</comments>
      <guid isPermaLink="false">http://www.powershellcommunity.org/Default.aspx?tabid=55&amp;EntryID=85</guid>
      <pubDate>Fri, 23 May 2008 19:46:00 GMT</pubDate>
      <slash:comments>1</slash:comments>
      <trackback:ping>http://www.powershellcommunity.org/DesktopModules/Blog/Trackback.aspx?id=85</trackback:ping>
    <feedburner:origLink>http://www.powershellcommunity.org/Default.aspx?tabid=55&amp;EntryID=85</feedburner:origLink></item>
    <item>
      <title>Fun WMI Trick Proves You Should Read the Help</title>
      <description>&lt;p&gt;Did you ever read the help for Windows PowerShell’s Get-WmiObject cmdlet? I mean really read the help?&lt;br /&gt;
You’ve probably noticed the -computerName parameter, but pay close attention to how it’s listed in the help:&lt;br /&gt;
[-computerName string[]]&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/powershellcommunity/~4/DOcc8Gl-kqY" height="1" width="1"/&gt;</description>
      <link>http://feedproxy.google.com/~r/powershellcommunity/~3/DOcc8Gl-kqY/Default.aspx</link>
      <author>don@sapien.com</author>
      <comments>http://www.powershellcommunity.org/Blogs/CommunityBlogs/tabid/55/EntryID/84/Default.aspx#Comments</comments>
      <guid isPermaLink="false">http://www.powershellcommunity.org/Default.aspx?tabid=55&amp;EntryID=84</guid>
      <pubDate>Fri, 23 May 2008 18:33:00 GMT</pubDate>
      <slash:comments>0</slash:comments>
      <trackback:ping>http://www.powershellcommunity.org/DesktopModules/Blog/Trackback.aspx?id=84</trackback:ping>
    <feedburner:origLink>http://www.powershellcommunity.org/Default.aspx?tabid=55&amp;EntryID=84</feedburner:origLink></item>
    <item>
      <title>External blog...</title>
      <description>&lt;p&gt;I'm moving some of my blogging activities to &lt;a href="http://www.concentratedtech.com"&gt;http://www.concentratedtech.com&lt;/a&gt;; you'll notice me blogging less on &lt;a href="http://blog.sapien.com"&gt;http://blog.sapien.com&lt;/a&gt; going forward. I'll also be cross-posting some of my PowerShell-related blog entries right here. You should also notice a much higher volume of blogging out of me in the near future :) so stay tuned.&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/powershellcommunity/~4/gqInni2VXxs" height="1" width="1"/&gt;</description>
      <link>http://feedproxy.google.com/~r/powershellcommunity/~3/gqInni2VXxs/Default.aspx</link>
      <author>don@sapien.com</author>
      <comments>http://www.powershellcommunity.org/Blogs/CommunityBlogs/tabid/55/EntryID/83/Default.aspx#Comments</comments>
      <guid isPermaLink="false">http://www.powershellcommunity.org/Default.aspx?tabid=55&amp;EntryID=83</guid>
      <pubDate>Fri, 23 May 2008 15:00:00 GMT</pubDate>
      <slash:comments>0</slash:comments>
      <trackback:ping>http://www.powershellcommunity.org/DesktopModules/Blog/Trackback.aspx?id=83</trackback:ping>
    <feedburner:origLink>http://www.powershellcommunity.org/Default.aspx?tabid=55&amp;EntryID=83</feedburner:origLink></item>
    <item>
      <title>PowerShell v2 eBook</title>
      <description>&lt;p&gt;The v2 Windows PowerShell eBook I'm co-authoring with Jeff Hicks (&lt;a href="http://www.sapienpress.com/pshv2"&gt;http://www.sapienpress.com/pshv2&lt;/a&gt;) is updated to reflect the latest Community Technology Preview (CTP) from Microsoft. Learn about the changes to remoting, the new transactional registry, the latest on script cmdlets, and much more - get involved with this CTP faster and get feedback to the PowerShell team!&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/powershellcommunity/~4/dWh01D0qY5s" height="1" width="1"/&gt;</description>
      <link>http://feedproxy.google.com/~r/powershellcommunity/~3/dWh01D0qY5s/Default.aspx</link>
      <author>don@sapien.com</author>
      <comments>http://www.powershellcommunity.org/Blogs/CommunityBlogs/tabid/55/EntryID/82/Default.aspx#Comments</comments>
      <guid isPermaLink="false">http://www.powershellcommunity.org/Default.aspx?tabid=55&amp;EntryID=82</guid>
      <pubDate>Wed, 21 May 2008 21:52:00 GMT</pubDate>
      <slash:comments>2</slash:comments>
      <trackback:ping>http://www.powershellcommunity.org/DesktopModules/Blog/Trackback.aspx?id=82</trackback:ping>
    <feedburner:origLink>http://www.powershellcommunity.org/Default.aspx?tabid=55&amp;EntryID=82</feedburner:origLink></item>
    <item>
      <title>Custom Cmdlets - Part three</title>
      <description>The last of a three-part series on the Cmdlets I have written for my own use.&lt;img src="http://feeds.feedburner.com/~r/powershellcommunity/~4/V3xTGCv-oIA" height="1" width="1"/&gt;</description>
      <link>http://feedproxy.google.com/~r/powershellcommunity/~3/V3xTGCv-oIA/Default.aspx</link>
      <comments>http://www.powershellcommunity.org/Blogs/CommunityBlogs/tabid/55/EntryID/81/Default.aspx#Comments</comments>
      <guid isPermaLink="false">http://www.powershellcommunity.org/Default.aspx?tabid=55&amp;EntryID=81</guid>
      <pubDate>Wed, 21 May 2008 05:18:00 GMT</pubDate>
      <slash:comments>0</slash:comments>
      <trackback:ping>http://www.powershellcommunity.org/DesktopModules/Blog/Trackback.aspx?id=81</trackback:ping>
    <feedburner:origLink>http://www.powershellcommunity.org/Default.aspx?tabid=55&amp;EntryID=81</feedburner:origLink></item>
    <item>
      <title>Script to HTML</title>
      <description>&lt;p&gt;In this blog, I cover features in &lt;a href="http://www.powershell.com/download/psp1.zip"&gt;PowerShell Plus&lt;/a&gt;. &lt;strong&gt;Feature #6:&lt;/strong&gt; Pasting script and console content to a blog&lt;/p&gt;
&lt;p&gt;if you wrote a cool script and would like to show it off to others, you can. PowerShell Plus supports color-coded script code transfer. Launch the editor (press CTRL+E), load your script, then copy it to your blog. Coincidentally, I'd like to share a script with you this way:&lt;/p&gt;
&lt;p&gt;&lt;span style="color: #800080"&gt;$helper&lt;/span&gt;&lt;span style="color: #000000"&gt; &lt;/span&gt;&lt;span style="color: #ff0000"&gt;=&lt;/span&gt;&lt;span style="color: #000000"&gt; &lt;/span&gt;&lt;span style="color: #5f9ea0"&gt;New-Object&lt;/span&gt;&lt;span style="color: #000000"&gt; &lt;/span&gt;&lt;span style="color: #5f9ea0"&gt;-COMObject&lt;/span&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/powershellcommunity/~4/Euoesj-LNxc" height="1" width="1"/&gt;</description>
      <link>http://feedproxy.google.com/~r/powershellcommunity/~3/Euoesj-LNxc/Default.aspx</link>
      <author>tobias.weltner@scriptinternals.de</author>
      <comments>http://www.powershellcommunity.org/Blogs/CommunityBlogs/tabid/55/EntryID/80/Default.aspx#Comments</comments>
      <guid isPermaLink="false">http://www.powershellcommunity.org/Default.aspx?tabid=55&amp;EntryID=80</guid>
      <pubDate>Mon, 19 May 2008 11:21:00 GMT</pubDate>
      <slash:comments>0</slash:comments>
      <trackback:ping>http://www.powershellcommunity.org/DesktopModules/Blog/Trackback.aspx?id=80</trackback:ping>
    <feedburner:origLink>http://www.powershellcommunity.org/Default.aspx?tabid=55&amp;EntryID=80</feedburner:origLink></item>
    <item>
      <title>Custom Cmdlets - Part two</title>
      <description>Part two of a three-part series on the Cmdlets I have written for my own use.&lt;img src="http://feeds.feedburner.com/~r/powershellcommunity/~4/JUIY-ujNZTA" height="1" width="1"/&gt;</description>
      <link>http://feedproxy.google.com/~r/powershellcommunity/~3/JUIY-ujNZTA/Default.aspx</link>
      <comments>http://www.powershellcommunity.org/Blogs/CommunityBlogs/tabid/55/EntryID/79/Default.aspx#Comments</comments>
      <guid isPermaLink="false">http://www.powershellcommunity.org/Default.aspx?tabid=55&amp;EntryID=79</guid>
      <pubDate>Thu, 15 May 2008 10:03:00 GMT</pubDate>
      <slash:comments>0</slash:comments>
      <trackback:ping>http://www.powershellcommunity.org/DesktopModules/Blog/Trackback.aspx?id=79</trackback:ping>
    <feedburner:origLink>http://www.powershellcommunity.org/Default.aspx?tabid=55&amp;EntryID=79</feedburner:origLink></item>
    <item>
      <title>Custom Cmdlets - Part one</title>
      <description>Part one of a three-part series on the Cmdlets I have written for my own use.&lt;img src="http://feeds.feedburner.com/~r/powershellcommunity/~4/7pzYliX4Lpw" height="1" width="1"/&gt;</description>
      <link>http://feedproxy.google.com/~r/powershellcommunity/~3/7pzYliX4Lpw/Default.aspx</link>
      <comments>http://www.powershellcommunity.org/Blogs/CommunityBlogs/tabid/55/EntryID/78/Default.aspx#Comments</comments>
      <guid isPermaLink="false">http://www.powershellcommunity.org/Default.aspx?tabid=55&amp;EntryID=78</guid>
      <pubDate>Wed, 14 May 2008 08:14:00 GMT</pubDate>
      <slash:comments>0</slash:comments>
      <trackback:ping>http://www.powershellcommunity.org/DesktopModules/Blog/Trackback.aspx?id=78</trackback:ping>
    <feedburner:origLink>http://www.powershellcommunity.org/Default.aspx?tabid=55&amp;EntryID=78</feedburner:origLink></item>
    <item>
      <title>Persisting History</title>
      <description>&lt;p&gt;In this blog, I cover features in &lt;a href="http://www.powershell.com/download/psp1.zip"&gt;PowerShell Plus&lt;/a&gt;. &lt;strong&gt;Feature #5:&lt;/strong&gt; History tracking&lt;/p&gt;
&lt;p&gt;I dont know about you, but I use command history a lot. It's just handy to press ArrowUp and get back my previous commands. Unfortunately, consoles generally seem to be a bit forgetful, and once you close powershell, all your history is gone. Of course you could export and re-import history using the PowerShell cmdlets, but that won't bring back the true console history and the ability to walk back your previous commands with the arrow keys. Bummer.&lt;/p&gt;
&lt;p&gt;In PowerShell+, that's better. When you close and re-open PowerShell+, all your history is still there. Cool, eh? What's even better, PS+ automatically streamlines your history, too, so when you close PS+, it only remembers unique commands, and it won't remember commands that resulted in an error.&lt;/p&gt;
&lt;p&gt;You can actua&lt;img src="http://feeds.feedburner.com/~r/powershellcommunity/~4/jc5tZAdaXJ0" height="1" width="1"/&gt;</description>
      <link>http://feedproxy.google.com/~r/powershellcommunity/~3/jc5tZAdaXJ0/Default.aspx</link>
      <author>tobias.weltner@scriptinternals.de</author>
      <comments>http://www.powershellcommunity.org/Blogs/CommunityBlogs/tabid/55/EntryID/77/Default.aspx#Comments</comments>
      <guid isPermaLink="false">http://www.powershellcommunity.org/Default.aspx?tabid=55&amp;EntryID=77</guid>
      <pubDate>Tue, 13 May 2008 16:10:00 GMT</pubDate>
      <slash:comments>0</slash:comments>
      <trackback:ping>http://www.powershellcommunity.org/DesktopModules/Blog/Trackback.aspx?id=77</trackback:ping>
    <feedburner:origLink>http://www.powershellcommunity.org/Default.aspx?tabid=55&amp;EntryID=77</feedburner:origLink></item>
    <item>
      <title>Variable Monitor with Ibuprofen Capsules and other Goodies</title>
      <description>&lt;p&gt;In this blog, I cover features in &lt;a href="http://www.powershell.com/download/psp1.zip"&gt;PowerShell Plus&lt;/a&gt;. &lt;strong&gt;Feature #4:&lt;/strong&gt; Live Variable Monitor&lt;/p&gt;
&lt;p&gt;There are tons of automatic PowerShell variables, and of course you can define your own. To keep track and explore variables, invoke the live variable monitor, simply by pressing CTRL+T. You get a list of all variables in current scope, and they are marked with star-symbols.&lt;/p&gt;
&lt;p&gt;To understand what the symbols are for, click on the down-arrow next to the funnel-button. With the funnel, you filter the var list. You can for example exclude all automatic variables and focus on new or changed variables only. This way, the list only shows stuff that changes. Right next to the funnel, there's a text box. You can enter any regular expression here to further enhance filtering.&lt;/p&gt;
&lt;p&gt;For example, to get a quick overview of all your preferences, enter Pref into the text b&lt;img src="http://feeds.feedburner.com/~r/powershellcommunity/~4/jzgRZmsQuC4" height="1" width="1"/&gt;</description>
      <link>http://feedproxy.google.com/~r/powershellcommunity/~3/jzgRZmsQuC4/Default.aspx</link>
      <author>tobias.weltner@scriptinternals.de</author>
      <comments>http://www.powershellcommunity.org/Blogs/CommunityBlogs/tabid/55/EntryID/76/Default.aspx#Comments</comments>
      <guid isPermaLink="false">http://www.powershellcommunity.org/Default.aspx?tabid=55&amp;EntryID=76</guid>
      <pubDate>Sun, 11 May 2008 11:51:00 GMT</pubDate>
      <slash:comments>0</slash:comments>
      <trackback:ping>http://www.powershellcommunity.org/DesktopModules/Blog/Trackback.aspx?id=76</trackback:ping>
    <feedburner:origLink>http://www.powershellcommunity.org/Default.aspx?tabid=55&amp;EntryID=76</feedburner:origLink></item>
    <item>
      <title>Console Tricks</title>
      <description>&lt;p&gt;In this blog, I cover features in &lt;a href="http://www.powershell.com/download/psp1.zip"&gt;PowerShell Plus&lt;/a&gt;. &lt;strong&gt;Feature #3:&lt;/strong&gt; Cool Console Tricks&lt;/p&gt;
&lt;p&gt;PowerShell Plus sports a real console, and that's good because it provides 100% PowerShell compatibility. However, our console is on steroids. Here are some things you can do with it:&lt;/p&gt;
&lt;p&gt;Intellisense-like support: Simply type $host and enter a dot, and there you go: intellisense-like menus open to help you code. These menus don't popup always automatically. On .NET namespaces, you might want to press TAB to invoke them:&lt;/p&gt;
&lt;p&gt;&lt;font face="Courier New"&gt;[System.Console]&lt;/font&gt;&lt;/p&gt;
&lt;p&gt;And when you add a double-colon, again there are menus, showing you the static members.&lt;/p&gt;
&lt;p&gt;&lt;font face="Courier New"&gt;[System.Console]::&lt;/font&gt;&lt;/p&gt;
&lt;p&gt;Another cool trick: drag a file into the console (&lt;img src="http://feeds.feedburner.com/~r/powershellcommunity/~4/YkXcTMdzYqE" height="1" width="1"/&gt;</description>
      <link>http://feedproxy.google.com/~r/powershellcommunity/~3/YkXcTMdzYqE/Default.aspx</link>
      <author>tobias.weltner@scriptinternals.de</author>
      <comments>http://www.powershellcommunity.org/Blogs/CommunityBlogs/tabid/55/EntryID/75/Default.aspx#Comments</comments>
      <guid isPermaLink="false">http://www.powershellcommunity.org/Default.aspx?tabid=55&amp;EntryID=75</guid>
      <pubDate>Fri, 09 May 2008 11:44:00 GMT</pubDate>
      <slash:comments>0</slash:comments>
      <trackback:ping>http://www.powershellcommunity.org/DesktopModules/Blog/Trackback.aspx?id=75</trackback:ping>
    <feedburner:origLink>http://www.powershellcommunity.org/Default.aspx?tabid=55&amp;EntryID=75</feedburner:origLink></item>
    <item>
      <title>Minimode #1 and #2</title>
      <description>&lt;p&gt;In this blog, I cover features in &lt;a href="http://www.powershell.com/download/psp1.zip"&gt;PowerShell Plus&lt;/a&gt;. &lt;strong&gt;Feature #2:&lt;/strong&gt; The various purist minimodes...&lt;/p&gt;
&lt;p&gt;I know PowerShell-Users love the pure stuff, and they love the console. Except sometimes it is nice to have some bells and whistels to help with object models and intellisense.&lt;/p&gt;
&lt;p&gt;This is why PS+ includes two things: a Minimode and - huh? - another Minimode!&lt;/p&gt;
&lt;p&gt;Minimode #1 can be invoked by CTRL+M. It turns all toolbars off and makes the console semi-transparent so you can see what is going on in the background.&lt;/p&gt;
&lt;p&gt;Minimode #2 can be invoked by ALT+SPACE. It leaves the console as it is but hides all toolbars. Press ALT again to get them back.&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/powershellcommunity/~4/SD5W2eoRZCk" height="1" width="1"/&gt;</description>
      <link>http://feedproxy.google.com/~r/powershellcommunity/~3/SD5W2eoRZCk/Default.aspx</link>
      <author>tobias.weltner@scriptinternals.de</author>
      <comments>http://www.powershellcommunity.org/Blogs/CommunityBlogs/tabid/55/EntryID/74/Default.aspx#Comments</comments>
      <guid isPermaLink="false">http://www.powershellcommunity.org/Default.aspx?tabid=55&amp;EntryID=74</guid>
      <pubDate>Thu, 08 May 2008 13:42:00 GMT</pubDate>
      <slash:comments>0</slash:comments>
      <trackback:ping>http://www.powershellcommunity.org/DesktopModules/Blog/Trackback.aspx?id=74</trackback:ping>
    <feedburner:origLink>http://www.powershellcommunity.org/Default.aspx?tabid=55&amp;EntryID=74</feedburner:origLink></item>
    <item>
      <title>Executing native commands in PS+ console</title>
      <description>&lt;p&gt;In this blog, I cover features in &lt;a href="http://www.powershell.com/download/psp1.zip"&gt;PowerShell Plus&lt;/a&gt;. &lt;strong&gt;Feature #1:&lt;/strong&gt; By pressing SHIFT + ENTER you can run commands within the old-style cmd.exe and avoid problems with backwards compatibility easily.&lt;/p&gt;
&lt;p&gt;PowerShell is "supposed" to be 100% backwards compatible but in reality it isn't. It can't. It uses some special characters such as parenthesis that modify the way a line is parsed. So the following simple command will fail in PowerShell:&lt;/p&gt;
&lt;p&gt;&lt;font face="Courier New"&gt;echo This won't work (because of the parenthesis)&lt;/font&gt;&lt;/p&gt;
&lt;p&gt;or&lt;/p&gt;
&lt;p&gt;&lt;font face="Courier New"&gt;wmic service where (startmode='Auto' and started=true) get /value&lt;/font&gt;&lt;/p&gt;
&lt;p&gt;To make working in PowerShell a one-stop thing, I added the capability to execute native commands in the old cmd.exe environment simply&lt;img src="http://feeds.feedburner.com/~r/powershellcommunity/~4/lbbb--EAjdE" height="1" width="1"/&gt;</description>
      <link>http://feedproxy.google.com/~r/powershellcommunity/~3/lbbb--EAjdE/Default.aspx</link>
      <author>tobias.weltner@scriptinternals.de</author>
      <comments>http://www.powershellcommunity.org/Blogs/CommunityBlogs/tabid/55/EntryID/73/Default.aspx#Comments</comments>
      <guid isPermaLink="false">http://www.powershellcommunity.org/Default.aspx?tabid=55&amp;EntryID=73</guid>
      <pubDate>Wed, 07 May 2008 16:37:00 GMT</pubDate>
      <slash:comments>0</slash:comments>
      <trackback:ping>http://www.powershellcommunity.org/DesktopModules/Blog/Trackback.aspx?id=73</trackback:ping>
    <feedburner:origLink>http://www.powershellcommunity.org/Default.aspx?tabid=55&amp;EntryID=73</feedburner:origLink></item>
    <item>
      <title>New PowerShell Training Videos</title>
      <description>&lt;p&gt;We're very pleased to announce a brand-new series of training videos for Windows PowerShell, &lt;a href="https://www.scriptingoutpost.com/c-8-scriptinganswerscom-university-class-on-disc.aspx"&gt;available now on our online store&lt;/a&gt;. These feature extremely high production values, tons of instructions, are in 720p high-definition video (viewable on your computer), hands-on exercises with guided answers, and much more. They're based upon the same outline we use in our instructor-led training classes, and these videos form the basis for our new &lt;a href="http://scriptinganswers.com/training/online/"&gt;online training&lt;/a&gt;. You can &lt;a href="http://www.scriptinganswers.com/Training/selfpaced/demovideo.asp"&gt;download demos of the new training&lt;/a&gt; immediately. Enjoy!&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/powershellcommunity/~4/bbg99EczvwA" height="1" width="1"/&gt;</description>
      <link>http://feedproxy.google.com/~r/powershellcommunity/~3/bbg99EczvwA/Default.aspx</link>
      <author>don@sapien.com</author>
      <comments>http://www.powershellcommunity.org/Blogs/CommunityBlogs/tabid/55/EntryID/72/Default.aspx#Comments</comments>
      <guid isPermaLink="false">http://www.powershellcommunity.org/Default.aspx?tabid=55&amp;EntryID=72</guid>
      <pubDate>Wed, 30 Apr 2008 14:48:00 GMT</pubDate>
      <slash:comments>0</slash:comments>
      <trackback:ping>http://www.powershellcommunity.org/DesktopModules/Blog/Trackback.aspx?id=72</trackback:ping>
    <feedburner:origLink>http://www.powershellcommunity.org/Default.aspx?tabid=55&amp;EntryID=72</feedburner:origLink></item>
    <item>
      <title>Windows PowerShell Virtual User Group Meeting #5</title>
      <description>&lt;p&gt;This is our fifth virtual event.&amp;#160; Invited speakers that will talk about various PowerShell-related topics: Bart De Smet (Microsoft), Steven Nelson (Microsoft), Hal Rottenberg (PowerScripting Podcast).&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/powershellcommunity/~4/6yGPnLsAKok" height="1" width="1"/&gt;</description>
      <link>http://feedproxy.google.com/~r/powershellcommunity/~3/6yGPnLsAKok/Default.aspx</link>
      <comments>http://www.powershellcommunity.org/Blogs/CommunityBlogs/tabid/55/EntryID/71/Default.aspx#Comments</comments>
      <guid isPermaLink="false">http://www.powershellcommunity.org/Default.aspx?tabid=55&amp;EntryID=71</guid>
      <pubDate>Wed, 16 Apr 2008 12:10:00 GMT</pubDate>
      <slash:comments>1</slash:comments>
      <trackback:ping>http://www.powershellcommunity.org/DesktopModules/Blog/Trackback.aspx?id=71</trackback:ping>
    <feedburner:origLink>http://www.powershellcommunity.org/Default.aspx?tabid=55&amp;EntryID=71</feedburner:origLink></item>
    <item>
      <title>PoSH goes MOC</title>
      <description>&lt;p&gt;Hello Community,&lt;br /&gt;
Microsoft Learning Team has listened to the calls of the MCT's.&lt;br /&gt;
&lt;br /&gt;
A new couse, currently in beta, is available. The coursename is:&lt;br /&gt;
&lt;strong&gt;"6434A- Scripting with Windows Powershell in Windows Server 2008"&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;Eleven modules with more than 300 pages of stuff.&amp;#160;&lt;br /&gt;
I'm looking forward to teach my first of those &lt;img alt="" src="/Providers/HtmlEditorProviders/Fck/FCKeditor/editor/images/smiley/msn/regular_smile.gif" /&gt;&lt;br /&gt;
&lt;br /&gt;
Greetings&lt;br /&gt;
Rolf&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/powershellcommunity/~4/BwT1j8E4XBQ" height="1" width="1"/&gt;</description>
      <link>http://feedproxy.google.com/~r/powershellcommunity/~3/BwT1j8E4XBQ/Default.aspx</link>
      <author>rolf@powershell-ag.de</author>
      <comments>http://www.powershellcommunity.org/Blogs/CommunityBlogs/tabid/55/EntryID/70/Default.aspx#Comments</comments>
      <guid isPermaLink="false">http://www.powershellcommunity.org/Default.aspx?tabid=55&amp;EntryID=70</guid>
      <pubDate>Sun, 06 Apr 2008 23:00:00 GMT</pubDate>
      <slash:comments>0</slash:comments>
      <trackback:ping>http://www.powershellcommunity.org/DesktopModules/Blog/Trackback.aspx?id=70</trackback:ping>
    <feedburner:origLink>http://www.powershellcommunity.org/Default.aspx?tabid=55&amp;EntryID=70</feedburner:origLink></item>
    <item>
      <title>Blogs are back</title>
      <description>&lt;p&gt;Blogs are working again.&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/powershellcommunity/~4/EF7eXyeQ0N4" height="1" width="1"/&gt;</description>
      <link>http://feedproxy.google.com/~r/powershellcommunity/~3/EF7eXyeQ0N4/Default.aspx</link>
      <comments>http://www.powershellcommunity.org/Blogs/CommunityBlogs/tabid/55/EntryID/69/Default.aspx#Comments</comments>
      <guid isPermaLink="false">http://www.powershellcommunity.org/Default.aspx?tabid=55&amp;EntryID=69</guid>
      <pubDate>Fri, 04 Apr 2008 12:10:00 GMT</pubDate>
      <slash:comments>1</slash:comments>
      <trackback:ping>http://www.powershellcommunity.org/DesktopModules/Blog/Trackback.aspx?id=69</trackback:ping>
    <feedburner:origLink>http://www.powershellcommunity.org/Default.aspx?tabid=55&amp;EntryID=69</feedburner:origLink></item>
    <item>
      <title>PowerShell + Exchange = New Book Preview</title>
      <description>Author Ilse van Criekinge is writing Exchange Management Shell: TFM, and two unedited preview chapters are now available on the SAPIEN Press Web site.&lt;img src="http://feeds.feedburner.com/~r/powershellcommunity/~4/3-quhuwEVY0" height="1" width="1"/&gt;</description>
      <link>http://feedproxy.google.com/~r/powershellcommunity/~3/3-quhuwEVY0/Default.aspx</link>
      <author>don@sapien.com</author>
      <comments>http://www.powershellcommunity.org/Blogs/CommunityBlogs/tabid/55/EntryID/67/Default.aspx#Comments</comments>
      <guid isPermaLink="false">http://www.powershellcommunity.org/Default.aspx?tabid=55&amp;EntryID=67</guid>
      <pubDate>Thu, 10 Jan 2008 04:45:00 GMT</pubDate>
      <slash:comments>0</slash:comments>
      <trackback:ping>http://www.powershellcommunity.org/DesktopModules/Blog/Trackback.aspx?id=67</trackback:ping>
    <feedburner:origLink>http://www.powershellcommunity.org/Default.aspx?tabid=55&amp;EntryID=67</feedburner:origLink></item>
    <item>
      <title>Interviewed on PowerScripting Podcast</title>
      <description>I was recently interviewed for Episode 16 of the PowerScripting Podcast. The hosts were kind enough to let me discuss several PowerShell-related topics in some detail, including my role with PowerShellCommunity.org, how to get started with PowerShell if you're a complete newbie, where this PowerShell thing is going anyway, and more. Give it a listen! Fair warning - it's pretty lengthy as podcasts go, but I think you'll agree that it's worth it. Play it during the morning commute!&lt;img src="http://feeds.feedburner.com/~r/powershellcommunity/~4/ioYHJX7w7SE" height="1" width="1"/&gt;</description>
      <link>http://feedproxy.google.com/~r/powershellcommunity/~3/ioYHJX7w7SE/Default.aspx</link>
      <author>don@sapien.com</author>
      <comments>http://www.powershellcommunity.org/Blogs/CommunityBlogs/tabid/55/EntryID/66/Default.aspx#Comments</comments>
      <guid isPermaLink="false">http://www.powershellcommunity.org/Default.aspx?tabid=55&amp;EntryID=66</guid>
      <pubDate>Mon, 07 Jan 2008 14:42:38 GMT</pubDate>
      <slash:comments>0</slash:comments>
      <trackback:ping>http://www.powershellcommunity.org/DesktopModules/Blog/Trackback.aspx?id=66</trackback:ping>
    <feedburner:origLink>http://www.powershellcommunity.org/Default.aspx?tabid=55&amp;EntryID=66</feedburner:origLink></item>
    <item>
      <title>PowerShell and IIS 7</title>
      <description>The introduction of IIS 7 with Windows 2008 brings a managed code (.NET) API for IIS.  This means we can administer it through PowerShell.  Add the remoting features of V2 and you have a very powerful administration tool.  This post shows some examples of remotely administering IIS 7 with PowerShell&lt;img src="http://feeds.feedburner.com/~r/powershellcommunity/~4/RRZSPXGrOSg" height="1" width="1"/&gt;</description>
      <link>http://feedproxy.google.com/~r/powershellcommunity/~3/RRZSPXGrOSg/Default.aspx</link>
      <author>powershell-uk@hotmail.co.uk</author>
      <comments>http://www.powershellcommunity.org/Blogs/CommunityBlogs/tabid/55/EntryID/65/Default.aspx#Comments</comments>
      <guid isPermaLink="false">http://www.powershellcommunity.org/Default.aspx?tabid=55&amp;EntryID=65</guid>
      <pubDate>Fri, 04 Jan 2008 10:06:42 GMT</pubDate>
      <slash:comments>0</slash:comments>
      <trackback:ping>http://www.powershellcommunity.org/DesktopModules/Blog/Trackback.aspx?id=65</trackback:ping>
    <feedburner:origLink>http://www.powershellcommunity.org/Default.aspx?tabid=55&amp;EntryID=65</feedburner:origLink></item>
    <item>
      <title>PowerShell and SubSonic</title>
      <description>PowerShell is the perfect tool for wrapping complex command-line tools.  By simplifying the API and using the built in Tab expansion capability, PowerShell makes even the most cumbersome commands usable without giving up any of their power.  In this example we'll look at how I converted a batch file for SubSonic to a PowerShell script.&lt;img src="http://feeds.feedburner.com/~r/powershellcommunity/~4/cwVaand7E2E" height="1" width="1"/&gt;</description>
      <link>http://feedproxy.google.com/~r/powershellcommunity/~3/cwVaand7E2E/Default.aspx</link>
      <author>joe.brinkman@dotnetnuke.com</author>
      <comments>http://www.powershellcommunity.org/Blogs/CommunityBlogs/tabid/55/EntryID/64/Default.aspx#Comments</comments>
      <guid isPermaLink="false">http://www.powershellcommunity.org/Default.aspx?tabid=55&amp;EntryID=64</guid>
      <pubDate>Tue, 01 Jan 2008 23:42:33 GMT</pubDate>
      <slash:comments>0</slash:comments>
      <trackback:ping>http://www.powershellcommunity.org/DesktopModules/Blog/Trackback.aspx?id=64</trackback:ping>
    <feedburner:origLink>http://www.powershellcommunity.org/Default.aspx?tabid=55&amp;EntryID=64</feedburner:origLink></item>
    <item>
      <title>Windows PowerShell virtual user group meeting #2--VIDEO ONLINE</title>
      <description>You'll find my edited videos of my second virtual user group meeting HERE along with the brief details on the contents of each video file.&lt;img src="http://feeds.feedburner.com/~r/powershellcommunity/~4/Rh_hc0ehpcY" height="1" width="1"/&gt;</description>
      <link>http://feedproxy.google.com/~r/powershellcommunity/~3/Rh_hc0ehpcY/Default.aspx</link>
      <comments>http://www.powershellcommunity.org/Blogs/CommunityBlogs/tabid/55/EntryID/63/Default.aspx#Comments</comments>
      <guid isPermaLink="false">http://www.powershellcommunity.org/Default.aspx?tabid=55&amp;EntryID=63</guid>
      <pubDate>Sun, 30 Dec 2007 02:32:54 GMT</pubDate>
      <slash:comments>0</slash:comments>
      <trackback:ping>http://www.powershellcommunity.org/DesktopModules/Blog/Trackback.aspx?id=63</trackback:ping>
    <feedburner:origLink>http://www.powershellcommunity.org/Default.aspx?tabid=55&amp;EntryID=63</feedburner:origLink></item>
    <item>
      <title>Improve our Community - Your Help Needed!</title>
      <description>Think something in this community could use improvement? You may be right. Here's how to be heard.&lt;img src="http://feeds.feedburner.com/~r/powershellcommunity/~4/d-ljPAiQ_BQ" height="1" width="1"/&gt;</description>
      <link>http://feedproxy.google.com/~r/powershellcommunity/~3/d-ljPAiQ_BQ/Default.aspx</link>
      <author>don@sapien.com</author>
      <comments>http://www.powershellcommunity.org/Blogs/CommunityBlogs/tabid/55/EntryID/62/Default.aspx#Comments</comments>
      <guid isPermaLink="false">http://www.powershellcommunity.org/Default.aspx?tabid=55&amp;EntryID=62</guid>
      <pubDate>Sat, 29 Dec 2007 03:38:55 GMT</pubDate>
      <slash:comments>1</slash:comments>
      <trackback:ping>http://www.powershellcommunity.org/DesktopModules/Blog/Trackback.aspx?id=62</trackback:ping>
    <feedburner:origLink>http://www.powershellcommunity.org/Default.aspx?tabid=55&amp;EntryID=62</feedburner:origLink></item>
    <item>
      <title>A load of scripting goodness for half price - Happy New Year!</title>
      <description>SAPIEN will offer PrimalScript Professional, two books, and PowerShell self-paced training for about 50% off on December 31st only.&lt;img src="http://feeds.feedburner.com/~r/powershellcommunity/~4/UCw5QB-bgKc" height="1" width="1"/&gt;</description>
      <link>http://feedproxy.google.com/~r/powershellcommunity/~3/UCw5QB-bgKc/Default.aspx</link>
      <author>don@sapien.com</author>
      <comments>http://www.powershellcommunity.org/Blogs/CommunityBlogs/tabid/55/EntryID/61/Default.aspx#Comments</comments>
      <guid isPermaLink="false">http://www.powershellcommunity.org/Default.aspx?tabid=55&amp;EntryID=61</guid>
      <pubDate>Fri, 28 Dec 2007 23:01:53 GMT</pubDate>
      <slash:comments>0</slash:comments>
      <trackback:ping>http://www.powershellcommunity.org/DesktopModules/Blog/Trackback.aspx?id=61</trackback:ping>
    <feedburner:origLink>http://www.powershellcommunity.org/Default.aspx?tabid=55&amp;EntryID=61</feedburner:origLink></item>
    <item>
      <title>PowerGUI Survey - Please respond</title>
      <description>We need your help and a couple of minutes of your time. Please go to this survey page and answer 5 simple questions on how you use PowerGUI today and where we should take it in the future.&lt;img src="http://feeds.feedburner.com/~r/powershellcommunity/~4/hUnMwXJj-Wg" height="1" width="1"/&gt;</description>
      <link>http://feedproxy.google.com/~r/powershellcommunity/~3/hUnMwXJj-Wg/Default.aspx</link>
      <comments>http://www.powershellcommunity.org/Blogs/CommunityBlogs/tabid/55/EntryID/60/Default.aspx#Comments</comments>
      <guid isPermaLink="false">http://www.powershellcommunity.org/Default.aspx?tabid=55&amp;EntryID=60</guid>
      <pubDate>Fri, 21 Dec 2007 11:10:20 GMT</pubDate>
      <slash:comments>0</slash:comments>
      <trackback:ping>http://www.powershellcommunity.org/DesktopModules/Blog/Trackback.aspx?id=60</trackback:ping>
    <feedburner:origLink>http://www.powershellcommunity.org/Default.aspx?tabid=55&amp;EntryID=60</feedburner:origLink></item>
    <item>
      <title>AD Cmdlets RTM</title>
      <description>AD cmdlets are finally gold!

We kind of kept sticking to the fashion of perpetual betas for quite some time now (since the first 1.0 beta released late March through the RC 1.0.5 this fall) and we feel that the product is now feature rich and stable enough for us to drop the beta label.&lt;img src="http://feeds.feedburner.com/~r/powershellcommunity/~4/5A3PUCdCYm4" height="1" width="1"/&gt;</description>
      <link>http://feedproxy.google.com/~r/powershellcommunity/~3/5A3PUCdCYm4/Default.aspx</link>
      <comments>http://www.powershellcommunity.org/Blogs/CommunityBlogs/tabid/55/EntryID/59/Default.aspx#Comments</comments>
      <guid isPermaLink="false">http://www.powershellcommunity.org/Default.aspx?tabid=55&amp;EntryID=59</guid>
      <pubDate>Fri, 21 Dec 2007 10:00:41 GMT</pubDate>
      <slash:comments>0</slash:comments>
      <trackback:ping>http://www.powershellcommunity.org/DesktopModules/Blog/Trackback.aspx?id=59</trackback:ping>
    <feedburner:origLink>http://www.powershellcommunity.org/Default.aspx?tabid=55&amp;EntryID=59</feedburner:origLink></item>
    <item>
      <title>Windows PowerShell TFM: 2nd now on Amazon</title>
      <description>Amazon.com now has a page for the 2nd edition of Windows PowerShell: TFM. This is a different book, with a ton of new content.  It has a separate ISBN, so make sure you are looking at http://www.amazon.com/Windows-PowerShell-v1-0-TFM-2nd/dp/0977659763&lt;img src="http://feeds.feedburner.com/~r/powershellcommunity/~4/O8DEe8eew3A" height="1" width="1"/&gt;</description>
      <link>http://feedproxy.google.com/~r/powershellcommunity/~3/O8DEe8eew3A/Default.aspx</link>
      <comments>http://www.powershellcommunity.org/Blogs/CommunityBlogs/tabid/55/EntryID/58/Default.aspx#Comments</comments>
      <guid isPermaLink="false">http://www.powershellcommunity.org/Default.aspx?tabid=55&amp;EntryID=58</guid>
      <pubDate>Tue, 18 Dec 2007 18:58:14 GMT</pubDate>
      <slash:comments>0</slash:comments>
      <trackback:ping>http://www.powershellcommunity.org/DesktopModules/Blog/Trackback.aspx?id=58</trackback:ping>
    <feedburner:origLink>http://www.powershellcommunity.org/Default.aspx?tabid=55&amp;EntryID=58</feedburner:origLink></item>
    <item>
      <title>Removing AD Attributes</title>
      <description>All those Set-* cmdlets are great at changing an attribute in AD, but how do you remove an attribute completely?&lt;img src="http://feeds.feedburner.com/~r/powershellcommunity/~4/5kvJbpvs3L8" height="1" width="1"/&gt;</description>
      <link>http://feedproxy.google.com/~r/powershellcommunity/~3/5kvJbpvs3L8/Default.aspx</link>
      <comments>http://www.powershellcommunity.org/Blogs/CommunityBlogs/tabid/55/EntryID/57/Default.aspx#Comments</comments>
      <guid isPermaLink="false">http://www.powershellcommunity.org/Default.aspx?tabid=55&amp;EntryID=57</guid>
      <pubDate>Tue, 18 Dec 2007 18:54:53 GMT</pubDate>
      <slash:comments>0</slash:comments>
      <trackback:ping>http://www.powershellcommunity.org/DesktopModules/Blog/Trackback.aspx?id=57</trackback:ping>
    <feedburner:origLink>http://www.powershellcommunity.org/Default.aspx?tabid=55&amp;EntryID=57</feedburner:origLink></item>
    <item>
      <title>PowerShell Help - Online!</title>
      <description>The PowerShell team has made the PowerShell Help available online, on TechNet.&lt;img src="http://feeds.feedburner.com/~r/powershellcommunity/~4/1qhWJ2cnxbg" height="1" width="1"/&gt;</description>
      <link>http://feedproxy.google.com/~r/powershellcommunity/~3/1qhWJ2cnxbg/Default.aspx</link>
      <author>don@sapien.com</author>
      <comments>http://www.powershellcommunity.org/Blogs/CommunityBlogs/tabid/55/EntryID/56/Default.aspx#Comments</comments>
      <guid isPermaLink="false">http://www.powershellcommunity.org/Default.aspx?tabid=55&amp;EntryID=56</guid>
      <pubDate>Tue, 18 Dec 2007 16:43:46 GMT</pubDate>
      <slash:comments>0</slash:comments>
      <trackback:ping>http://www.powershellcommunity.org/DesktopModules/Blog/Trackback.aspx?id=56</trackback:ping>
    <feedburner:origLink>http://www.powershellcommunity.org/Default.aspx?tabid=55&amp;EntryID=56</feedburner:origLink></item>
    <item>
      <title>PowerShell named the Best on Platforma 2008</title>
      <description>Platforma 2008 (aka TechEd Russia) team has just published the results of attendee surveys and the PowerShell session I did at the event got named the best of the show!&lt;img src="http://feeds.feedburner.com/~r/powershellcommunity/~4/nz_Md56zUVQ" height="1" width="1"/&gt;</description>
      <link>http://feedproxy.google.com/~r/powershellcommunity/~3/nz_Md56zUVQ/Default.aspx</link>
      <comments>http://www.powershellcommunity.org/Blogs/CommunityBlogs/tabid/55/EntryID/55/Default.aspx#Comments</comments>
      <guid isPermaLink="false">http://www.powershellcommunity.org/Default.aspx?tabid=55&amp;EntryID=55</guid>
      <pubDate>Tue, 18 Dec 2007 12:00:15 GMT</pubDate>
      <slash:comments>0</slash:comments>
      <trackback:ping>http://www.powershellcommunity.org/DesktopModules/Blog/Trackback.aspx?id=55</trackback:ping>
    <feedburner:origLink>http://www.powershellcommunity.org/Default.aspx?tabid=55&amp;EntryID=55</feedburner:origLink></item>
    <item>
      <title>Creating a management dashboard with PowerGadgets and PowerShell</title>
      <description>Several months ago I stumbled upon &lt;a href="http://www.powergadgets.com/"&gt;PowerGadgets&lt;/a&gt; and have been finding more and more uses for it ever since.  I was initially intrigued by the ability to run powershell scripts but didn't have any immediate needs that required that much power.  One of the strengths of PowerGadgets is the ability to run database queries and then to present the data using very slick graphs, guages and maps.&lt;img src="http://feeds.feedburner.com/~r/powershellcommunity/~4/030VgTGJxwk" height="1" width="1"/&gt;</description>
      <link>http://feedproxy.google.com/~r/powershellcommunity/~3/030VgTGJxwk/Default.aspx</link>
      <author>joe.brinkman@dotnetnuke.com</author>
      <comments>http://www.powershellcommunity.org/Blogs/CommunityBlogs/tabid/55/EntryID/54/Default.aspx#Comments</comments>
      <guid isPermaLink="false">http://www.powershellcommunity.org/Default.aspx?tabid=55&amp;EntryID=54</guid>
      <pubDate>Sun, 16 Dec 2007 23:30:51 GMT</pubDate>
      <slash:comments>0</slash:comments>
      <trackback:ping>http://www.powershellcommunity.org/DesktopModules/Blog/Trackback.aspx?id=54</trackback:ping>
    <feedburner:origLink>http://www.powershellcommunity.org/Default.aspx?tabid=55&amp;EntryID=54</feedburner:origLink></item>
    <item>
      <title>Setting demo AD environments</title>
      <description>Finally I will always have great AD demo environments with no accounts named TestUser01 or alike. ;) This is the outcome of the setting up test AD environments discussion we had this week. Darren and Rob suggested a couple of tricks on duplicating AD to a test lab, and xaegr provided a great link to US census information data on the most frequently used names, as well as a sample script I am re-using and enhancing below.&lt;img src="http://feeds.feedburner.com/~r/powershellcommunity/~4/tGITHS53vBc" height="1" width="1"/&gt;</description>
      <link>http://feedproxy.google.com/~r/powershellcommunity/~3/tGITHS53vBc/Default.aspx</link>
      <comments>http://www.powershellcommunity.org/Blogs/CommunityBlogs/tabid/55/EntryID/53/Default.aspx#Comments</comments>
      <guid isPermaLink="false">http://www.powershellcommunity.org/Default.aspx?tabid=55&amp;EntryID=53</guid>
      <pubDate>Fri, 14 Dec 2007 17:35:27 GMT</pubDate>
      <slash:comments>0</slash:comments>
      <trackback:ping>http://www.powershellcommunity.org/DesktopModules/Blog/Trackback.aspx?id=53</trackback:ping>
    <feedburner:origLink>http://www.powershellcommunity.org/Default.aspx?tabid=55&amp;EntryID=53</feedburner:origLink></item>
    <item>
      <title>How do you set up test AD environments?</title>
      <description>I am often asked how PowerShell can be used to set up test or lab Active Directory environments - and frankly could not come up with a single comprehensive answer - different people need different things in their labs. In this post I go through a few options of that...&lt;img src="http://feeds.feedburner.com/~r/powershellcommunity/~4/KFvpvzNNtVk" height="1" width="1"/&gt;</description>
      <link>http://feedproxy.google.com/~r/powershellcommunity/~3/KFvpvzNNtVk/Default.aspx</link>
      <comments>http://www.powershellcommunity.org/Blogs/CommunityBlogs/tabid/55/EntryID/52/Default.aspx#Comments</comments>
      <guid isPermaLink="false">http://www.powershellcommunity.org/Default.aspx?tabid=55&amp;EntryID=52</guid>
      <pubDate>Wed, 12 Dec 2007 12:34:52 GMT</pubDate>
      <slash:comments>0</slash:comments>
      <trackback:ping>http://www.powershellcommunity.org/DesktopModules/Blog/Trackback.aspx?id=52</trackback:ping>
    <feedburner:origLink>http://www.powershellcommunity.org/Default.aspx?tabid=55&amp;EntryID=52</feedburner:origLink></item>
    <item>
      <title>Not PowerShell. Still cool.</title>
      <description>As someone who spends as much time away from home as at home, I value simple, effective travel tools. This one blew me away, and it's free.&lt;img src="http://feeds.feedburner.com/~r/powershellcommunity/~4/f_Cd0lgD5vQ" height="1" width="1"/&gt;</description>
      <link>http://feedproxy.google.com/~r/powershellcommunity/~3/f_Cd0lgD5vQ/Default.aspx</link>
      <author>don@sapien.com</author>
      <comments>http://www.powershellcommunity.org/Blogs/CommunityBlogs/tabid/55/EntryID/51/Default.aspx#Comments</comments>
      <guid isPermaLink="false">http://www.powershellcommunity.org/Default.aspx?tabid=55&amp;EntryID=51</guid>
      <pubDate>Tue, 11 Dec 2007 23:01:30 GMT</pubDate>
      <slash:comments>0</slash:comments>
      <trackback:ping>http://www.powershellcommunity.org/DesktopModules/Blog/Trackback.aspx?id=51</trackback:ping>
    <feedburner:origLink>http://www.powershellcommunity.org/Default.aspx?tabid=55&amp;EntryID=51</feedburner:origLink></item>
    <item>
      <title>PowerShell Analyzer 1.0 and PowerShell Plus Beta Available for free.</title>
      <description>PowerShell Analyzer 1.0 is finally released. For a week or two we consider this a "soft" launch, just in case there is some major issue that eluded our testing, but we are pretty confident its stable. 
Additionally, if you have already used your 45 Day trial, we have EXTENDED it another 45 days.
PowerShell Plus is now available with a 45 Day trial as well, and Additionally its available fully free for Non Commercial use as well.&lt;img src="http://feeds.feedburner.com/~r/powershellcommunity/~4/Jtv_gQv7AKA" height="1" width="1"/&gt;</description>
      <link>http://feedproxy.google.com/~r/powershellcommunity/~3/Jtv_gQv7AKA/Default.aspx</link>
      <comments>http://www.powershellcommunity.org/Blogs/CommunityBlogs/tabid/55/EntryID/50/Default.aspx#Comments</comments>
      <guid isPermaLink="false">http://www.powershellcommunity.org/Default.aspx?tabid=55&amp;EntryID=50</guid>
      <pubDate>Sat, 08 Dec 2007 09:52:49 GMT</pubDate>
      <slash:comments>0</slash:comments>
      <trackback:ping>http://www.powershellcommunity.org/DesktopModules/Blog/Trackback.aspx?id=50</trackback:ping>
    <feedburner:origLink>http://www.powershellcommunity.org/Default.aspx?tabid=55&amp;EntryID=50</feedburner:origLink></item>
    <item>
      <title>Back in BlogLand</title>
      <description>Finally my main blog is back in Business. I had gotten discouraged with my previous web host and abundant comment spam, and just plain being busy. But now with the help of an updated WordPress, new Host and Windows Live Writer all should be good.&lt;img src="http://feeds.feedburner.com/~r/powershellcommunity/~4/X4L5DFAhvGQ" height="1" width="1"/&gt;</description>
      <link>http://feedproxy.google.com/~r/powershellcommunity/~3/X4L5DFAhvGQ/Default.aspx</link>
      <comments>http://www.powershellcommunity.org/Blogs/CommunityBlogs/tabid/55/EntryID/49/Default.aspx#Comments</comments>
      <guid isPermaLink="false">http://www.powershellcommunity.org/Default.aspx?tabid=55&amp;EntryID=49</guid>
      <pubDate>Sat, 08 Dec 2007 09:21:29 GMT</pubDate>
      <slash:comments>1</slash:comments>
      <trackback:ping>http://www.powershellcommunity.org/DesktopModules/Blog/Trackback.aspx?id=49</trackback:ping>
    <feedburner:origLink>http://www.powershellcommunity.org/Default.aspx?tabid=55&amp;EntryID=49</feedburner:origLink></item>
    <item>
      <title>Why AppDomains are not a Silver Bullet</title>
      <description>As knowledge of PowerShell increases for those new to .NET, there comes a point when people start to notice some shortcomings of the Assembly loading/unloading mechanisms of the 2.0 CLR. Namely, once you load an assembly into PowerShell to use it, you can't unload it again. The only way to remove it from memory is to restart PowerShell. Eventually, you might read something about how Assemblies can be loaded into AppDomains, and AppDomains themselves can be unloaded. This is true, but for the most part it is not much use in PowerShell unless the Types in question where specifically designed with this in mind. For those of you who understand enough of what I'm talking about to get this far without going "huh?", the following script will demonstrate some of the issues at hand...&lt;img src="http://feeds.feedburner.com/~r/powershellcommunity/~4/7KSlJaF2KRU" height="1" width="1"/&gt;</description>
      <link>http://feedproxy.google.com/~r/powershellcommunity/~3/7KSlJaF2KRU/Default.aspx</link>
      <author>oising@gmail.com</author>
      <comments>http://www.powershellcommunity.org/Blogs/CommunityBlogs/tabid/55/EntryID/48/Default.aspx#Comments</comments>
      <guid isPermaLink="false">http://www.powershellcommunity.org/Default.aspx?tabid=55&amp;EntryID=48</guid>
      <pubDate>Fri, 07 Dec 2007 23:49:37 GMT</pubDate>
      <slash:comments>0</slash:comments>
      <trackback:ping>http://www.powershellcommunity.org/DesktopModules/Blog/Trackback.aspx?id=48</trackback:ping>
    <feedburner:origLink>http://www.powershellcommunity.org/Default.aspx?tabid=55&amp;EntryID=48</feedburner:origLink></item>
    <item>
      <title>PowerGUI Wallpaper</title>
      <description>Thanks to Andrey Tsarkov we now have a PowerGUI Wallpaper available from the PowerGUI downloads page: http://powergui.org/downloads.jspa&lt;img src="http://feeds.feedburner.com/~r/powershellcommunity/~4/Pgsgu-t58rk" height="1" width="1"/&gt;</description>
      <link>http://feedproxy.google.com/~r/powershellcommunity/~3/Pgsgu-t58rk/Default.aspx</link>
      <comments>http://www.powershellcommunity.org/Blogs/CommunityBlogs/tabid/55/EntryID/47/Default.aspx#Comments</comments>
      <guid isPermaLink="false">http://www.powershellcommunity.org/Default.aspx?tabid=55&amp;EntryID=47</guid>
      <pubDate>Fri, 07 Dec 2007 14:17:10 GMT</pubDate>
      <slash:comments>0</slash:comments>
      <trackback:ping>http://www.powershellcommunity.org/DesktopModules/Blog/Trackback.aspx?id=47</trackback:ping>
    <feedburner:origLink>http://www.powershellcommunity.org/Default.aspx?tabid=55&amp;EntryID=47</feedburner:origLink></item>
  </channel>
</rss>
