Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<blockquote> <p>Is it "worthwhile"?</p> </blockquote> <p>Absolutely. Here are number of reasons why.<br /></p> <ol> <li>More and more Microsoft products are based-on PowerShell - e.g. Exchange Server 2007, SQL Server 2008, etc.<br /></li> <li>PowerShell can access Microsoft .NET.</li> <li>Easy to learn - You only need few commands to explore capabilities of PowerShell - e.g.) Get-Command, Get-Help, Get-Member, etc.</li> <li>Most of commands are aliased and mapped in a way that they are similar to DOS or *NIX shell commands - e.g.) "ls" and "dir" are aliases for "Get-ChildItem", "cd" for "Set-Location"</li> <li>It's a great developer's tool - Since PowerShell can access .NET library, you can prototype some of your .NET functionalities in PowerShell</li> <li>You can navigate around Registry, Certificate, Environment Variables, etc as if they are file system - You use the same command you use in FileSystem to navigate around - e.g.) cd HKLM:\</li> </ol> <p><strong>Drawbacks:</strong><br /></p> <ol> <li>PowerShell version 1.0 does not support Remoting (supported in 2.0) and creating a new thread(using System.Threading.Thread, but will support background jobs in 2.0)<br /></li> <li>Learning curve can be long if you are not used to C#/Java based language<br /></li> <li>It's hard to create generic .NET objects <ul> <li>e.g.) creating a generic <code>List&lt;int&gt;</code> collection is like following</li> </ul></li> </ol> <blockquote> <p>$l = new-Object System.Collections.Generic.List``1[[System.Int32]]</p> </blockquote>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload