What was so unlovely about it? It worked just fine. Since most front-end developers are familiar with C# or Java, it makes it easier for them but PowerShell is just a different way of doing the same thing you could do in VBS.

--Jeff Moden"RBAR is pronounced "ree-bar" and is a "Modenism" for "Row-By-Agonizing-Row".

First step towards the paradigm shift of writing Set Based code: Stop thinking about what you want to do to a row... think, instead, of what you want to do to a column."

Hail The PowershellNice and to the point editorialI was there in Teched, attended all the powershell conferencesI am still in the information-overload stage, so much good informationAlso got exposed to F# and the Kanban!!!Now I just need to brush up my Klingon!!!

Phil Factor (6/24/2012)Jeff, if you think that PowerShell is equivelent to VBA/VBScript, then you haven't tried PowerShell hard enough. Sure, you can convert from VB to PowerShell, but PowerShell does so much more...

Agreed. I find Powershell to be surprisingly set-oriented for such a procedural/operational language. In many ways it's the most SQL-like language Microsoft has ever released to production. (besides actual SQL of course... )

Good article. I would appreciate it if someone could bring me up to speed on this point: Does PowerShell itself (v 3.0?), or a third-party product, offer PowerShell debugging capability that is the equivalent of that found in the VS.NET IDE for VB.NET\C# ? (I regard such debugging capability as essential, not just a nice feature.)