Scott Hanselman

browse by category or date

The Value of Writing Windows PowerShell Cmdlets

June 13, '07 Comments [2] Posted in Corillian | PowerShell | Programming
Sponsored By

image The folks at Channel 9 dug up another interview I did with Jeffrey Snover, PowerShell architect. Here's the one I did in November of 2006, for contrast. The project has grown

I think we filmed this in March. In this one I sing the praises of PowerShell and our team at Corillian that wrote "Project Evergreen," a deployment philosophy that turned into our Corillian Member Advantage product. Check the video out. Watch it via Windows Media or download the WMV. I hope you enjoy it.

« Six Essential Language Agnostic Programm... | Blog Home | Some Guiding Principles for Software Dev... »

About Scott

Scott Hanselman is a former professor, former Chief Architect in finance, now speaker, consultant, father, diabetic, and Microsoft employee. I am a failed stand-up comic, a cornrower, and a book author.

facebook twitter subscribe
About   Newsletter
Sponsored By
Hosting By
Dedicated Windows Server Hosting by ORCS Web
Comments [2]
Thursday, June 14, 2007 6:25:44 AM UTC
Interesting. How did you incorporate Powershell into Member Advantage?

BTW, now that you are part of Checkfree does that mean you'll be hanging out here in Atlanta much? '-)

(Also, really nice real-time comment preview!)
Mike Schinkel
Tuesday, June 19, 2007 1:30:41 AM UTC
Great video and interesting, as always. I had a thought for a future video cast or blog entry. I'd love to see you discuss in more detail how to build a system that makes use of cmdlets to perform the high-level activities as you discussed here. Perhaps just a basic Windows Forms application that invoked cmdlets to do some sort of business logic. I can't find many resources out there that covers this topic, yet it is mentioned frequently with reference to Exchange and in your video.

Thanks,
Brian
Brian Vallelunga
Comments are closed.

Disclaimer: The opinions expressed herein are my own personal opinions and do not represent my employer's view in any way.