n1k0/casperjs — pull request #303 by owenmartin (2012-12-04 19:34:37+00:00)
Title: Powershell replacement for casperjs on Windows

The implementation of the batch file is lacking in proper support for parameters. This is not so much a limitation of the casperjs.bat file, as it is of batch files in general.
A better alternative is to use Powershell. It has more options and almost certainly has a brighter future than batch scripts.

Powershell does support arguments out of the box, but these are to be prefixed with a single -, rather than --. The solution is either;
*roll your own parser that handles --
*alter the documentation for casperjs to note windows users should use -

I would prefer the first, however this goes against the default implementation of powershell, and leads to some messy code.

Either way, this will handle command parameters better than the batch script, but will not handle spaces in paths (even with quotes).

A design decision needs to be made on native support for powershell, with its windows quirks, trying to write our own parser in powershell for -- arguments, or damn it all and write a teenie tiny .NET app that will handle it all nicely?