http://powershell.com/cs/blogs/tips/atom.aspxCommunity Server2013-05-02T06:00:00Z/cs/blogs/tips/archive/2013/05/22/shortening-parameter-arguments-in-powershell-3-0.aspx2013-05-22T11:00:00Z2013-05-22T11:00:00Z<p>In PowerShell 3.0, when a parameter expects a fixed list of values, you do not need to write the complete argument. It is OK to write just as much as is needed to uniquely identify the argument:</p> <pre><span style="color:#5f9ea0;">Write-Host</span><span style="color:#000000;"> </span><span style="color:#800000;">&#39;</span><span style="color:#800000;">This is a colorful message</span><span style="color:#800000;">&#39;</span><span style="color:#000000;"> </span><span style="color:#5f9ea0;">-ForegroundColor</span><span style="color:#000000;"> </span><span style="color:#0000ff;">r</span><span style="color:#000000;"> </span><span style="color:#5f9ea0;">-BackgroundColor</span><span style="color:#000000;"> </span><span style="color:#0000ff;">y</span> </pre> <p>This produces a red text on yellow background.</p> <p>Using shortcuts like this isn&#39;t very useful, though, because at the same time PowerShell 3.0 introduces argument completion. So after you typed &quot;r&quot; as argument to -ForegroundColor, simply press TAB to make PowerShell complete the argument. This is just as quick and produces much better code:</p> <pre><span style="color:#5f9ea0;">Write-Host</span><span style="color:#000000;"> </span><span style="color:#800000;">&#39;</span><span style="color:#800000;">This is a colorful message</span><span style="color:#800000;">&#39;</span><span style="color:#000000;"> </span><span style="color:#5f9ea0;">-ForegroundColor</span><span style="color:#000000;"> </span><span style="color:#0000ff;">Red</span><span style="color:#000000;"> </span><span style="color:#5f9ea0;">-BackgroundColor</span><span style="color:#000000;"> </span><span style="color:#0000ff;">Yellow</span> </pre> <p><a target="twitter" href="http://twitter.com/home/?status=RT+%40PowerTip+%20Shortening%20Parameter%20Arguments%20in%20PowerShell%203.0%20with%20%23PowerShell+http://bit.ly/125Pg0U"><img src="http://powershell.com/cs/Themes/powershell/images/ps/twitter_32x32.png" alt="Twitter This Tip!" style="vertical-align:middle;border:0px;" /></a> <a target="twitter" href="http://twitter.com/home/?status=RT+%40%20Shortening%20Parameter%20Arguments%20in%20PowerShell%203.0%20with%20%23PowerShell+http://bit.ly/125Pg0U">ReTweet this Tip!</a></p><div style="clear:both;"></div><img src="http://powershell.com/cs/aggbug.aspx?PostID=23073" width="1" height="1">powershelltipshttp://powershell.com/cs/members/powershelltips/default.aspx/cs/blogs/tips/archive/2013/05/21/resolving-urls.aspx2013-05-21T11:00:00Z2013-05-21T11:00:00Z<p>Sometimes you may stumble across URLs like this one:</p> <p>http://go.microsoft.com/fwlink/?LinkID=13517</p> <p>As it turns out, these are just &quot;pointers&quot; to the real web address. In PowerShell 3.0, the new cmdlet Invoke-WebRequest can resolve these URLs and return the real address that it points to:</p> <pre><span style="color:#800080;">$URLRaw</span><span style="color:#000000;"> </span><span style="color:#ff0000;">=</span><span style="color:#000000;"> </span><span style="color:#800000;">&#39;</span><span style="color:#800000;">http://go.microsoft.com/fwlink/?LinkID=135173</span><span style="color:#800000;">&#39;</span><span style="color:#000000;"> (</span><span style="color:#5f9ea0;">Invoke-WebRequest</span><span style="color:#000000;"> </span><span style="color:#5f9ea0;">-Uri</span><span style="color:#000000;"> </span><span style="color:#800080;">$URLRaw</span><span style="color:#000000;"> </span><span style="color:#5f9ea0;">-MaximumRedirection</span><span style="color:#000000;"> </span><span style="color:#000000;">0</span><span style="color:#000000;"> </span><span style="color:#5f9ea0;">-ErrorAction</span><span style="color:#000000;"> </span><span style="color:#0000ff;">Ignore</span><span style="color:#000000;">)</span><span style="color:#000000;">.</span><span style="color:#8b4513;">Headers</span><span style="color:#000000;">.</span><span style="color:#8b4513;">Location</span> </pre> <p><a target="twitter" href="http://twitter.com/home/?status=RT+%40PowerTip+%20Resolving%20URLs%20with%20%23PowerShell+http://bit.ly/Yd3XUb"><img src="http://powershell.com/cs/Themes/powershell/images/ps/twitter_32x32.png" alt="Twitter This Tip!" style="vertical-align:middle;border:0px;" /></a> <a target="twitter" href="http://twitter.com/home/?status=RT+%40%20Resolving%20URLs%20with%20%23PowerShell+http://bit.ly/Yd3XUb">ReTweet this Tip!</a></p><div style="clear:both;"></div><img src="http://powershell.com/cs/aggbug.aspx?PostID=23072" width="1" height="1">powershelltipshttp://powershell.com/cs/members/powershelltips/default.aspx/cs/blogs/tips/archive/2013/05/20/validating-active-directory-user-account-and-password.aspx2013-05-20T11:00:00Z2013-05-20T11:00:00Z<p>Ever wanted to check whether a given user account and password was correct? Here is a little function that can help you:</p> <pre><span style="color:#0000ff;">function</span><span style="color:#000000;"> </span><span style="color:#5f9ea0;">Test-ADCredential</span><span style="color:#000000;"> { </span><span style="color:#0000ff;">param</span><span style="color:#000000;">( [</span><span style="color:#8b4513;">System.Management.Automation.Credential</span><span style="color:#000000;">()] </span><span style="color:#800080;">$Credential</span><span style="color:#000000;"> ) </span><span style="color:#5f9ea0;">Add-Type</span><span style="color:#000000;"> </span><span style="color:#5f9ea0;">-AssemblyName</span><span style="color:#000000;"> </span><span style="color:#8b4513;">System.DirectoryServices.AccountManagement</span><span style="color:#000000;"> </span><span style="color:#800080;">$info</span><span style="color:#000000;"> </span><span style="color:#ff0000;">=</span><span style="color:#000000;"> </span><span style="color:#800080;">$Credential</span><span style="color:#000000;">.</span><span style="color:#8b4513;">GetNetworkCredential</span><span style="color:#000000;">() </span><span style="color:#0000ff;">if</span><span style="color:#000000;"> (</span><span style="color:#800080;">$info</span><span style="color:#000000;">.</span><span style="color:#8b4513;">Domain</span><span style="color:#000000;"> </span><span style="color:#ff0000;">-eq</span><span style="color:#000000;"> </span><span style="color:#800000;">&#39;&#39;</span><span style="color:#000000;">) { </span><span style="color:#800080;">$info</span><span style="color:#000000;">.</span><span style="color:#8b4513;">Domain</span><span style="color:#000000;"> </span><span style="color:#ff0000;">=</span><span style="color:#000000;"> </span><span style="color:#800080;">$env:USERDOMAIN</span><span style="color:#000000;"> } </span><span style="color:#800080;">$TypeDomain</span><span style="color:#000000;"> </span><span style="color:#ff0000;">=</span><span style="color:#000000;"> [</span><span style="color:#8b4513;">System.DirectoryServices.AccountManagement.ContextType</span><span style="color:#000000;">]</span><span style="color:#000000;">::</span><span style="color:#8b4513;">Domain</span><span style="color:#000000;"> </span><span style="color:#0000ff;">try</span><span style="color:#000000;"> { </span><span style="color:#800080;">$pc</span><span style="color:#000000;"> </span><span style="color:#ff0000;">=</span><span style="color:#000000;"> </span><span style="color:#5f9ea0;">New-Object</span><span style="color:#000000;"> </span><span style="color:#8b4513;">System.DirectoryServices.AccountManagement.PrincipalContext</span><span style="color:#000000;"> </span><span style="color:#800080;">$TypeDomain</span><span style="color:#000000;">,</span><span style="color:#800080;">$info</span><span style="color:#000000;">.</span><span style="color:#8b4513;">Domain</span><span style="color:#000000;"> </span><span style="color:#800080;">$pc</span><span style="color:#000000;">.</span><span style="color:#8b4513;">ValidateCredentials</span><span style="color:#000000;">(</span><span style="color:#800080;">$info</span><span style="color:#000000;">.</span><span style="color:#8b4513;">UserName</span><span style="color:#000000;">,</span><span style="color:#800080;">$info</span><span style="color:#000000;">.</span><span style="color:#8b4513;">Password</span><span style="color:#000000;">) } </span><span style="color:#0000ff;">catch</span><span style="color:#000000;"> { </span><span style="color:#5f9ea0;">Write-Warning</span><span style="color:#000000;"> </span><span style="color:#800000;">&quot;Unable to contact domain &#39;$($info.Domain)&#39;. Original error:$_&quot;</span><span style="color:#000000;"> } }</span> </pre> <p>Simply submit a credential object or a string in the format &quot;domain\username&quot;.</p> <p><a target="twitter" href="http://twitter.com/home/?status=RT+%40PowerTip+%20Validating%20Active%20Directory%20User%20Account%20and%20Password%20with%20%23PowerShell+http://bit.ly/187MoDY"><img src="http://powershell.com/cs/Themes/powershell/images/ps/twitter_32x32.png" alt="Twitter This Tip!" style="vertical-align:middle;border:0px;" /></a> <a target="twitter" href="http://twitter.com/home/?status=RT+%40%20Validating%20Active%20Directory%20User%20Account%20and%20Password%20with%20%23PowerShell+http://bit.ly/187MoDY">ReTweet this Tip!</a></p><div style="clear:both;"></div><img src="http://powershell.com/cs/aggbug.aspx?PostID=23071" width="1" height="1">powershelltipshttp://powershell.com/cs/members/powershelltips/default.aspx/cs/blogs/tips/archive/2013/05/17/working-with-timespan-objects.aspx2013-05-17T11:00:00Z2013-05-17T11:00:00Z<p>TimeSpan objects represent a given amount of time. They are incredibly useful when you calculate with dates or times because they can represent the amount of time between two dates, or can add a day (or a minute) to a date to create relative dates.</p> <p>Here are some samples to get you started:</p> <pre><span style="color:#008000;"># get a timespan representing one day and 3 hours: </span><span style="color:#5f9ea0;">New-TimeSpan</span><span style="color:#000000;"> </span><span style="color:#5f9ea0;">-Days</span><span style="color:#000000;"> </span><span style="color:#000000;">1</span><span style="color:#000000;"> </span><span style="color:#5f9ea0;">-Hours</span><span style="color:#000000;"> </span><span style="color:#000000;">3</span><span style="color:#000000;"> </span><span style="color:#008000;"># get a timespan representing the time difference between now and next Christmas </span><span style="color:#5f9ea0;">New-Timespan</span><span style="color:#000000;"> </span><span style="color:#5f9ea0;">-End</span><span style="color:#000000;"> </span><span style="color:#800000;">&#39;</span><span style="color:#800000;">2013-12-24 18:30:00</span><span style="color:#800000;">&#39;</span><span style="color:#000000;"> </span><span style="color:#008000;"># get a timespan by subtracting two dates: </span><span style="color:#000000;">[</span><span style="color:#0000ff;">DateTime</span><span style="color:#000000;">]</span><span style="color:#800000;">&#39;</span><span style="color:#800000;">2013-12-24 18:30:00</span><span style="color:#800000;">&#39;</span><span style="color:#000000;"> </span><span style="color:#5f9ea0;">-</span><span style="color:#000000;"> (</span><span style="color:#5f9ea0;">Get-Date</span><span style="color:#000000;">) </span><span style="color:#008000;"># get a timespan by subtracting a timespan representing one day from a date: </span><span style="color:#000000;">(</span><span style="color:#5f9ea0;">Get-Date</span><span style="color:#000000;">) </span><span style="color:#5f9ea0;">-</span><span style="color:#000000;"> [</span><span style="color:#0000ff;">TimeSpan</span><span style="color:#000000;">]</span><span style="color:#800000;">&#39;</span><span style="color:#800000;">1.00:00:00</span><span style="color:#800000;">&#39;</span><span style="color:#000000;"> </span><span style="color:#008000;"># getting a specific property from a timespan (for example just the days): </span><span style="color:#800080;">$days</span><span style="color:#000000;"> </span><span style="color:#ff0000;">=</span><span style="color:#000000;"> (</span><span style="color:#5f9ea0;">New-Timespan</span><span style="color:#000000;"> </span><span style="color:#5f9ea0;">-End</span><span style="color:#000000;"> </span><span style="color:#800000;">&#39;</span><span style="color:#800000;">2013-12-24 18:30:00</span><span style="color:#800000;">&#39;</span><span style="color:#000000;">)</span><span style="color:#000000;">.</span><span style="color:#8b4513;">Days</span><span style="color:#000000;"> </span><span style="color:#800000;">&quot;Days to Christmas: $days&quot;</span><span style="color:#000000;"> </span><span style="color:#008000;"># negating a timespan: </span><span style="color:#800080;">$timespan</span><span style="color:#000000;"> </span><span style="color:#ff0000;">=</span><span style="color:#000000;"> </span><span style="color:#5f9ea0;">New-TimeSpan</span><span style="color:#000000;"> </span><span style="color:#5f9ea0;">-Days</span><span style="color:#000000;"> </span><span style="color:#000000;">1</span><span style="color:#000000;"> </span><span style="color:#800080;">$timespan</span><span style="color:#000000;">.</span><span style="color:#8b4513;">Negate</span><span style="color:#000000;">() </span><span style="color:#800080;">$timespan</span><span style="color:#000000;"> </span><span style="color:#008000;"># creating a negative timespan directly: </span><span style="color:#5f9ea0;">New-TimeSpan</span><span style="color:#000000;"> </span><span style="color:#5f9ea0;">-Days</span><span style="color:#000000;"> </span><span style="color:#5f9ea0;">-1</span> </pre> <p><a target="twitter" href="http://twitter.com/home/?status=RT+%40PowerTip+%20Working%20With%20TimeSpan%20Objects%20with%20%23PowerShell+http://bit.ly/ZUFkHe"><img src="http://powershell.com/cs/Themes/powershell/images/ps/twitter_32x32.png" alt="Twitter This Tip!" style="vertical-align:middle;border:0px;" /></a> <a target="twitter" href="http://twitter.com/home/?status=RT+%40%20Working%20With%20TimeSpan%20Objects%20with%20%23PowerShell+http://bit.ly/ZUFkHe">ReTweet this Tip!</a></p><div style="clear:both;"></div><img src="http://powershell.com/cs/aggbug.aspx?PostID=23070" width="1" height="1">powershelltipshttp://powershell.com/cs/members/powershelltips/default.aspx/cs/blogs/tips/archive/2013/05/16/converting-low-level-error-numbers-into-help-messages.aspx2013-05-16T11:00:00Z2013-05-16T11:00:00Z<p>Sometimes, native commands such as net.exe return cryptic error numbers instead of full error messages. Traditionally, you could use the following command to convert these error numbers into full messages:</p> <pre><span style="color:#0000ff;">PS</span><span style="color:#000000;">&gt;</span><span style="color:#000000;"> </span><span style="color:#0000ff;">net</span><span style="color:#000000;"> </span><span style="color:#0000ff;">helpmsg</span><span style="color:#000000;"> </span><span style="color:#000000;">3534</span><span style="color:#000000;"> </span><span style="color:#0000ff;">The</span><span style="color:#000000;"> </span><span style="color:#0000ff;">service</span><span style="color:#000000;"> </span><span style="color:#0000ff;">did</span><span style="color:#000000;"> </span><span style="color:#0000ff;">not</span><span style="color:#000000;"> </span><span style="color:#0000ff;">report</span><span style="color:#000000;"> </span><span style="color:#0000ff;">an</span><span style="color:#000000;"> </span><span style="color:#0000ff;">error</span><span style="color:#000000;">.</span><span style="color:#000000;"> </span><span style="color:#0000ff;">PS</span><span style="color:#000000;">&gt;</span><span style="color:#000000;"> </span><span style="color:#0000ff;">net</span><span style="color:#000000;"> </span><span style="color:#0000ff;">helpmsg</span><span style="color:#000000;"> </span><span style="color:#000000;">1</span><span style="color:#000000;"> </span><span style="color:#0000ff;">Incorrect</span><span style="color:#000000;"> </span><span style="color:#0000ff;">function</span><span style="color:#000000;">.</span><span style="color:#000000;"> </span><span style="color:#0000ff;">PS</span><span style="color:#000000;">&gt;</span><span style="color:#000000;"> </span><span style="color:#0000ff;">net</span><span style="color:#000000;"> </span><span style="color:#0000ff;">helpmsg</span><span style="color:#000000;"> </span><span style="color:#000000;">4323</span><span style="color:#000000;"> </span><span style="color:#0000ff;">The</span><span style="color:#000000;"> </span><span style="color:#0000ff;">transport</span><span style="color:#000000;"> </span><span style="color:#0000ff;">cannot</span><span style="color:#000000;"> </span><span style="color:#0000ff;">access</span><span style="color:#000000;"> </span><span style="color:#0000ff;">the</span><span style="color:#000000;"> </span><span style="color:#0000ff;">medium</span><span style="color:#000000;">.</span> </pre> <p>A better way may be to use winrm.exe because this command can do the very same - and more:</p> <pre><span style="color:#0000ff;">PS</span><span style="color:#000000;">&gt;</span><span style="color:#000000;"> </span><span style="color:#0000ff;">winrm</span><span style="color:#000000;"> </span><span style="color:#0000ff;">helpmsg</span><span style="color:#000000;"> </span><span style="color:#000000;">3534</span><span style="color:#000000;"> </span><span style="color:#0000ff;">The</span><span style="color:#000000;"> </span><span style="color:#0000ff;">service</span><span style="color:#000000;"> </span><span style="color:#0000ff;">did</span><span style="color:#000000;"> </span><span style="color:#0000ff;">not</span><span style="color:#000000;"> </span><span style="color:#0000ff;">report</span><span style="color:#000000;"> </span><span style="color:#0000ff;">an</span><span style="color:#000000;"> </span><span style="color:#0000ff;">error</span><span style="color:#000000;">.</span><span style="color:#000000;"> </span><span style="color:#0000ff;">PS</span><span style="color:#000000;">&gt;</span><span style="color:#000000;"> </span><span style="color:#0000ff;">winrm</span><span style="color:#000000;"> </span><span style="color:#0000ff;">helpmsg</span><span style="color:#000000;"> </span><span style="color:#000000;">1</span><span style="color:#000000;"> </span><span style="color:#0000ff;">Incorrect</span><span style="color:#000000;"> </span><span style="color:#0000ff;">function</span><span style="color:#000000;">.</span><span style="color:#000000;"> </span><span style="color:#0000ff;">PS</span><span style="color:#000000;">&gt;</span><span style="color:#000000;"> </span><span style="color:#0000ff;">winrm</span><span style="color:#000000;"> </span><span style="color:#0000ff;">helpmsg</span><span style="color:#000000;"> </span><span style="color:#000000;">4323</span><span style="color:#000000;"> </span><span style="color:#0000ff;">The</span><span style="color:#000000;"> </span><span style="color:#0000ff;">transport</span><span style="color:#000000;"> </span><span style="color:#0000ff;">cannot</span><span style="color:#000000;"> </span><span style="color:#0000ff;">access</span><span style="color:#000000;"> </span><span style="color:#0000ff;">the</span><span style="color:#000000;"> </span><span style="color:#0000ff;">medium</span><span style="color:#000000;">.</span> </pre> <p>While net.exe can only convert a certain range of error messages, winrm.exe is more flexible and can for example also convert Remoting-specific error codes:</p> <pre><span style="color:#0000ff;">PS</span><span style="color:#000000;">&gt;</span><span style="color:#000000;"> </span><span style="color:#0000ff;">winrm</span><span style="color:#000000;"> </span><span style="color:#0000ff;">helpmsg</span><span style="color:#000000;"> </span><span style="color:#000000;">0x80338104</span><span style="color:#000000;"> </span><span style="color:#0000ff;">The</span><span style="color:#000000;"> </span><span style="color:#5f9ea0;">WS-Management</span><span style="color:#000000;"> </span><span style="color:#0000ff;">service</span><span style="color:#000000;"> </span><span style="color:#0000ff;">cannot</span><span style="color:#000000;"> </span><span style="color:#0000ff;">process</span><span style="color:#000000;"> </span><span style="color:#0000ff;">the</span><span style="color:#000000;"> </span><span style="color:#0000ff;">request</span><span style="color:#000000;">.</span><span style="color:#000000;"> </span><span style="color:#0000ff;">The</span><span style="color:#000000;"> </span><span style="color:#0000ff;">WMI</span><span style="color:#000000;"> </span><span style="color:#0000ff;">service</span><span style="color:#000000;"> </span><span style="color:#0000ff;">returned</span><span style="color:#000000;"> </span><span style="color:#0000ff;">an</span><span style="color:#000000;"> </span><span style="color:#800000;">&#39;</span><span style="color:#800000;">access denied</span><span style="color:#800000;">&#39;</span><span style="color:#000000;"> </span><span style="color:#0000ff;">error</span><span style="color:#000000;">.</span><span style="color:#000000;"> </span><span style="color:#0000ff;">PS</span><span style="color:#000000;">&gt;</span><span style="color:#000000;"> </span><span style="color:#0000ff;">net</span><span style="color:#000000;"> </span><span style="color:#0000ff;">helpmsg</span><span style="color:#000000;"> </span><span style="color:#000000;">0x80338104</span><span style="color:#000000;"> </span><span style="color:#0000ff;">The</span><span style="color:#000000;"> </span><span style="color:#0000ff;">syntax</span><span style="color:#000000;"> </span><span style="color:#0000ff;">of</span><span style="color:#000000;"> </span><span style="color:#0000ff;">this</span><span style="color:#000000;"> </span><span style="color:#0000ff;">command</span><span style="color:#000000;"> </span><span style="color:#0000ff;">is</span><span style="color:#000000;">:</span><span style="color:#000000;"> </span><span style="color:#0000ff;">NET</span><span style="color:#000000;"> </span><span style="color:#0000ff;">HELPMSG</span><span style="color:#000000;"> </span><span style="color:#0000ff;">message</span><span style="color:#000000;">#</span> </pre> <p>As you see, winrm.exe returns the correct error message whereas net.exe falls back to a standard template and cannot translate the number. Winrm.exe therefore is the more generic approach that you can safely use to translate any low-level API error code to text.</p> <p><a target="twitter" href="http://twitter.com/home/?status=RT+%40PowerTip+%20Converting%20Low-Level%20Error%20Numbers%20into%20Help%20Messages%20with%20%23PowerShell+http://bit.ly/12AZV6G"><img src="http://powershell.com/cs/Themes/powershell/images/ps/twitter_32x32.png" alt="Twitter This Tip!" style="vertical-align:middle;border:0px;" /></a> <a target="twitter" href="http://twitter.com/home/?status=RT+%40%20Converting%20Low-Level%20Error%20Numbers%20into%20Help%20Messages%20with%20%23PowerShell+http://bit.ly/12AZV6G">ReTweet this Tip!</a></p><div style="clear:both;"></div><img src="http://powershell.com/cs/aggbug.aspx?PostID=23069" width="1" height="1">powershelltipshttp://powershell.com/cs/members/powershelltips/default.aspx/cs/blogs/tips/archive/2013/05/15/identifying-32-bit-executables.aspx2013-05-15T11:00:00Z2013-05-15T11:00:00Z<p>Thanks to Shay Levy from http://powershellmagazine.com for showing how to do this: here&#39;s a small function that returns the architecture an executable was compiled for:</p> <pre><span style="color:#0000ff;">function</span><span style="color:#000000;"> </span><span style="color:#5f9ea0;">Get-FileArchitecture</span><span style="color:#000000;"> { </span><span style="color:#0000ff;">param</span><span style="color:#000000;"> ( </span><span style="color:#800080;">$filePath</span><span style="color:#000000;"> </span><span style="color:#ff0000;">=</span><span style="color:#000000;"> </span><span style="color:#800000;">&quot;</span><span style="text-decoration:underline;color:#008000;">$env:windir\notepad.exe</span><span style="color:#800000;">&quot;</span><span style="color:#000000;"> ) </span><span style="color:#800080;">$Architecture</span><span style="color:#000000;"> </span><span style="color:#ff0000;">=</span><span style="color:#000000;"> </span><span style="color:#800000;">&#39;</span><span style="color:#800000;">Native,I386,Itanium,x64</span><span style="color:#800000;">&#39;</span><span style="color:#000000;">.</span><span style="color:#8b4513;">Split</span><span style="color:#000000;">(</span><span style="color:#800000;">&#39;</span><span style="color:#800000;">,</span><span style="color:#800000;">&#39;</span><span style="color:#000000;">) </span><span style="color:#800080;">$data</span><span style="color:#000000;"> </span><span style="color:#ff0000;">=</span><span style="color:#000000;"> </span><span style="color:#5f9ea0;">New-Object</span><span style="color:#000000;"> </span><span style="color:#8b4513;">System.Byte</span><span style="color:#000000;">[] </span><span style="color:#000000;">4096</span><span style="color:#000000;"> </span><span style="color:#800080;">$stream</span><span style="color:#000000;"> </span><span style="color:#ff0000;">=</span><span style="color:#000000;"> </span><span style="color:#5f9ea0;">New-Object</span><span style="color:#000000;"> </span><span style="color:#8b4513;">System.IO.FileStream</span><span style="color:#000000;"> </span><span style="color:#5f9ea0;">-ArgumentList</span><span style="color:#000000;"> </span><span style="color:#800080;">$filePath</span><span style="color:#000000;">,</span><span style="color:#0000ff;">Open</span><span style="color:#000000;">,</span><span style="color:#0000ff;">Read</span><span style="color:#000000;"> [</span><span style="color:#0000ff;">void</span><span style="color:#000000;">]</span><span style="color:#800080;">$stream</span><span style="color:#000000;">.</span><span style="color:#8b4513;">Read</span><span style="color:#000000;">(</span><span style="color:#800080;">$data</span><span style="color:#000000;">,</span><span style="color:#000000;">0</span><span style="color:#000000;">,</span><span style="color:#000000;">60</span><span style="color:#000000;">) </span><span style="color:#800080;">$PE_HEADER_ADDR</span><span style="color:#000000;"> </span><span style="color:#ff0000;">=</span><span style="color:#000000;"> [</span><span style="color:#8b4513;">System.BitConverter</span><span style="color:#000000;">]</span><span style="color:#000000;">::</span><span style="color:#8b4513;">ToInt32</span><span style="color:#000000;">(</span><span style="color:#800080;">$data</span><span style="color:#000000;">,</span><span style="color:#000000;"> </span><span style="color:#000000;">60</span><span style="color:#000000;">) </span><span style="color:#800080;">$Architecture</span><span style="color:#000000;">[[</span><span style="color:#8b4513;">System.BitConverter</span><span style="color:#000000;">]</span><span style="color:#000000;">::</span><span style="color:#8b4513;">ToUInt16</span><span style="color:#000000;">(</span><span style="color:#800080;">$data</span><span style="color:#000000;">,</span><span style="color:#000000;"> </span><span style="color:#800080;">$PE_HEADER_ADDR</span><span style="color:#000000;"> </span><span style="color:#ff0000;">+</span><span style="color:#000000;"> </span><span style="color:#000000;">4</span><span style="color:#000000;">)] }</span> </pre> <p>Simply submit a path to an exe file, and you get back the architecture it was compiled for.</p> <p>This line would dump all non-64-bit applications from your Windows folder (which you would, of course, only run on a 64-bit system):</p> <pre><span style="color:#5f9ea0;">Get-ChildItem</span><span style="color:#000000;"> </span><span style="color:#800080;">$env:windir</span><span style="color:#000000;"> </span><span style="color:#5f9ea0;">-Filter</span><span style="color:#000000;"> </span><span style="color:#ff0000;">*</span><span style="color:#000000;">.</span><span style="color:#8b4513;">exe</span><span style="color:#000000;"> </span><span style="color:#5f9ea0;">-ErrorAction</span><span style="color:#000000;"> </span><span style="color:#0000ff;">SilentlyContinue</span><span style="color:#000000;"> </span><span style="color:#5f9ea0;">-Recurse</span><span style="color:#000000;"> </span><span style="color:#0000ff;">|</span><span style="color:#000000;"> </span><span style="color:#5f9ea0;">ForEach-Object</span><span style="color:#000000;"> { </span><span style="color:#800080;">$arch</span><span style="color:#000000;"> </span><span style="color:#ff0000;">=</span><span style="color:#000000;"> </span><span style="color:#5f9ea0;">Get-FileArchitecture</span><span style="color:#000000;"> </span><span style="color:#000080;">$_</span><span style="color:#000000;">.</span><span style="color:#8b4513;">FullName</span><span style="color:#000000;"> </span><span style="color:#0000ff;">if</span><span style="color:#000000;"> (</span><span style="color:#800000;">&#39;</span><span style="color:#800000;">x64</span><span style="color:#800000;">&#39;</span><span style="color:#000000;">,</span><span style="color:#800000;">&#39;</span><span style="color:#800000;">native</span><span style="color:#800000;">&#39;</span><span style="color:#000000;"> </span><span style="color:#ff0000;">-notcontains</span><span style="color:#000000;"> </span><span style="color:#800080;">$arch</span><span style="color:#000000;">) { </span><span style="color:#800080;">$object</span><span style="color:#000000;"> </span><span style="color:#ff0000;">=</span><span style="color:#000000;"> </span><span style="color:#000080;">$_</span><span style="color:#000000;"> </span><span style="color:#0000ff;">|</span><span style="color:#000000;"> </span><span style="color:#5f9ea0;">Select-Object</span><span style="color:#000000;"> </span><span style="color:#5f9ea0;">-Property</span><span style="color:#000000;"> </span><span style="color:#0000ff;">Name</span><span style="color:#000000;">,</span><span style="color:#000000;"> </span><span style="color:#0000ff;">Architecture</span><span style="color:#000000;">,</span><span style="color:#000000;"> </span><span style="color:#0000ff;">FullName</span><span style="color:#000000;"> </span><span style="color:#800080;">$object</span><span style="color:#000000;">.</span><span style="color:#8b4513;">Architecture</span><span style="color:#000000;"> </span><span style="color:#ff0000;">=</span><span style="color:#000000;"> </span><span style="color:#800080;">$arch</span><span style="color:#000000;"> </span><span style="color:#800080;">$object</span><span style="color:#000000;"> } }</span> </pre> <p><a target="twitter" href="http://twitter.com/home/?status=RT+%40PowerTip+%20Identifying%2032-bit%20Executables%20with%20%23PowerShell+http://bit.ly/ZF2q9a"><img src="http://powershell.com/cs/Themes/powershell/images/ps/twitter_32x32.png" alt="Twitter This Tip!" style="vertical-align:middle;border:0px;" /></a> <a target="twitter" href="http://twitter.com/home/?status=RT+%40%20Identifying%2032-bit%20Executables%20with%20%23PowerShell+http://bit.ly/ZF2q9a">ReTweet this Tip!</a></p><div style="clear:both;"></div><img src="http://powershell.com/cs/aggbug.aspx?PostID=23068" width="1" height="1">powershelltipshttp://powershell.com/cs/members/powershelltips/default.aspx/cs/blogs/tips/archive/2013/05/14/creating-string-arrays-without-quotes.aspx2013-05-14T11:00:00Z2013-05-14T11:00:00Z<p>Often, you may need a list of strings and want to store it in a variable. The common coding practice is like this:</p> <pre><span style="color:#800080;">$MachineType</span><span style="color:#000000;"> </span><span style="color:#ff0000;">=</span><span style="color:#000000;"> </span><span style="color:#800000;">&#39;</span><span style="color:#800000;">Native</span><span style="color:#800000;">&#39;</span><span style="color:#000000;">,</span><span style="color:#800000;">&#39;</span><span style="color:#800000;">I386</span><span style="color:#800000;">&#39;</span><span style="color:#000000;">,</span><span style="color:#800000;">&#39;</span><span style="color:#800000;">Itanium</span><span style="color:#800000;">&#39;</span><span style="color:#000000;">,</span><span style="color:#800000;">&#39;</span><span style="color:#800000;">x64</span><span style="color:#800000;">&#39;</span> </pre> <p>A much easier approach does not require quotes or commas. It simply submits the strings you want in your list as parameters to Write-Output. Write-Output is a cmdlet, so it does not require quotes around strings (unless they contain special characters or spaces):</p> <pre><span style="color:#800080;">$MachineType</span><span style="color:#000000;"> </span><span style="color:#ff0000;">=</span><span style="color:#000000;"> </span><span style="color:#5f9ea0;">Write-Output</span><span style="color:#000000;"> </span><span style="color:#0000ff;">Native</span><span style="color:#000000;"> </span><span style="color:#0000ff;">I386</span><span style="color:#000000;"> </span><span style="color:#0000ff;">Itanium</span><span style="color:#000000;"> </span><span style="color:#0000ff;">x64</span> </pre> <p>The result is the same in both cases.</p> <p><a target="twitter" href="http://twitter.com/home/?status=RT+%40PowerTip+%20Creating%20String%20Arrays%20without%20Quotes%20with%20%23PowerShell+http://bit.ly/Z7odlb"><img src="http://powershell.com/cs/Themes/powershell/images/ps/twitter_32x32.png" alt="Twitter This Tip!" style="vertical-align:middle;border:0px;" /></a> <a target="twitter" href="http://twitter.com/home/?status=RT+%40%20Creating%20String%20Arrays%20without%20Quotes%20with%20%23PowerShell+http://bit.ly/Z7odlb">ReTweet this Tip!</a></p><div style="clear:both;"></div><img src="http://powershell.com/cs/aggbug.aspx?PostID=23067" width="1" height="1">powershelltipshttp://powershell.com/cs/members/powershelltips/default.aspx/cs/blogs/tips/archive/2013/05/13/discover-new-quot-internet-quot-cmdlets-in-powershell-3-0.aspx2013-05-13T11:00:00Z2013-05-13T11:00:00Z<p>With Invoke-WebRequest and Invoke-RestMethod, PowerShell 3.0 now has powerful support for downloading information from the Internet as well as communicating with Internet services. We have had a number of tips on these in the past.</p> <p>Some people use Invoke-WebRequest to easily read RSS information. For example, this line is supposed to get the contents of the PowerShell team blog RSS feed:</p> <pre><span style="color:#800080;">$rss</span><span style="color:#000000;"> </span><span style="color:#ff0000;">=</span><span style="color:#000000;"> </span><span style="color:#800000;">&#39;</span><span style="color:#800000;">http://blogs.msdn.com/b/powershell/rss.aspx</span><span style="color:#800000;">&#39;</span><span style="color:#000000;"> </span><span style="color:#5f9ea0;">Invoke-RestMethod</span><span style="color:#000000;"> </span><span style="color:#800080;">$rss</span><span style="color:#000000;"> </span><span style="color:#0000ff;">|</span><span style="color:#000000;"> </span><span style="color:#5f9ea0;">Select-Object</span><span style="color:#000000;"> </span><span style="color:#5f9ea0;">-Property</span><span style="color:#000000;"> </span><span style="color:#0000ff;">Title</span><span style="color:#000000;">,</span><span style="color:#000000;"> </span><span style="color:#0000ff;">Link</span><span style="color:#000000;">,</span><span style="color:#000000;"> </span><span style="color:#0000ff;">PubDate</span> </pre> <p>As it turns out, this works, but the results are only partial. To get the complete team blog, you would have to use Invoke-WebRequest like this:</p> <pre><span style="color:#800080;">$rss</span><span style="color:#000000;"> </span><span style="color:#ff0000;">=</span><span style="color:#000000;"> </span><span style="color:#800000;">&#39;</span><span style="color:#800000;">http://blogs.msdn.com/b/powershell/rss.aspx</span><span style="color:#800000;">&#39;</span><span style="color:#000000;"> </span><span style="color:#800080;">$webpage</span><span style="color:#000000;"> </span><span style="color:#ff0000;">=</span><span style="color:#000000;"> </span><span style="color:#5f9ea0;">Invoke-WebRequest</span><span style="color:#000000;"> </span><span style="color:#800080;">$rss</span><span style="color:#000000;"> </span><span style="color:#800080;">$xml</span><span style="color:#000000;"> </span><span style="color:#ff0000;">=</span><span style="color:#000000;"> [</span><span style="color:#0000ff;">XML</span><span style="color:#000000;">]</span><span style="color:#800080;">$webpage</span><span style="color:#000000;">.</span><span style="color:#8b4513;">Content</span><span style="color:#000000;"> </span><span style="color:#800080;">$xml</span><span style="color:#000000;">.</span><span style="color:#8b4513;">rss</span><span style="color:#000000;">.</span><span style="color:#8b4513;">channel</span><span style="color:#000000;">.</span><span style="color:#8b4513;">item</span><span style="color:#000000;"> </span><span style="color:#0000ff;">|</span><span style="color:#000000;"> </span><span style="color:#5f9ea0;">Select-Object</span><span style="color:#000000;"> </span><span style="color:#5f9ea0;">-Property</span><span style="color:#000000;"> </span><span style="color:#0000ff;">Title</span><span style="color:#000000;">,</span><span style="color:#000000;"> </span><span style="color:#0000ff;">Link</span><span style="color:#000000;">,</span><span style="color:#000000;"> </span><span style="color:#0000ff;">PubDate</span> </pre> <p>So to use these cmdlets, you need to play with them and find out how they work. Invoke-WebRequest always retrieves the complete content from a web page, but leaves it to you to pick the data and data type you need.</p> <p><a target="twitter" href="http://twitter.com/home/?status=RT+%40PowerTip+%20Discover%20New%20"><img src="http://powershell.com/cs/Themes/powershell/images/ps/twitter_32x32.png" alt="Twitter This Tip!" style="vertical-align:middle;border:0px;" /></a> <a target="twitter" href="http://twitter.com/home/?status=RT+%40%20Discover%20New%20">ReTweet this Tip!</a></p><div style="clear:both;"></div><img src="http://powershell.com/cs/aggbug.aspx?PostID=23066" width="1" height="1">powershelltipshttp://powershell.com/cs/members/powershelltips/default.aspx/cs/blogs/tips/archive/2013/05/10/using-help-window-as-text-dialog.aspx2013-05-10T11:00:00Z2013-05-10T11:00:00Z<p>Did you know that you can use the Help Window that comes with PowerShell 3.0 and display your own text information inside of it? What&#39;s even better: the help window will support full text searches in the text you display and highlight any matching text, just like with PowerShell help topics.</p> <p>Note: the code works immediately in PowerShell 3.0 ISE editor. If you want to run it in the PowerShell 3.0 console, you need to first load the necessary assembly like this:</p> <pre><span style="color:#5f9ea0;">Add-Type</span><span style="color:#000000;"> </span><span style="color:#5f9ea0;">-AssemblyName</span><span style="color:#000000;"> </span><span style="color:#8b4513;">Microsoft.PowerShell.GraphicalHost</span> </pre> <p>Here&#39;s the code (it displays text found in winrm.ini but you can display any text - just assign it to $text).</p> <pre><span style="color:#800080;">$text</span><span style="color:#000000;"> </span><span style="color:#ff0000;">=</span><span style="color:#000000;"> </span><span style="color:#5f9ea0;">Get-Content</span><span style="color:#000000;"> </span><span style="color:#800080;">$env:windir</span><span style="color:#000000;">\</span><span style="color:#0000ff;">system32</span><span style="color:#000000;">\</span><span style="color:#0000ff;">winrm</span><span style="color:#000000;">\</span><span style="color:#ff0000;">*</span><span style="color:#000000;">\</span><span style="color:#8b4513;">winrm.ini</span><span style="color:#000000;"> </span><span style="color:#5f9ea0;">-ReadCount</span><span style="color:#000000;"> </span><span style="color:#000000;">0</span><span style="color:#000000;"> </span><span style="color:#0000ff;">|</span><span style="color:#000000;"> </span><span style="color:#5f9ea0;">Out-String</span><span style="color:#000000;"> </span><span style="color:#800080;">$HelpWindow</span><span style="color:#000000;"> </span><span style="color:#ff0000;">=</span><span style="color:#000000;"> </span><span style="color:#5f9ea0;">New-Object</span><span style="color:#000000;"> </span><span style="color:#8b4513;">Microsoft.Management.UI.HelpWindow</span><span style="color:#000000;"> </span><span style="color:#800080;">$text</span><span style="color:#000000;"> </span><span style="color:#5f9ea0;">-Property</span><span style="color:#000000;"> </span><span style="color:#000000;">@</span><span style="color:#000000;">{ </span><span style="color:#0000ff;">Title</span><span style="color:#ff0000;">=</span><span style="color:#800000;">&quot;My Text Viewer&quot;</span><span style="color:#000000;"> </span><span style="color:#0000ff;">Background</span><span style="color:#ff0000;">=</span><span style="color:#800000;">&#39;</span><span style="color:#800000;">#011f51</span><span style="color:#800000;">&#39;</span><span style="color:#000000;"> </span><span style="color:#0000ff;">Foreground</span><span style="color:#ff0000;">=</span><span style="color:#800000;">&#39;</span><span style="color:#800000;">#FFFFFFFF</span><span style="color:#800000;">&#39;</span><span style="color:#000000;"> } </span><span style="color:#800080;">$HelpWindow</span><span style="color:#000000;">.</span><span style="color:#8b4513;">ShowDialog</span><span style="color:#000000;">()</span> </pre> <p><a target="twitter" href="http://twitter.com/home/?status=RT+%40PowerTip+%20Using%20Help%20Window%20as%20Text%20Dialog%20with%20%23PowerShell+http://bit.ly/14ZROoT"><img src="http://powershell.com/cs/Themes/powershell/images/ps/twitter_32x32.png" alt="Twitter This Tip!" style="vertical-align:middle;border:0px;" /></a> <a target="twitter" href="http://twitter.com/home/?status=RT+%40%20Using%20Help%20Window%20as%20Text%20Dialog%20with%20%23PowerShell+http://bit.ly/14ZROoT">ReTweet this Tip!</a></p><div style="clear:both;"></div><img src="http://powershell.com/cs/aggbug.aspx?PostID=23065" width="1" height="1">powershelltipshttp://powershell.com/cs/members/powershelltips/default.aspx/cs/blogs/tips/archive/2013/05/09/using-default-parameter-values.aspx2013-05-09T11:00:00Z2013-05-09T11:00:00Z<p>If you find yourself submitting the same value for a cmdlet parameter over and over again, then PowerShell 3.0 lets you set a default value.</p> <p>Once you defined a default value for a parameter, you no longer need to specify it. This can be very convenient in production scenarios. It can be dangerous, too, because scripts that rely on this may not run on other machines anymore.</p> <p>For example, to default the Path parameter of Get-ChildItem to the temporary folder, this is what you do:</p> <pre><span style="color:#000080;">$PSDefaultParameterValues</span><span style="color:#000000;">.</span><span style="color:#8b4513;">Add</span><span style="color:#000000;">(</span><span style="color:#800000;">&#39;</span><span style="color:#800000;">Get-ChildItem:Path</span><span style="color:#800000;">&#39;</span><span style="color:#000000;">,</span><span style="color:#000000;"> </span><span style="color:#800080;">$env:temp</span><span style="color:#000000;">)</span> </pre> <p>Next time you run Get-ChildItem (or one of its aliases such as dir) without specifying a path, you get the content of your temp folder.</p> <p>To make a default that is not limited to Get-ChildItem but applies to any cmdlet that has a Path parameter, replace the cmdlet name with a wildcard:</p> <pre><span style="color:#000080;">$PSDefaultParameterValues</span><span style="color:#000000;">.</span><span style="color:#8b4513;">Add</span><span style="color:#000000;">(</span><span style="color:#800000;">&#39;</span><span style="color:#800000;">*:Path</span><span style="color:#800000;">&#39;</span><span style="color:#000000;">,</span><span style="color:#000000;"> </span><span style="color:#800080;">$env:temp</span><span style="color:#000000;">)</span> </pre> <p>Once you play with this, you&#39;ll soon find that defaults can be very useful but should be limited to cmdlets where they make sense. Fortunately, $PSDefaultParameterValues will forget all values once you restart PowerShell, so it&#39;s easy to get rid of unwanted defaults.</p> <p>Defaults you found useful should be defined in one of your profile scripts (for example, the one specified in $profile).</p> <p><a target="twitter" href="http://twitter.com/home/?status=RT+%40PowerTip+%20Using%20Default%20Parameter%20Values%20with%20%23PowerShell+http://bit.ly/184yBky"><img src="http://powershell.com/cs/Themes/powershell/images/ps/twitter_32x32.png" alt="Twitter This Tip!" style="vertical-align:middle;border:0px;" /></a> <a target="twitter" href="http://twitter.com/home/?status=RT+%40%20Using%20Default%20Parameter%20Values%20with%20%23PowerShell+http://bit.ly/184yBky">ReTweet this Tip!</a></p><div style="clear:both;"></div><img src="http://powershell.com/cs/aggbug.aspx?PostID=23064" width="1" height="1">powershelltipshttp://powershell.com/cs/members/powershelltips/default.aspx/cs/blogs/tips/archive/2013/05/08/find-matching-brace-or-parenthesis.aspx2013-05-08T11:00:00Z2013-05-08T11:00:00Z<p>One common headache are non-matching braces or parentheses in PowerShell scripts. So when you write a script, it is recommended to align matching braces and parentheses and make your code more readable this way.</p> <p>In addition, PowerShell 3.0 ISE editor helps identify the matching counterpart. When you position the cursor right before a brace or parenthesis, the matching one gets highlighted. Unfortunately, the highlight color is light gray so you may not have noticed this before.</p> <p>If the matching counterpart is not visible, you can press CTRL+] (or choose Edit-Go to match in the menu). It is selectable only when the cursor is positioned right before a brace or parenthesis.</p> <p>On a side note, this menu item has been wrongly localized in some cultures. In Germany, for example, &quot;match&quot; was translated with &quot;game&quot;, so you may have wondered what &quot;games&quot; you could play in ISE when you looked at the menu item before).</p> <p><a target="twitter" href="http://twitter.com/home/?status=RT+%40PowerTip+%20Find%20Matching%20Brace%20(or%20Parenthesis)%20with%20%23PowerShell+http://bit.ly/11ta834"><img src="http://powershell.com/cs/Themes/powershell/images/ps/twitter_32x32.png" alt="Twitter This Tip!" style="vertical-align:middle;border:0px;" /></a> <a target="twitter" href="http://twitter.com/home/?status=RT+%40%20Find%20Matching%20Brace%20(or%20Parenthesis)%20with%20%23PowerShell+http://bit.ly/11ta834">ReTweet this Tip!</a></p><div style="clear:both;"></div><img src="http://powershell.com/cs/aggbug.aspx?PostID=23063" width="1" height="1">powershelltipshttp://powershell.com/cs/members/powershelltips/default.aspx/cs/blogs/tips/archive/2013/05/07/using-central-ise-snippet-repository.aspx2013-05-07T11:00:00Z2013-05-07T11:00:00Z<p>In a previous tip we illustrated that ISE code snippets (press CTRL+J to view them) are plain ps1xml-files that you can manage in File Explorer. By default, the PowerShell 3.0 ISE editor loads snippets from your private cache folder.</p> <p>Imagine you and your colleagues set up a network drive to share useful snippets. Instead of manually checking this folder and manually copying the snippets from this folder onto your local machine, you can also tell the ISE editor to load the snippets directly from the central repository. Here is a sample:</p> <pre><span style="color:#800080;">$snippetPath</span><span style="color:#000000;"> </span><span style="color:#ff0000;">=</span><span style="color:#000000;"> </span><span style="color:#5f9ea0;">Join-Path</span><span style="color:#000000;"> (</span><span style="color:#5f9ea0;">Split-Path</span><span style="color:#000000;"> </span><span style="color:#800080;">$profile</span><span style="color:#000000;">.</span><span style="color:#8b4513;">CurrentUserCurrentHost</span><span style="color:#000000;">) </span><span style="color:#800000;">&quot;Snippets&quot;</span><span style="color:#000000;"> </span><span style="color:#800080;">$snippetPath</span><span style="color:#000000;"> </span><span style="color:#5f9ea0;">Get-ChildItem</span><span style="color:#000000;"> </span><span style="color:#5f9ea0;">-Path</span><span style="color:#000000;"> </span><span style="color:#800080;">$snippetPath</span><span style="color:#000000;"> </span><span style="color:#5f9ea0;">-Filter</span><span style="color:#000000;"> </span><span style="color:#ff0000;">*</span><span style="color:#000000;">.</span><span style="color:#8b4513;">ps1xml</span><span style="color:#000000;"> </span><span style="color:#0000ff;">|</span><span style="color:#000000;"> </span><span style="color:#5f9ea0;">ForEach-Object</span><span style="color:#000000;"> { </span><span style="color:#800080;">$psise</span><span style="color:#000000;">.</span><span style="color:#8b4513;">CurrentPowerShellTab</span><span style="color:#000000;">.</span><span style="color:#8b4513;">Snippets</span><span style="color:#000000;">.</span><span style="color:#8b4513;">Load</span><span style="color:#000000;">(</span><span style="color:#000080;">$_</span><span style="color:#000000;">.</span><span style="color:#8b4513;">FullName</span><span style="color:#000000;">) }</span> </pre> <p>This sample loads the snippets from your private local folder, so it shows what ISE does by default. Simply assign another path to $snippetPath to load the snippets from another folder. This could be your central team repository, and it could also be a USB stick you are carrying around with you that holds your favorite snippets.</p> <p>As it turns out, this is the code executed behind the scenes by Import-IseSnippet. In fact, all *-IseSnippet commands are functions, and you can view the source code like this:</p> <pre><span style="color:#800080;">$path</span><span style="color:#000000;"> </span><span style="color:#ff0000;">=</span><span style="color:#000000;"> </span><span style="color:#800000;">&quot;</span><span style="text-decoration:underline;color:#008000;">$pshome\modules\ise\ise.psm1</span><span style="color:#800000;">&quot;</span><span style="color:#000000;"> </span><span style="color:#0000ff;">ise</span><span style="color:#000000;"> </span><span style="color:#800080;">$path</span> </pre> <p><a target="twitter" href="http://twitter.com/home/?status=RT+%40PowerTip+%20Using%20Central%20ISE%20Snippet%20Repository%20with%20%23PowerShell+http://bit.ly/15QapTP"><img src="http://powershell.com/cs/Themes/powershell/images/ps/twitter_32x32.png" alt="Twitter This Tip!" style="vertical-align:middle;border:0px;" /></a> <a target="twitter" href="http://twitter.com/home/?status=RT+%40%20Using%20Central%20ISE%20Snippet%20Repository%20with%20%23PowerShell+http://bit.ly/15QapTP">ReTweet this Tip!</a></p><div style="clear:both;"></div><img src="http://powershell.com/cs/aggbug.aspx?PostID=23062" width="1" height="1">powershelltipshttp://powershell.com/cs/members/powershelltips/default.aspx/cs/blogs/tips/archive/2013/05/06/sharing-and-exchanging-ise-code-snippets.aspx2013-05-06T11:00:00Z2013-05-06T11:00:00Z<p>By default, the PowerShell 3.0 ISE editor loads code snippets automatically, and you can then select and insert any of these by pressing CTRL+J.</p> <p>Custom code snippets are stored in a special folder that you can open like this:</p> <pre><span style="color:#800080;">$snippetPath</span><span style="color:#000000;"> </span><span style="color:#ff0000;">=</span><span style="color:#000000;"> </span><span style="color:#5f9ea0;">Join-Path</span><span style="color:#000000;"> (</span><span style="color:#5f9ea0;">Split-Path</span><span style="color:#000000;"> </span><span style="color:#800080;">$profile</span><span style="color:#000000;">.</span><span style="color:#8b4513;">CurrentUserCurrentHost</span><span style="color:#000000;">) </span><span style="color:#800000;">&quot;Snippets&quot;</span><span style="color:#000000;"> </span><span style="color:#0000ff;">explorer</span><span style="color:#000000;"> </span><span style="color:#800080;">$snippetPath</span> </pre> <p>As you see, custom snippets are stored in a folder, and each is a file with the extension ps1xml. By opening this folder in your File Explorer, it is very easy to delete unwanted snippets or share some of them with friends and colleagues.</p> <p><a target="twitter" href="http://twitter.com/home/?status=RT+%40PowerTip+%20Sharing%20and%20Exchanging%20ISE%20Code%20Snippets%20with%20%23PowerShell+http://bit.ly/ZOUPTZ"><img src="http://powershell.com/cs/Themes/powershell/images/ps/twitter_32x32.png" alt="Twitter This Tip!" style="vertical-align:middle;border:0px;" /></a> <a target="twitter" href="http://twitter.com/home/?status=RT+%40%20Sharing%20and%20Exchanging%20ISE%20Code%20Snippets%20with%20%23PowerShell+http://bit.ly/ZOUPTZ">ReTweet this Tip!</a></p><div style="clear:both;"></div><img src="http://powershell.com/cs/aggbug.aspx?PostID=23061" width="1" height="1">powershelltipshttp://powershell.com/cs/members/powershelltips/default.aspx/cs/blogs/tips/archive/2013/05/03/hiding-default-ise-snippets.aspx2013-05-03T11:00:00Z2013-05-03T11:00:00Z<p>The PowerShell 3.0 ISE editor ships with a number of default code snippets that you can see (and insert) by pressing CTRL+J. Once you start to refine your snippets and create your own (New-IseSnippet), you may want to hide the default snippets.</p> <p>This line will remove the default snippets from the snippet menu:</p> <pre><span style="color:#800080;">$psISE</span><span style="color:#000000;">.</span><span style="color:#8b4513;">Options</span><span style="color:#000000;">.</span><span style="color:#8b4513;">ShowDefaultSnippets</span><span style="color:#000000;"> </span><span style="color:#ff0000;">=</span><span style="color:#000000;"> </span><span style="color:#0000ff;">$false</span> </pre> <p>And this line will re-enable default snippets:</p> <pre><span style="color:#800080;">$psISE</span><span style="color:#000000;">.</span><span style="color:#8b4513;">Options</span><span style="color:#000000;">.</span><span style="color:#8b4513;">ShowDefaultSnippets</span><span style="color:#000000;"> </span><span style="color:#ff0000;">=</span><span style="color:#000000;"> </span><span style="color:#0000ff;">$true</span> </pre> <p><a target="twitter" href="http://twitter.com/home/?status=RT+%40PowerTip+%20Hiding%20Default%20ISE%20Snippets%20with%20%23PowerShell+http://bit.ly/Zf4cOj"><img src="http://powershell.com/cs/Themes/powershell/images/ps/twitter_32x32.png" alt="Twitter This Tip!" style="vertical-align:middle;border:0px;" /></a> <a target="twitter" href="http://twitter.com/home/?status=RT+%40%20Hiding%20Default%20ISE%20Snippets%20with%20%23PowerShell+http://bit.ly/Zf4cOj">ReTweet this Tip!</a></p><div style="clear:both;"></div><img src="http://powershell.com/cs/aggbug.aspx?PostID=22946" width="1" height="1">powershelltipshttp://powershell.com/cs/members/powershelltips/default.aspx/cs/blogs/tips/archive/2013/05/02/removing-ise-snippets.aspx2013-05-02T11:00:00Z2013-05-02T11:00:00Z<p>In a previous tip, we showed how you can use New-IseSnippet to add new code snippets to the ISE editor in PowerShell 3.0. These custom snippets stay permanently because PowerShell creates XML files for them. You can view these files with Get-IseSnippet:</p> <pre><span style="color:#5f9ea0;">Get-IseSnippet</span> </pre> <p>To remove a snippet that you no longer need, use Get-IseSnippet, identify the one you want to get rid of, and delete it. This sample would look for a snippet with a name that starts with &quot;function body&quot;, and deletes it:</p> <pre><span style="color:#5f9ea0;">Get-IseSnippet</span><span style="color:#000000;"> </span><span style="color:#0000ff;">|</span><span style="color:#000000;"> </span><span style="color:#5f9ea0;">Where-Object</span><span style="color:#000000;"> </span><span style="color:#0000ff;">Name</span><span style="color:#000000;"> </span><span style="color:#ff0000;">-like</span><span style="color:#000000;"> </span><span style="color:#800000;">&#39;</span><span style="color:#800000;">Function body*</span><span style="color:#800000;">&#39;</span><span style="color:#000000;"> </span><span style="color:#0000ff;">|</span><span style="color:#000000;"> </span><span style="color:#5f9ea0;">Remove-Item</span> </pre> <p>The snippet will stay in memory until you close the ISE editor.</p> <p><a target="twitter" href="http://twitter.com/home/?status=RT+%40PowerTip+%20Removing%20ISE%20Snippets%20with%20%23PowerShell+http://bit.ly/11BJBzs"><img src="http://powershell.com/cs/Themes/powershell/images/ps/twitter_32x32.png" alt="Twitter This Tip!" style="vertical-align:middle;border:0px;" /></a> <a target="twitter" href="http://twitter.com/home/?status=RT+%40%20Removing%20ISE%20Snippets%20with%20%23PowerShell+http://bit.ly/11BJBzs">ReTweet this Tip!</a></p><div style="clear:both;"></div><img src="http://powershell.com/cs/aggbug.aspx?PostID=22945" width="1" height="1">powershelltipshttp://powershell.com/cs/members/powershelltips/default.aspx