About the name

Pash = PoSH (PowerShell) + bash (one of the Unix shells)

Goals

The main goal is to provide a rich shell environment for other operating systems as well as to provide a hostable scripting engine for rich applications. The user experience should be seamless for people who are used to Windows version of PowerShell. The scrips, cmdlets and providers should runs AS-IS (if they are not using Windows-specific functionality). The rich applications that host PowerShell should run on any other operating system AS-IS. Secondary goal: the scripts should run across the machines and different OS’s seamlesly (but following all the security guidelines).

Environment

The current implementation of Pash is written using pure .Net 2.0. It compiles on VS 2008 as well as on Mono. So all the developers can choose the environment that fits their needs and preferences. The produced assemblies can be executed “right out of the box” on Windows, Linux, Mac (or others) without any additional recompilation. Note: for Windows Mobile and Windows CE the produced code should be recompiled against the .NET Compact Framework.

Jeffrey Snoversaid

I can’t tell you how many customers have been asking for this.
I think it will be quite popular.
We should figure out how to make sure that you are totally in synch with PS so that we don’t drive customers crazy.

I love PowerShell (PoSh). It gives me (most of) the power of Perl, plus the DotNet framework(library), plus easy discoverability and debugging since all variables in PowerShell are objects with properties and methods.
Now PowerShell is available for M…

anne O'nimesaid

anonymoussaid

Have you considered what 11 and 14 respectively is in hexidecimal? 11h = 17d and 14h = 20d so 11..14 (hex) will return 17, 18, 19 and 20 (decimal) as shown in the screenshot. One could argue that if input is in hexidecimal output should also be in hexidecimal unless something else is stated.

There has been a lot of talk at the SharpOS project on wanting Powershell, but all of us being much to busy to start yet another side-project. (And Powershell is a beast all on its own!)

And it appears that someone not only has done it, but is doing it well. I can’t wait to try it out on my Linux VM, and I’m even more excited at the possibilities of integrating it into our 100% C# OS, down the road.

Vladekksaid

The project is not really dead. It moves forward with a very slow speed, mainly because there is almost to none interest in the project from the community (both M$ and Mono). I’ve received a couple of initial requests to join, but the people have disappeared.

P.S. Actually “ls” is working – check the config file for correct aliases.

FromTheDeepNetsaid

This is an exciting idea, but letting it get released as version “1.1” when ls / Get-ChildItem isn’t even working is extremely frustrating and obviously a bit premature. Hit-the-marketing-deadlines-and-fix-it-after-it-ships is supposed to be the Microsoft / proprietary way, not the open source way.

Vladekksaid

The project is not really dead. It moves forward with a very slow speed, mainly because there is almost to none interest in the project from the community (both M$ and Mono). I’ve received a couple of initial requests to join, but the people have disappeared.

That’s sad. But if situation is such, I agree you should apply your skills where they will be needed and used more.

As for “ls” – I can’t change directory with “cd”. Prompt changes as if was changed, but nothing else happens – ls or Get-ChildItem always outputs nothing.

Tomsaid

vbman09said

I hope you will continue the project – its definitely worth. The Mono Community is probably to small to notice or not too much interested in admin stuff or in another interpreted language. And for most Windows admins cross plattfom is either not an issue or they already use Bash, Perl etc. May be you should move the project to CodePlex (I’ll doubt you get any Linux dev do some work on another scripting language for Linux – or join Karl Prosser and bring a “moveable PowerShell” to a new level;).

Victorsaid

Could you please write a few words about how to compile the sources? I want to compile the project with Mono Develop 2.0 but it looks like a Gold Parser-Library is missing? Could please provide a link to the downloadsite of this library.

[…] but that’s probably more due to my lack of experience than anything else. There’s an Open Source implementation of Powershell I’ve been thinking of checking out, it doesn’t implement the Windows specific cmdlets, […]

Johnsaid

David Noblesaid

Are you still working on this? I ask because I see very little activity on Source Forge and just three comments; one that simply says, “good idea.” By the way, I agree with that comment, but as a former Microsoft employee, I’d expect some talk, but not much cooperation on this.

That’s not to say the PowerShell team wouldn’t like to see PowerShell become a cross-platform management tool, but rather that cross-platform projects are very difficult to start, manage and support from inside Microsoft given ship pressures. Where are you currently headed with this?

[…] an automation tool for Powershell, a Windows command line shell . There is a limited cross platform implementation of Powershell out in the wild but with limited functionality, so moving forwards its either writing a nant build script, investigating the aforementioned PASH […]

[…] which is an automation tool forPowershell, a Windows command line shell . There is a cross platform implementation of Powershell out in the wild but with limited functionality, so moving forwards its either writing a nant build script, investigating the aforementioned […]

Is there some news for PASH ? I need to know if PASH is able to run a V2 PowerShell script. I have’nt details about it support. Please, could you help me or tell me an other way to run a V2 PowerShell script on linux ?