PowerShell Language now licensed under the Community Promise

Rate This
  • Comments 8

The PowerShell team is excited to announce that starting today we are licensing the language specification for Windows PowerShell 2.0 under the Microsoft Community Promise.

This means that now anyone can implement PowerShell on any platform they want to.  We know some of our most passionate customers sometimes work on platforms that can’t run PowerShell today, so when writing this specification, we wrote it in a platform neutral manner.

We hope to see implementations on all of your favorite platforms.  This would benefit the industry, our partners, and our customers.  We told you that you should learn PowerShell and we would do everything we could to make it the best investment you ever made.  Specifying the language and enabling the community to implement it is yet another step in that direction.

Wait, did I just hear you ask: “what language specification?”  Grab it here - hot off the press:


Even if you aren’t planning on implementing the language, you might still find the specification to be an interesting read.  Some reviewers said the specification helped clear up some aspects of the language.

If you’re a language geek like me, love implementing languages, and love PowerShell, then this news and documentation should give you plenty of incentive to get started.  Be sure to check out the community promise before getting started:


Jason Shirk
Windows PowerShell SDE
Microsoft Corporation

Leave a Comment
  • Please add 4 and 3 and type the answer here:
  • Post
  • I am curious if Microsoft will work on porting PowerShell to other platform now?   Or support some initiative like Pash (http://pash.sourceforge.net/) project?  I guess by publishing the language specification, you are in a way taking the first step to support that porting initiative and this Community Promise is another.  This is good news.  :)

  • While Microsoft probably won't port this to another platform themselves, I was at the event where they announced this and they do hope this encourages others to make something like Pash.  They know that right now some people don't like PowerShell because it is Microsoft only.  They talked about Pash and commented that the complexity of the task made it very difficult for them to succeed without a document like this.  

    I'm glad they have this out now and also hope that others implement PowerShell on other platforms.

  • If you freely licensed the source code then implementing PowerShell on other platforms would be even easier.

  • Other platforms have various excellent shells.  Why would anyone be interested in PowerShell?

  • Do any other platforms have such a modern shell, modern meaning that we're passing and handling objects instead of strings most of the time?

  • No, they don't. That's why they need PowerShell.

  • Hey Microsoft: Would you consider going a step further, and releasing the PowerShell parser under an Open Source license?

    Or maybe you'd consider sharing your automated tests?

  • Is 'command-argument-token' supposed to be 'command-argument'?

Page 1 of 1 (8 items)

PowerShell Language now licensed under the Community Promise