<?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/" xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd"><channel><title>PowerShell.com</title><link>http://powershell.com/cs/blogs/</link><description>The Place for PowerShell people: Home of Dr. Tobias Weltner, PowerShell MVP</description><dc:language>en-US</dc:language><generator>CommunityServer 2008.5 (Build: 30929.2835)</generator><item><title>Manage winrm settings with wsman provider</title><link>http://powershell.com/cs/blogs/windows-powershell-team/archive/2009/01/06/manage-winrm-settings-with-wsman-provider.aspx</link><pubDate>Tue, 06 Jan 2009 20:57:00 GMT</pubDate><guid isPermaLink="false">f421715f-7aba-45f0-8a8d-44de5318a3a7:814</guid><dc:creator>Windows PowerShell Blog</dc:creator><slash:comments>0</slash:comments><description>PowerShell remoting is built on top of Windows Remote Management (WinRM), which is Microsoft’s implementation of WS-Management protocol. You can use winrm.cmd command line tool to query and manage winrm settings. PowerShell V2 CTP3 contains a wsman provider for you to manage winrm settings with the standard *-Item cmdlets . Let’s try it out: PS C:\&amp;gt; cd wsman: PS WSMan:\&amp;gt; dir WSManConfig: Microsoft Read More......(&lt;a href="http://powershell.com/cs/blogs/windows-powershell-team/archive/2009/01/06/manage-winrm-settings-with-wsman-provider.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://powershell.com/cs/aggbug.aspx?PostID=814" width="1" height="1"&gt;</description><category domain="http://powershell.com/cs/blogs/windows-powershell-team/archive/tags/Remoting/default.aspx">Remoting</category></item><item><title>Get-Decimal1.ps1</title><link>http://powershell.com/cs/blogs/powershell-scripts/archive/2009/01/06/get-decimal1-ps1.aspx</link><pubDate>Tue, 06 Jan 2009 16:06:00 GMT</pubDate><guid isPermaLink="false">f421715f-7aba-45f0-8a8d-44de5318a3a7:808</guid><dc:creator>PowerShell Scripts</dc:creator><slash:comments>0</slash:comments><description>&amp;lt; # &amp;#160; .SYNOPSIS&amp;#160; &amp;#160;&amp;#160;&amp;#160; Demonstrates Decimal arithmetic.&amp;#160; .DESCRIPTION&amp;#160; &amp;#160;&amp;#160;&amp;#160; This script Creates two decimals, then multiplys them and displays them.&amp;#160;&amp;#160; .NOTES&amp;#160; &amp;#160;&amp;#160;&amp;#160; File Name&amp;#160; : get-decimal1.ps1&amp;#160; &amp;#160;&amp;#160;&amp;#160; Author&amp;#160;&amp;#160;&amp;#160;&amp;#160; : Thomas Lee - tfl @psp .co.uk&amp;#160; &amp;#160;&amp;#160;&amp;#160; Requires&amp;#160;&amp;#160; Read More......(&lt;a href="http://powershell.com/cs/blogs/powershell-scripts/archive/2009/01/06/get-decimal1-ps1.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://powershell.com/cs/aggbug.aspx?PostID=808" width="1" height="1"&gt;</description><category domain="http://powershell.com/cs/blogs/powershell-scripts/archive/tags/PowerShell+Scripts/default.aspx">PowerShell Scripts</category><category domain="http://powershell.com/cs/blogs/powershell-scripts/archive/tags/PowerShell/default.aspx">PowerShell</category><category domain="http://powershell.com/cs/blogs/powershell-scripts/archive/tags/scripts/default.aspx">scripts</category><category domain="http://powershell.com/cs/blogs/powershell-scripts/archive/tags/System.Decimal/default.aspx">System.Decimal</category></item><item><title>PowerShell Audit Reports – Turning Great Scripts Into a Module</title><link>http://powershell.com/cs/blogs/under-the-stairs/archive/2009/01/06/powershell-audit-reports-turning-great-scripts-into-a-module.aspx</link><pubDate>Tue, 06 Jan 2009 12:25:00 GMT</pubDate><guid isPermaLink="false">f421715f-7aba-45f0-8a8d-44de5318a3a7:806</guid><dc:creator>Under The Stairs</dc:creator><slash:comments>0</slash:comments><description>I just read a neat blog post entitled PowerShelling Audit Reports over on the TenBrink Tech blog . This blog post sets out three scripts: GetRecursiveGroupMembership.ps1, Audit-QuickGroup.ps1, and Audit-MultipleGroups.ps1. The second and third make use Read More......(&lt;a href="http://powershell.com/cs/blogs/under-the-stairs/archive/2009/01/06/powershell-audit-reports-turning-great-scripts-into-a-module.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://powershell.com/cs/aggbug.aspx?PostID=806" width="1" height="1"&gt;</description><category domain="http://powershell.com/cs/blogs/under-the-stairs/archive/tags/PowerShell+V2/default.aspx">PowerShell V2</category><category domain="http://powershell.com/cs/blogs/under-the-stairs/archive/tags/CTP3/default.aspx">CTP3</category><category domain="http://powershell.com/cs/blogs/under-the-stairs/archive/tags/module/default.aspx">module</category><category domain="http://powershell.com/cs/blogs/under-the-stairs/archive/tags/Quest+QAD+Tools/default.aspx">Quest QAD Tools</category><category domain="http://powershell.com/cs/blogs/under-the-stairs/archive/tags/manifest/default.aspx">manifest</category><category domain="http://powershell.com/cs/blogs/under-the-stairs/archive/tags/Quest/default.aspx">Quest</category></item><item><title>PowerShell-Scripting.com</title><link>http://powershell.com/cs/blogs/under-the-stairs/archive/2009/01/05/powershell-scripting-com.aspx</link><pubDate>Mon, 05 Jan 2009 22:55:00 GMT</pubDate><guid isPermaLink="false">f421715f-7aba-45f0-8a8d-44de5318a3a7:801</guid><dc:creator>Under The Stairs</dc:creator><slash:comments>0</slash:comments><description>My French is none too great. If it were, PowerShell-Scripting.com might be of more use. The site looks to be a rich resource for French speaking PowerShell users. Now if only they’s list my PowerShell Scripts blog ( http://pshscripts.blogspot.com )! Technorati Read More......(&lt;a href="http://powershell.com/cs/blogs/under-the-stairs/archive/2009/01/05/powershell-scripting-com.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://powershell.com/cs/aggbug.aspx?PostID=801" width="1" height="1"&gt;</description><category domain="http://powershell.com/cs/blogs/under-the-stairs/archive/tags/PowerShell/default.aspx">PowerShell</category><category domain="http://powershell.com/cs/blogs/under-the-stairs/archive/tags/web+site/default.aspx">web site</category><category domain="http://powershell.com/cs/blogs/under-the-stairs/archive/tags/french/default.aspx">french</category></item><item><title>Checkout Out-WPF</title><link>http://powershell.com/cs/blogs/windows-powershell-team/archive/2009/01/05/checkout-out-wpf.aspx</link><pubDate>Mon, 05 Jan 2009 18:50:29 GMT</pubDate><guid isPermaLink="false">f421715f-7aba-45f0-8a8d-44de5318a3a7:794</guid><dc:creator>Windows PowerShell Blog</dc:creator><slash:comments>0</slash:comments><description>Joel (Jaykul) Bennett has a cool post HERE where he is experimenting with some GUI scripting toolkits and a utility Out-WPF.&amp;#160; You can also checkout a Screencast of Out-WPF working HERE .&amp;#160; It is very cool and very short so give it a look-see. Scripting GUIs with PowerShell is going to be a REALLY BIG DEAL going forward. Jeffrey Snover [MSFT] Windows Management Partner Architect Visit the Windows Read More......(&lt;a href="http://powershell.com/cs/blogs/windows-powershell-team/archive/2009/01/05/checkout-out-wpf.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://powershell.com/cs/aggbug.aspx?PostID=794" width="1" height="1"&gt;</description></item><item><title>Invoking Methods Using Variables</title><link>http://powershell.com/cs/blogs/windows-powershell-team/archive/2009/01/05/invoking-methods-using-variables.aspx</link><pubDate>Mon, 05 Jan 2009 17:05:26 GMT</pubDate><guid isPermaLink="false">f421715f-7aba-45f0-8a8d-44de5318a3a7:795</guid><dc:creator>Windows PowerShell Blog</dc:creator><slash:comments>0</slash:comments><description>You can have a lot of fun with PowerShell.&amp;#160; Makes sense right - we&amp;#39;re busting our butts off and we get to define it so why wouldn&amp;#39;t we make it fun? Your busting your butts off at your job as well so why shouldn&amp;#39;t your tools be fun?&amp;#160; Right? In particular, our late binding of names allows you to do some really cool, really powerful stuff.&amp;#160; Here is an example: PS&amp;gt; $d=Get Read More......(&lt;a href="http://powershell.com/cs/blogs/windows-powershell-team/archive/2009/01/05/invoking-methods-using-variables.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://powershell.com/cs/aggbug.aspx?PostID=795" width="1" height="1"&gt;</description></item><item><title>Get-System.EnvironmentsStaticProperties1.ps1</title><link>http://powershell.com/cs/blogs/powershell-scripts/archive/2009/01/05/get-system-environmentsstaticproperties1-ps1.aspx</link><pubDate>Mon, 05 Jan 2009 15:44:00 GMT</pubDate><guid isPermaLink="false">f421715f-7aba-45f0-8a8d-44de5318a3a7:790</guid><dc:creator>PowerShell Scripts</dc:creator><slash:comments>0</slash:comments><description>&amp;lt; # &amp;#160; .SYNOPSIS&amp;#160; &amp;#160;&amp;#160;&amp;#160; Demonstrates the static properties on System.Environment&amp;#160; .DESCRIPTION&amp;#160; &amp;#160;&amp;#160;&amp;#160; This script uses the System.Environment class to retrieve interesting&amp;#160; &amp;#160;&amp;#160;&amp;#160; information about your system. The fields returned are static fields&amp;#160;&amp;#160; &amp;#160;&amp;#160;&amp;#160; on the System.Environment class.&amp;#160; .NOTES&amp;#160; &amp;#160;&amp;#160;&amp;#160; Read More......(&lt;a href="http://powershell.com/cs/blogs/powershell-scripts/archive/2009/01/05/get-system-environmentsstaticproperties1-ps1.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://powershell.com/cs/aggbug.aspx?PostID=790" width="1" height="1"&gt;</description><category domain="http://powershell.com/cs/blogs/powershell-scripts/archive/tags/PowerShell+Scripts/default.aspx">PowerShell Scripts</category><category domain="http://powershell.com/cs/blogs/powershell-scripts/archive/tags/PowerShell/default.aspx">PowerShell</category><category domain="http://powershell.com/cs/blogs/powershell-scripts/archive/tags/scripts/default.aspx">scripts</category><category domain="http://powershell.com/cs/blogs/powershell-scripts/archive/tags/system.environment/default.aspx">system.environment</category></item><item><title>Scott Herold - Getting Started With PowerShell and PowerGUI in your Virtual Infrastructure</title><link>http://powershell.com/cs/blogs/windows-powershell-team/archive/2009/01/05/scott-herold-getting-started-with-powershell-and-powergui-in-your-virtual-infrastructure.aspx</link><pubDate>Mon, 05 Jan 2009 13:13:57 GMT</pubDate><guid isPermaLink="false">f421715f-7aba-45f0-8a8d-44de5318a3a7:788</guid><dc:creator>Windows PowerShell Blog</dc:creator><slash:comments>0</slash:comments><description>Scott Herold has published the first of a three part series called Getting Started With PowerShell and PowerGUI in your Virtual Infrastructure .&amp;#160; I believe that MOST admins should spend time getting&amp;#160; PowerGUI in focus and especially those admins that are intimidated by the command line interface.&amp;#160; Scott only has part 1 of his series available and while it applies to Virtual Infrastructure Read More......(&lt;a href="http://powershell.com/cs/blogs/windows-powershell-team/archive/2009/01/05/scott-herold-getting-started-with-powershell-and-powergui-in-your-virtual-infrastructure.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://powershell.com/cs/aggbug.aspx?PostID=788" width="1" height="1"&gt;</description></item><item><title>Revisiting Old Posts: Get-Process | Dir (about ValueFromPipelineByPropertyName)</title><link>http://powershell.com/cs/blogs/windows-powershell-team/archive/2009/01/05/revisiting-old-posts-get-process-dir-about-valuefrompipelinebypropertyname.aspx</link><pubDate>Mon, 05 Jan 2009 09:54:03 GMT</pubDate><guid isPermaLink="false">f421715f-7aba-45f0-8a8d-44de5318a3a7:789</guid><dc:creator>Windows PowerShell Blog</dc:creator><slash:comments>0</slash:comments><description>A number of PowerShell MVPs and PowerShell team members are helping me to compile a table of contents for our blog, which basically means that I’m getting to go back and revisit all of the fun stuff posted to the PowerShell blog over the past few years.&amp;#160; It’s a fun an educational process, and, hopefully, when we’re done the blog will be a much simpler place to explore. I’m trying to keep my eye Read More......(&lt;a href="http://powershell.com/cs/blogs/windows-powershell-team/archive/2009/01/05/revisiting-old-posts-get-process-dir-about-valuefrompipelinebypropertyname.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://powershell.com/cs/aggbug.aspx?PostID=789" width="1" height="1"&gt;</description><category domain="http://powershell.com/cs/blogs/windows-powershell-team/archive/tags/ValueFromPiplelineByPropertyName/default.aspx">ValueFromPiplelineByPropertyName</category></item><item><title>PS&gt; Dir –A D     The Screencast</title><link>http://powershell.com/cs/blogs/windows-powershell-team/archive/2009/01/04/ps-gt-dir-a-d-the-screencast.aspx</link><pubDate>Mon, 05 Jan 2009 02:32:00 GMT</pubDate><guid isPermaLink="false">f421715f-7aba-45f0-8a8d-44de5318a3a7:787</guid><dc:creator>Windows PowerShell Blog</dc:creator><slash:comments>0</slash:comments><description>I decided to experiment with a screencast. This is my first and I have no idea what I’m doing so please forgive me if it sucks. I’d like to know whether you find this format useful or not and then specific feedback about how to make the screencast better (e.g. I recorded it at 1024x768 - is that good or too large?). In my previous blog – I mentioned that Proxy cmdlets are super important and powerful Read More......(&lt;a href="http://powershell.com/cs/blogs/windows-powershell-team/archive/2009/01/04/ps-gt-dir-a-d-the-screencast.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://powershell.com/cs/aggbug.aspx?PostID=787" width="1" height="1"&gt;</description><category domain="http://powershell.com/cs/blogs/windows-powershell-team/archive/tags/PowerShell+V2/default.aspx">PowerShell V2</category><category domain="http://powershell.com/cs/blogs/windows-powershell-team/archive/tags/CTP3/default.aspx">CTP3</category><category domain="http://powershell.com/cs/blogs/windows-powershell-team/archive/tags/Jeffrey+Snover/default.aspx">Jeffrey Snover</category><category domain="http://powershell.com/cs/blogs/windows-powershell-team/archive/tags/Proxy/default.aspx">Proxy</category><category domain="http://powershell.com/cs/blogs/windows-powershell-team/archive/tags/ScreenCast/default.aspx">ScreenCast</category></item><item><title>Using PowerShellPlus with PowerShell V2 (CTP3)</title><link>http://powershell.com/cs/blogs/tobias/archive/2009/01/04/using-powershellplus-with-powershell-v2-ctp3.aspx</link><pubDate>Sun, 04 Jan 2009 21:54:00 GMT</pubDate><guid isPermaLink="false">f421715f-7aba-45f0-8a8d-44de5318a3a7:803</guid><dc:creator>Tobias Weltner</dc:creator><slash:comments>1</slash:comments><description>&lt;p&gt;The great news is: PowerShellPlus works as-is with PowerShell V1 and PowerShell V2, indicating the stable and solid approach of its engine. No updates needed. From the very beginning, we took care to use only approved and backwards-compatible PowerShell APIs.&lt;/p&gt;
&lt;p&gt;You don&amp;#39;t use &lt;a href="http://www.powershellplus.com"&gt;PowerShellPlus&lt;/a&gt; yet?&amp;nbsp; It is an awesome interactive console and PowerShell editor, and you should really try it! It is derived from famous &amp;quot;PowerShellIDE&amp;quot; which was the world&amp;#39;s first PowerShell GUI, editor and debugger (surfaced June 2006). Yet again, it pays off to have solid 4 years of experience in this product.&lt;/p&gt;
&lt;p&gt;There are a couple of things you should know when you just upgraded from V1 to V2 to get PSP to recognize the new V2 features.&lt;/p&gt;
&lt;h2&gt;Update the Cache&lt;/h2&gt;
&lt;p&gt;For speed purposes, PowerShellPlus caches information regarding available Snap-Ins and Cmdlets. So when you have been using PSP on PowerShell V1 for a while and upgrade to PowerShell V2 CTP3, things continue to work as expected except all new V2 specific Cmdlet parameters and help pages are still missing.&lt;/p&gt;
&lt;p&gt;Normally, PSP detects at startup all freshly added Snapins and adds them to its cache. Upgrading PowerShell is a whole new ballgame though because actually no new snapins is added. Instead, existing snapins are updated.&lt;/p&gt;
&lt;p&gt;To manually reset and update PSPs internal cache, do this:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Launch PowerShell Plus&lt;/li&gt;
&lt;li&gt;Hold down SHIFT when the splash screen opens to open the startup management dialog&lt;/li&gt;
&lt;li&gt;Check the option &amp;quot;Clear cached Cmdlet info&amp;quot;, then click OK&lt;/li&gt;
&lt;li&gt;PSP starts and re-examines all available snapins. This may take a minute or two, and you will see a green bar with progress information. Once the green bar is gone, you are all set.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;Once you cleared and updated the cache, try this:&lt;/p&gt;
&lt;p&gt;Get-WMIObject -&lt;/p&gt;
&lt;p&gt;Code completion will show the complete list of V2 parameters.&lt;/p&gt;
&lt;h2&gt;Update the Learning Center&lt;/h2&gt;
&lt;p&gt;If you&amp;#39;d also like to update the learning center help pages, keep this in mind: the procedure you just executed automatically adds all new help topics to the learning center. It does not update existing topics though. So to update the learning center, simply delete its cache before you do the procedure above (&amp;quot;Yeah, thanks for telling me now! Just did it!&amp;quot; -&amp;nbsp;oh well, ok, just do it again)!&lt;/p&gt;
&lt;p&gt;How do I clear the learning center cache? For example like this:&lt;/p&gt;
&lt;p&gt;del $env:localappdata\PowerShellPlus\manpages\*.htm -whatif&lt;/p&gt;
&lt;p&gt;(Remove the -whatif if you are confident you typed in the correct line)&lt;/p&gt;
&lt;h2&gt;What&amp;#39;s Next?&lt;/h2&gt;
&lt;p&gt;Of course there are plenty of additional extras in PowerShell V2 like block comments and inline code. We will support them with one of our next maintenance releases but for now, isn&amp;#39;t it good to know that PowerShellPlus runs beautifully with PowerShell V2 CTP3? &lt;/p&gt;
&lt;p&gt;Cheers&lt;/p&gt;
&lt;p&gt;-Tobias&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://powershell.com/cs/aggbug.aspx?PostID=803" width="1" height="1"&gt;</description><category domain="http://powershell.com/cs/blogs/tobias/archive/tags/PowerShellPlus/default.aspx">PowerShellPlus</category><category domain="http://powershell.com/cs/blogs/tobias/archive/tags/Cache/default.aspx">Cache</category><category domain="http://powershell.com/cs/blogs/tobias/archive/tags/CTP3/default.aspx">CTP3</category></item><item><title>Extending and/or Modifing Commands with Proxies</title><link>http://powershell.com/cs/blogs/windows-powershell-team/archive/2009/01/04/extending-and-or-modifing-commands-with-proxies.aspx</link><pubDate>Sun, 04 Jan 2009 16:55:00 GMT</pubDate><guid isPermaLink="false">f421715f-7aba-45f0-8a8d-44de5318a3a7:786</guid><dc:creator>Windows PowerShell Blog</dc:creator><slash:comments>0</slash:comments><description>There are so many powerful features in V2, it is hard to know where to begin. This one is going to blow to top of your head off when you understand what it enables you to do. In this blog, I talk about Proxy Cmdlets which is the ability for one Cmdlet to call another. You could always do this but to do it right has always been very difficult. In particular, what you want to have happen is to be able Read More......(&lt;a href="http://powershell.com/cs/blogs/windows-powershell-team/archive/2009/01/04/extending-and-or-modifing-commands-with-proxies.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://powershell.com/cs/aggbug.aspx?PostID=786" width="1" height="1"&gt;</description><category domain="http://powershell.com/cs/blogs/windows-powershell-team/archive/tags/PowerShell+V2/default.aspx">PowerShell V2</category><category domain="http://powershell.com/cs/blogs/windows-powershell-team/archive/tags/CTP3/default.aspx">CTP3</category><category domain="http://powershell.com/cs/blogs/windows-powershell-team/archive/tags/Modules/default.aspx">Modules</category><category domain="http://powershell.com/cs/blogs/windows-powershell-team/archive/tags/Jeffrey+Snover/default.aspx">Jeffrey Snover</category><category domain="http://powershell.com/cs/blogs/windows-powershell-team/archive/tags/Proxy/default.aspx">Proxy</category></item><item><title>Get-NonWorkingDevices.ps1</title><link>http://powershell.com/cs/blogs/powershell-scripts/archive/2009/01/04/get-nonworkingdevices-ps1.aspx</link><pubDate>Sun, 04 Jan 2009 15:36:00 GMT</pubDate><guid isPermaLink="false">f421715f-7aba-45f0-8a8d-44de5318a3a7:785</guid><dc:creator>PowerShell Scripts</dc:creator><slash:comments>0</slash:comments><description>&amp;lt; # &amp;#160; .SYNOPSIS&amp;#160; &amp;#160;&amp;#160;&amp;#160; Uses Win32_PNPEntity to return information about non-working devices. .DESCRIPTION&amp;#160; &amp;#160;&amp;#160;&amp;#160; This script calls Get-WmiObject to retrieve plug and play details,&amp;#160;&amp;#160; &amp;#160;&amp;#160;&amp;#160; then formats and displays non-working devices. The script also has to&amp;#160; &amp;#160;&amp;#160;&amp;#160; work around how WMI returns 0 and 1 object (i.e. no Read More......(&lt;a href="http://powershell.com/cs/blogs/powershell-scripts/archive/2009/01/04/get-nonworkingdevices-ps1.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://powershell.com/cs/aggbug.aspx?PostID=785" width="1" height="1"&gt;</description><category domain="http://powershell.com/cs/blogs/powershell-scripts/archive/tags/PowerShell+Scripts/default.aspx">PowerShell Scripts</category><category domain="http://powershell.com/cs/blogs/powershell-scripts/archive/tags/PowerShell/default.aspx">PowerShell</category><category domain="http://powershell.com/cs/blogs/powershell-scripts/archive/tags/PowerShell+script/default.aspx">PowerShell script</category><category domain="http://powershell.com/cs/blogs/powershell-scripts/archive/tags/wmi/default.aspx">wmi</category><category domain="http://powershell.com/cs/blogs/powershell-scripts/archive/tags/WIn32_5F00_PointingDevice/default.aspx">WIn32_PointingDevice</category><category domain="http://powershell.com/cs/blogs/powershell-scripts/archive/tags/Win32_5F00_PNPEntity/default.aspx">Win32_PNPEntity</category></item><item><title>Modules in PowerShell V2</title><link>http://powershell.com/cs/blogs/under-the-stairs/archive/2009/01/04/modules-in-powershell-v2.aspx</link><pubDate>Sun, 04 Jan 2009 10:51:00 GMT</pubDate><guid isPermaLink="false">f421715f-7aba-45f0-8a8d-44de5318a3a7:784</guid><dc:creator>Under The Stairs</dc:creator><slash:comments>0</slash:comments><description>Introduction As PowerShell has evolved, there are a number of things that have been needed to be added in order to make it truly enterprise ready. One of the key concepts added into Version 2 of PowerShell is that of a module. A module is some chunk of Read More......(&lt;a href="http://powershell.com/cs/blogs/under-the-stairs/archive/2009/01/04/modules-in-powershell-v2.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://powershell.com/cs/aggbug.aspx?PostID=784" width="1" height="1"&gt;</description><category domain="http://powershell.com/cs/blogs/under-the-stairs/archive/tags/PowerShell/default.aspx">PowerShell</category><category domain="http://powershell.com/cs/blogs/under-the-stairs/archive/tags/CTP3/default.aspx">CTP3</category><category domain="http://powershell.com/cs/blogs/under-the-stairs/archive/tags/V2/default.aspx">V2</category><category domain="http://powershell.com/cs/blogs/under-the-stairs/archive/tags/Modules/default.aspx">Modules</category></item><item><title>Programming PowerShell_ISE</title><link>http://powershell.com/cs/blogs/windows-powershell-team/archive/2009/01/03/programming-powershell-ise.aspx</link><pubDate>Sun, 04 Jan 2009 05:54:26 GMT</pubDate><guid isPermaLink="false">f421715f-7aba-45f0-8a8d-44de5318a3a7:783</guid><dc:creator>Windows PowerShell Blog</dc:creator><slash:comments>0</slash:comments><description>I recently wrote a blog Powershell_Ise Can Do a Lot More Than You Think where I described the ability to program it to do new stuff.&amp;#160; Karl Prosser has picked up the baton and written some cool scripts programming the PowerShell_ISE to make it do some of the features that he had put into his amazing PowerShell Analyzer.&amp;#160; I encourage you to read his blog and study his code so you get a feel Read More......(&lt;a href="http://powershell.com/cs/blogs/windows-powershell-team/archive/2009/01/03/programming-powershell-ise.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://powershell.com/cs/aggbug.aspx?PostID=783" width="1" height="1"&gt;</description></item><item><title>Diagnosing Here-Strings With PowerShell_ISE</title><link>http://powershell.com/cs/blogs/windows-powershell-team/archive/2009/01/03/diagnosing-here-strings-with-powershell-ise.aspx</link><pubDate>Sun, 04 Jan 2009 00:25:07 GMT</pubDate><guid isPermaLink="false">f421715f-7aba-45f0-8a8d-44de5318a3a7:782</guid><dc:creator>Windows PowerShell Blog</dc:creator><slash:comments>0</slash:comments><description>James Brundage posted a blog entry How To Write a Console Application in PowerShell with Add-Type which used a here-string.&amp;#160;&amp;#160; One user (lcr) copied and pasted the text and got the following error: Unrecognized token in source text. At line:1 char:72 + Add-Type -OutputType ConsoleApplication -OutputAssembly HelloWorld.exe&amp;#160; &amp;lt; &amp;lt;&amp;lt;&amp;lt; @&amp;quot; &amp;#160;&amp;#160;&amp;#160; + CategoryInfo&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160; Read More......(&lt;a href="http://powershell.com/cs/blogs/windows-powershell-team/archive/2009/01/03/diagnosing-here-strings-with-powershell-ise.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://powershell.com/cs/aggbug.aspx?PostID=782" width="1" height="1"&gt;</description><category domain="http://powershell.com/cs/blogs/windows-powershell-team/archive/tags/PowerShell+V2/default.aspx">PowerShell V2</category><category domain="http://powershell.com/cs/blogs/windows-powershell-team/archive/tags/CTP3/default.aspx">CTP3</category><category domain="http://powershell.com/cs/blogs/windows-powershell-team/archive/tags/Jeffrey+Snover/default.aspx">Jeffrey Snover</category><category domain="http://powershell.com/cs/blogs/windows-powershell-team/archive/tags/PowerShell+ISE/default.aspx">PowerShell ISE</category></item><item><title>Get-MouseDetails.ps1</title><link>http://powershell.com/cs/blogs/powershell-scripts/archive/2009/01/03/get-mousedetails-ps1.aspx</link><pubDate>Sat, 03 Jan 2009 14:02:00 GMT</pubDate><guid isPermaLink="false">f421715f-7aba-45f0-8a8d-44de5318a3a7:781</guid><dc:creator>PowerShell Scripts</dc:creator><slash:comments>0</slash:comments><description>&amp;lt; # &amp;#160; .SYNOPSIS&amp;#160; &amp;#160;&amp;#160;&amp;#160; Used Win32_PointingDevice WMI class to return Mouse details&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160; .DESCRIPTION&amp;#160; &amp;#160;&amp;#160;&amp;#160; This script first defines some functions to decode various&amp;#160;&amp;#160; &amp;#160;&amp;#160;&amp;#160; WMI attributed from binary to text. Then the script calls&amp;#160;&amp;#160; &amp;#160;&amp;#160;&amp;#160; Get-WmiObject to retreive Mouse details, then Read More......(&lt;a href="http://powershell.com/cs/blogs/powershell-scripts/archive/2009/01/03/get-mousedetails-ps1.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://powershell.com/cs/aggbug.aspx?PostID=781" width="1" height="1"&gt;</description><category domain="http://powershell.com/cs/blogs/powershell-scripts/archive/tags/PowerShell+Scripts/default.aspx">PowerShell Scripts</category><category domain="http://powershell.com/cs/blogs/powershell-scripts/archive/tags/PowerShell/default.aspx">PowerShell</category><category domain="http://powershell.com/cs/blogs/powershell-scripts/archive/tags/scripts/default.aspx">scripts</category><category domain="http://powershell.com/cs/blogs/powershell-scripts/archive/tags/PowerShell+V2/default.aspx">PowerShell V2</category><category domain="http://powershell.com/cs/blogs/powershell-scripts/archive/tags/wmi/default.aspx">wmi</category><category domain="http://powershell.com/cs/blogs/powershell-scripts/archive/tags/WIn32_5F00_PointingDevice/default.aspx">WIn32_PointingDevice</category></item><item><title>Parameter Attributes in PowerShell V2 CTP Advanced Functions</title><link>http://powershell.com/cs/blogs/under-the-stairs/archive/2009/01/03/parameter-attributes-in-powershell-v2-ctp-advanced-functions.aspx</link><pubDate>Sat, 03 Jan 2009 11:06:00 GMT</pubDate><guid isPermaLink="false">f421715f-7aba-45f0-8a8d-44de5318a3a7:780</guid><dc:creator>Under The Stairs</dc:creator><slash:comments>0</slash:comments><description>In PowerShell V2 CTP3, you can create Advanced Functions which are, in effect, cmdlets written in script. I’ve already blogged about some of the cool features, particularly AutoHelp , which I find utterly cool! One neat aspect is the ability to define Read More......(&lt;a href="http://powershell.com/cs/blogs/under-the-stairs/archive/2009/01/03/parameter-attributes-in-powershell-v2-ctp-advanced-functions.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://powershell.com/cs/aggbug.aspx?PostID=780" width="1" height="1"&gt;</description><category domain="http://powershell.com/cs/blogs/under-the-stairs/archive/tags/PowerShell/default.aspx">PowerShell</category><category domain="http://powershell.com/cs/blogs/under-the-stairs/archive/tags/PowerShell+V2/default.aspx">PowerShell V2</category><category domain="http://powershell.com/cs/blogs/under-the-stairs/archive/tags/cmdlet/default.aspx">cmdlet</category><category domain="http://powershell.com/cs/blogs/under-the-stairs/archive/tags/PowersShell/default.aspx">PowersShell</category><category domain="http://powershell.com/cs/blogs/under-the-stairs/archive/tags/Attribute/default.aspx">Attribute</category><category domain="http://powershell.com/cs/blogs/under-the-stairs/archive/tags/Advanced+Function/default.aspx">Advanced Function</category></item><item><title>How To Write a Console Application in PowerShell with Add-Type</title><link>http://powershell.com/cs/blogs/windows-powershell-team/archive/2009/01/02/how-to-write-a-console-application-in-powershell-with-add-type.aspx</link><pubDate>Sat, 03 Jan 2009 00:26:56 GMT</pubDate><guid isPermaLink="false">f421715f-7aba-45f0-8a8d-44de5318a3a7:779</guid><dc:creator>Windows PowerShell Blog</dc:creator><slash:comments>0</slash:comments><description>Windows PowerShell CTP3 has a lot of very cool things.&amp;#160; CTP2 introduced the Add-Type cmdlet, which allowed you to dynamically compile C# in PowerShell.&amp;#160; It was actually possible to use the CompilerParameters to Add-Type to make a console application, but it wasn&amp;#39;t particularly easy.&amp;#160; In CTP3, we&amp;#39;ve made this a lot easier to do. There&amp;#39;s now an -OutputType parameter for Add Read More......(&lt;a href="http://powershell.com/cs/blogs/windows-powershell-team/archive/2009/01/02/how-to-write-a-console-application-in-powershell-with-add-type.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://powershell.com/cs/aggbug.aspx?PostID=779" width="1" height="1"&gt;</description><category domain="http://powershell.com/cs/blogs/windows-powershell-team/archive/tags/CTP3/default.aspx">CTP3</category><category domain="http://powershell.com/cs/blogs/windows-powershell-team/archive/tags/HowTo/default.aspx">HowTo</category><category domain="http://powershell.com/cs/blogs/windows-powershell-team/archive/tags/Add-Type/default.aspx">Add-Type</category></item><item><title>Get-Verb</title><link>http://powershell.com/cs/blogs/windows-powershell-team/archive/2009/01/02/get-verb.aspx</link><pubDate>Fri, 02 Jan 2009 21:35:02 GMT</pubDate><guid isPermaLink="false">f421715f-7aba-45f0-8a8d-44de5318a3a7:776</guid><dc:creator>Windows PowerShell Blog</dc:creator><slash:comments>0</slash:comments><description>When I write a PowerShell function, I try to ensure that it follows the PowerShell standard verbs. These verbs actually exist as static properties in a few different types in PowerShell, so I thought I&amp;#39;d make a quick advanced function so I can get all of the Verbs. Check it out: Get-Verb Synopsis: Gets the standard PowerShell verbs Syntax: Get-Verb [[-verb] [&amp;lt;String[]&amp;gt;]] [-Verbose] [-Debug Read More......(&lt;a href="http://powershell.com/cs/blogs/windows-powershell-team/archive/2009/01/02/get-verb.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://powershell.com/cs/aggbug.aspx?PostID=776" width="1" height="1"&gt;</description><category domain="http://powershell.com/cs/blogs/windows-powershell-team/archive/tags/Get-Verb/default.aspx">Get-Verb</category></item><item><title>How and Why to Use Splatting (passing [switch] parameters)</title><link>http://powershell.com/cs/blogs/windows-powershell-team/archive/2009/01/02/how-and-why-to-use-splatting-passing-switch-parameters.aspx</link><pubDate>Fri, 02 Jan 2009 21:03:37 GMT</pubDate><guid isPermaLink="false">f421715f-7aba-45f0-8a8d-44de5318a3a7:777</guid><dc:creator>Windows PowerShell Blog</dc:creator><slash:comments>0</slash:comments><description>On our internal discussion list, someone just asked about how to pass switch parameters from one function to another.&amp;#160; This person asked this as &amp;quot;Why can&amp;#39;t [switch] parameters be passed as parameters?&amp;quot;. My short answer was simple: &amp;quot;They Can Be&amp;quot; Answering this question is a great way to illustrate the value of a PowerShell V2 feature called Splatting.&amp;#160; Splatting is Read More......(&lt;a href="http://powershell.com/cs/blogs/windows-powershell-team/archive/2009/01/02/how-and-why-to-use-splatting-passing-switch-parameters.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://powershell.com/cs/aggbug.aspx?PostID=777" width="1" height="1"&gt;</description><category domain="http://powershell.com/cs/blogs/windows-powershell-team/archive/tags/_5B00_switch_5D00_/default.aspx">[switch]</category><category domain="http://powershell.com/cs/blogs/windows-powershell-team/archive/tags/Splatting/default.aspx">Splatting</category></item><item><title>A Module to Create Modules and Advanced Functions</title><link>http://powershell.com/cs/blogs/windows-powershell-team/archive/2009/01/02/a-module-to-create-modules-and-advanced-functions.aspx</link><pubDate>Fri, 02 Jan 2009 17:46:00 GMT</pubDate><guid isPermaLink="false">f421715f-7aba-45f0-8a8d-44de5318a3a7:778</guid><dc:creator>Windows PowerShell Blog</dc:creator><slash:comments>0</slash:comments><description>It is hard to overstate how important Modules and Advanced Functions are. If you are a PowerShell user - you need to take the time to learn these new mechanisms and use them as your first choice in implementing new functions. The reason for this is that these mechanisms are critical technologies to support SHARING. Advanced Functions provide help, parameter tab-completion, and cmdlet semantics that Read More......(&lt;a href="http://powershell.com/cs/blogs/windows-powershell-team/archive/2009/01/02/a-module-to-create-modules-and-advanced-functions.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://powershell.com/cs/aggbug.aspx?PostID=778" width="1" height="1"&gt;</description><category domain="http://powershell.com/cs/blogs/windows-powershell-team/archive/tags/CTP3/default.aspx">CTP3</category><category domain="http://powershell.com/cs/blogs/windows-powershell-team/archive/tags/Advanced+Functions/default.aspx">Advanced Functions</category><category domain="http://powershell.com/cs/blogs/windows-powershell-team/archive/tags/Module/default.aspx">Module</category><category domain="http://powershell.com/cs/blogs/windows-powershell-team/archive/tags/Jeffrey+Snover/default.aspx">Jeffrey Snover</category></item><item><title>Get-DateTime.ps1</title><link>http://powershell.com/cs/blogs/powershell-scripts/archive/2009/01/02/get-datetime-ps1.aspx</link><pubDate>Fri, 02 Jan 2009 16:45:00 GMT</pubDate><guid isPermaLink="false">f421715f-7aba-45f0-8a8d-44de5318a3a7:774</guid><dc:creator>PowerShell Scripts</dc:creator><slash:comments>0</slash:comments><description>&amp;lt; # &amp;#160; .SYNOPSIS&amp;#160; &amp;#160; Uses .NET formatting strings to format date/time values&amp;#160;&amp;#160;&amp;#160; .DESCRIPTION&amp;#160; &amp;#160; Recreates an MSDN sample for displaying Date/TIme Format. See&amp;#160; &amp;#160; links section for pointer to original Sample.&amp;#160; .NOTES&amp;#160; &amp;#160;&amp;#160;&amp;#160; File Name&amp;#160; : Get-DateTime.ps1&amp;#160; &amp;#160;&amp;#160;&amp;#160; Author&amp;#160;&amp;#160;&amp;#160;&amp;#160; : Thomas Lee Read More......(&lt;a href="http://powershell.com/cs/blogs/powershell-scripts/archive/2009/01/02/get-datetime-ps1.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://powershell.com/cs/aggbug.aspx?PostID=774" width="1" height="1"&gt;</description><category domain="http://powershell.com/cs/blogs/powershell-scripts/archive/tags/PowerShell+Scripts/default.aspx">PowerShell Scripts</category><category domain="http://powershell.com/cs/blogs/powershell-scripts/archive/tags/PowerShell/default.aspx">PowerShell</category><category domain="http://powershell.com/cs/blogs/powershell-scripts/archive/tags/scripts/default.aspx">scripts</category><category domain="http://powershell.com/cs/blogs/powershell-scripts/archive/tags/PowerShell+V2/default.aspx">PowerShell V2</category><category domain="http://powershell.com/cs/blogs/powershell-scripts/archive/tags/Script/default.aspx">Script</category><category domain="http://powershell.com/cs/blogs/powershell-scripts/archive/tags/formatting/default.aspx">formatting</category><category domain="http://powershell.com/cs/blogs/powershell-scripts/archive/tags/string+formating/default.aspx">string formating</category><category domain="http://powershell.com/cs/blogs/powershell-scripts/archive/tags/System.DateTime/default.aspx">System.DateTime</category></item><item><title>Posting PowerShell Scripts – one solution</title><link>http://powershell.com/cs/blogs/under-the-stairs/archive/2009/01/02/posting-powershell-scripts-one-solution.aspx</link><pubDate>Fri, 02 Jan 2009 11:15:00 GMT</pubDate><guid isPermaLink="false">f421715f-7aba-45f0-8a8d-44de5318a3a7:772</guid><dc:creator>Under The Stairs</dc:creator><slash:comments>0</slash:comments><description>On my PowerShell Scripts blog , I publish daily, or near daily, PowerShell scripts. I am slowly decorating the MSDN on-line library with PowerShell samples. I am also playing with the latest version of PowerShell V2 (aka CTP3) and the new auto-help feature Read More......(&lt;a href="http://powershell.com/cs/blogs/under-the-stairs/archive/2009/01/02/posting-powershell-scripts-one-solution.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://powershell.com/cs/aggbug.aspx?PostID=772" width="1" height="1"&gt;</description><category domain="http://powershell.com/cs/blogs/under-the-stairs/archive/tags/PowerShell/default.aspx">PowerShell</category><category domain="http://powershell.com/cs/blogs/under-the-stairs/archive/tags/scripts/default.aspx">scripts</category><category domain="http://powershell.com/cs/blogs/under-the-stairs/archive/tags/script/default.aspx">script</category><category domain="http://powershell.com/cs/blogs/under-the-stairs/archive/tags/PowerShell+scripts/default.aspx">PowerShell scripts</category></item><item><title>Happy New Year !</title><link>http://powershell.com/cs/blogs/the-powershell-guy/archive/2009/01/01/happy-new-year.aspx</link><pubDate>Thu, 01 Jan 2009 21:39:00 GMT</pubDate><guid isPermaLink="false">f421715f-7aba-45f0-8a8d-44de5318a3a7:770</guid><dc:creator>The PowerShell Guy</dc:creator><slash:comments>0</slash:comments><description>I’m very happy and proud that I received a e-mail from Microsoft that I got my 4th MVP Award, and may call myself a PowerShell MVP for another year, an excellent start for me ;-). Dear Marc van Orsouw, Congratulations! We are pleased to present you with the 2009 Microsoft® MVP Award! This award is given to exceptional technical community leaders who actively share their high quality, real world expertise Read More......(&lt;a href="http://powershell.com/cs/blogs/the-powershell-guy/archive/2009/01/01/happy-new-year.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://powershell.com/cs/aggbug.aspx?PostID=770" width="1" height="1"&gt;</description><category domain="http://powershell.com/cs/blogs/the-powershell-guy/archive/tags/PowerShell/default.aspx">PowerShell</category><category domain="http://powershell.com/cs/blogs/the-powershell-guy/archive/tags/MVP/default.aspx">MVP</category></item></channel></rss>