Leveraging Windows PowerShell Type Extensions to get documentation

Active directory search | keyongtech

Active directory search | keyongtech — Sun, 18 Jan 2009 19:27:38 GMT

PingBack from http://www.keyongtech.com/2835580-active-directory-search

re: Leveraging Windows PowerShell Type Extensions to get documentation

June Blender — Sat, 14 Jun 2008 05:16:32 GMT

An added "Select" makes it work with collections. It gets the .NET help for the type of the first object in the collection.

$Uri = "http://msdn2.microsoft.com/" + $culture + "/library/" + ($this | select -first 1).GetType().FullName + ".ASPX"

Otherwise, you get "Content Not Found" for:

(get-process).msdn(), which will confuse beginners.

re: Leveraging Windows PowerShell Type Extensions to get documentation

vozeldr — Thu, 13 Sep 2007 22:58:57 GMT

When used with a COM object, the method throws an exception because it cannot reflect out the GetType method.

re: Leveraging Windows PowerShell Type Extensions to get documentation

nene — Tue, 12 Sep 2006 00:40:19 GMT

gfg

re: Leveraging Windows PowerShell Type Extensions to get documentation

Nick Daniels — Tue, 22 Aug 2006 19:48:06 GMT

Also if you change the begining of $Uri to http://windowssdk.msdn.microsoft.com/ you'll get docs for all the PowerShell and .Net 3.0 objects. Handy.

re: Leveraging Windows PowerShell Type Extensions to get documentation

Nick Daniels — Tue, 22 Aug 2006 19:37:54 GMT

Here is an even shorter script that will start your default browser, be it IE, FireFox, Opera, Whatever:

$culture = $host.currentculture
if ($args[0])
{
$culture = $args[0]
}
$Uri = "http://msdn2.microsoft.com/" + $culture + "/library/" + $this.GetType().FullName + ".ASPX"

[System.Diagnostics.Process]::Start($uri) | out-null

ScriptBlock and Runspace Remoting in PowerShell

ComputerZen.com - Scott Hanselman — Sat, 15 Jul 2006 12:13:11 GMT

BaseName for FileInfo objects

Windows PowerShell — Mon, 03 Jul 2006 00:30:23 GMT

&lt;Edited to add categories&gt;In our active, responsive, and useful newsgroup Microsoft.Public.Windows.PowerShell...

re: Leveraging Windows PowerShell Type Extensions to get documentation

borota — Tue, 27 Jun 2006 09:13:56 GMT

In my customization, I added these 2 lines at the end of script area, to also activate the Internet Explorer window:

$ShellObj = New-Object -ComObject WScript.Shell
$ShellObj.AppActivate((Get-Process | Where {$_.MainWindowHandle -eq $global:MSDNViewer.HWND}).Id)

I wonder if that could be done by just using PowerShell existent cmdlets though.

PowerShell is so cooool. I love it! Working with objects at the command line - the idea is just brilliant!

Interesting Finds: June 24, 2006 AM edition

Jason Haley — Sat, 24 Jun 2006 18:47:27 GMT