SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I've just started reading various books on SharePoint development and have come across a wonderful tool called PowerShell. From the looks of it, it could replace the old DOS tool cmd.exe. There are a few blogs discussing PowerShell vs. cmd.exe, but I have found none really useful one discussing PowerShell vs. cmd.exe in the eyes of a SharePoint developer.

Simply put, is it possible to only use PowerShell as the only command line tool as a SharePoint developer, or do you still rely on cmd.exe?

share|improve this question
up vote 1 down vote accepted

There's no task you couldn't do with PS because it allows to work with any .NET objects. The stsadm tool is considered obsolete now - the most commands have the equivalents in SharePoint PS commandlets. And for the unsupported stsadm options you can still use stsadm even through PS as it's able to execute standard command line tools. So you definitely can work with PS alone.

share|improve this answer
Thanx, just what I needed, and wanted to hear! – Benny Skogberg Mar 6 '12 at 20:32

you cannot do much using cmd.exe in terms of working with sharepoint. the key difference between cmd.exe and powershell when it comes to sharepoint is the fact that yuo can use C# assemblies within powershell. this allows you to access sharepoint core libraries from within powershell. This functionality is not available in cmd.exe. So you will only use powershell as your cmd line tool.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.