Automating the world one-liner at a time…
One of the things I like to say is that, “Microsoft is incapable of sustained error”. By that I mean that Microsoft is an intensely self-conscious culture, fearless about confronting shortcomings and constantly looking for ways to do things better. We beat ourselves up pretty brutally about the shortcomings of Vista and committed ourselves to doing better going forward. This is one of the reasons why Windows Server 2008 was such a good release. We didn’t stop there, we raised the bar for Windows 7 and Windows Server 2008 R2.
Part of that was the product itself. Anyone that uses either of these products can see that immediately. These are solid, high quality products. We also raised the bar and teaching people about the release.
This morning, MSDN’s Channel9 opened up a new site for learning about WS08/R2 HERE. This site has lessons and short training videos for the following WS08/R2 topics:
Much of this content if focused on developers but admin/It Pro scripters will find PowerShell section useful and appropriate.
Experiment! Enjoy! Engage!
Jeffrey Snover [MSFT] Distinguished Engineer 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
You changed Powershell to allow a "-force" option to remove-item [http://blogs.msdn.com/powershell/archive/2006/04/25/is-it-safe-to-use-aliases-in-scripts.aspx]. That works. However, I must ask, if you allow people to remove the item, why didn't you just allow them to remove the "readonly" attribute rather than add to the syntax of the PS language?
Also, one reason to remove the "diff" alias, for instance, is that there is a different "diff" in the Unix utilies. By having readonly aliases, it makes writing powershell scripts that use the Unix "diff" non-portable because you have encode a full path name to use the Unix version of diff.
For all published scripts [any script given to another] I strongly recommend not using aliases. Readbility is infinitely more important than pithyness when it comes to publishing a program.
50% of programming is communication. Don't throw the value of Powershell away, by minimizing communication.
I like PS 2.0 a lot!! Good work you folks have done. PS is on my list of excellent things from Microsoft.
Will PowerShell be available on Core anytime soon? I've seen some hacks on how to get it to work on Win Server 2008 but I'm wondering do you know will it be supported in future?
vary excellent post shearing.thanks