21 Mar 2009 11:46
Congratulations to Jeffrey Snover, the main inventor of PowerShell
http://www.microsoft.com/presspass/exec ... fault.mspx
Powershell is becoming a HUGE deal at Microsoft
All Microsoft server products are eventually to become PowerShell-compatible
Exchange 2007 and Powershell
https://docs.microsoft.com/en-us/powers ... xchange-ps
SQL Server and Powershell
https://docs.microsoft.com/en-us/sql/po ... rver-ver15
Sharepoint (next version)
https://www.microsoft.com/en-gb/downloa ... x?id=35588
https://web.archive.org/web/20120301023 ... fault.mspx
#08 Nov 2009 20:00
Jim de Graff
My problem with PowerShell is that it is too easy to write code that nobody else can read. It is approaching the (lack of) readability of APL which mainly could not even be deciphered by the original coder a day or two later.
Sacred cows make the tastiest burgers.
#24 Jan 2011 22:59
^ This is true if you write everything using Alias names and shortcut syntax.
If you want to make readable PowerShell scripts it's generally a good idea to use the full cmdlet names.
Alias definitions can be changed or over-ridden with a function, but if you use the full cmdlet name there can't be any possible confusion about what will be run.
When running commands interactively at the command line this really doesnt matter, but once you save something as a script it does pay to avoid Alias names. It also means that if in 5 years time you suddenly want to customise an alias, then you don't have to worry about it breaking a load of scripts you already wrote.
1 post • Page 1 of 1