Comments on: Powershell Powers, Activate!

By: Andrew

Andrew — Sat, 17 Jan 2009 23:13:23 +0000

Thanks, Jeffrey! That looks promising — although I hope I don’t have to pull apart a build system XML the next time I need to walk a document tree. =]

By: Jeffrey Snover

Jeffrey Snover — Sat, 17 Jan 2009 19:11:58 +0000

Sounds like you should check out the new Select-XML cmdlet in CTP3:
Select-Xml
(0)-XPath
(1)-Xml | -Node (ByValue)
[-Namespace ]

Select-Xml
(0)-XPath
-Content (ByValue)
[-Namespace ]

Select-Xml
(0)-XPath
(1)-Path | -PSPath (ByName)
[-Namespace ]

Here is an example of it working:
[5308:0]PS> dir . *xml -Recurse |select-xml ‘//SelectionSet[Name="CertificateProviderTypes"]‘ |fl

Node : SelectionSet
Path : C:\Windows\System32\WindowsPowerShell\v1.0\Certificate.Format.ps1xml
Pattern : //SelectionSet[Name="CertificateProviderTypes"]

Experiment! Enjoy! Engage!

Jeffrey Snover [MSFT]
Windows Management Partner Architect
Visit the Windows PowerShell Team blog at: http://blogs.msdn.com/PowerShell
Visit the Windows PowerShell ScriptCenter at: http://www.microsoft.com/technet/scriptcenter/hubs/msh.mspx

By: Andrew

Andrew — Sat, 17 Jan 2009 08:51:08 +0000

Ha. Ha. Ha.
I can do pretty much anything possible via bash or csh via Powershell — however, I’m being extremely lazy about it. Conceivably (I’m not testing it, and I’m not a Powershell expert), I should be able to:
([xml] [string]::join(“`n”, (gc -read 10kb Native.Build.targets))).GetElementsByTagName(“Internal_LinkOutputFile”) | % { $temp = $_.CreateNavigator() ; while ($temp.MoveToParent()) { } ; $temp }

Where EVERYTHING in the pipeline is an object, rather than restricted to just text flow.

You can go back to your pipe characters and output redirection, I’ll stick with my strongly-typed scripting interactive command intepreter. =]

By: Darth Paradox

Darth Paradox — Sat, 17 Jan 2009 07:04:01 +0000

PowerShell, huh? That sounds almost as nifty as basic Unix!