Automating the world one-liner at a time…
On an internal email thread, someone asked Vivek Sharma why they should implement PowerShell. They knew that PowerShell provided scripting but they had a COM interface which already gave them scripting so the question was – what, if any, were the additional benefits to doing PowerShell. Vivek gave a great answer that I thought I would share with you:
Any guesses why I'm a charter member of the Vivek Sharma fan club?
The Exchange team totally got PowerShell when other people looked at us like we had a rat's tail hanging out of our mouths. They are a high IQ team.
Jeffrey Snover [MSFT]Windows PowerShell/MMC ArchitectVisit the Windows PowerShell Team blog at: http://blogs.msdn.com/PowerShellVisit the Windows PowerShell ScriptCenter at: http://www.microsoft.com/technet/scriptcenter/hubs/msh.mspx
I thought PowerShell for Vista was coming yesterday... not even a blog post to say "it's coming" or "we're late because..."
I keep drooling over all the bloggers talking about PowerShell, but I can't use it yet!
> I thought PowerShell for Vista was coming yesterday...
Your wait is over:
Jeffrey Snover [MSFT]
Windows PowerShell/MMC 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
What would be really interesting -- both for powershell fans and vista developers -- is: what exactly had to be changed for PowerShell to run smoothly on Vista?
Is it possible, in some way/shape/form, to replace CMD.EXE with PowerShell system-wide? As in, use PowerShell as a default command prompt?
That would depend -- truthfully, it's probably not something you want to remove completely. It's an operating system component, so lots of little programs (i.e.: shareware, etc) assume that it exists. See some background here: http://www.leeholmes.com/blog/NothingSolvesEverythingPowerShellAndOtherTechnologies.aspx. You've also got situations where applications ship with batch files to help you work with them -- such as the vsvars32.bat that ships with Visual Studio. PowerShell can't interpret .bat or .cmd files, so you'd be out of luck there.
That said, it is absolutely possible to use PowerShell for all of your command prompt needs. For that, you just type Start | Run | "powershell" instead of Start | Run | "cmd". If you use a shortcut to launch cmd.exe, have it launch PowerShell instead.
Glad to hear you're kicking the tires :)
Lee Holmes [MSFT]
Windows PowerShell Development
Cool. Was the question to Vivek from the AD team?
Serious question - what's the state of the AD team's support for PowerShell; and if it isn't going to be "any day now" what can I do as a customer to speed up the process?
I've been doing interactive JScript for years, using a simple read-eval-print loop. Some COM automation works very well. Others, not so much. Powershell is so much better.