On 12/27/06, Tim Hill <drtimhill@comcast.net> wrote:
> No, I realize what you are doing. However, WSH scripts are not
> executed "directly" by the Windows shell; they are run by the
> cscript.exe or wscript.exe Windows applications. So when you run
> "foo.wsf" you are really running cscript.exe (or wscript.exe) and
> passing it "foo.wsf" as a command-line argument. This magic is
> handled by the Windows shell with the help of the search path and
> some environment variables. If either the search path or the
> environment is wrong the magic will break and the script won't run.
>
> You probably want to explicitly specify everything on the command
> line. Something like:
>
> c:\Windows\system32\cscript.exe //B //Nologo MyScript.wsf my-arguments
OK, but the question is *how* does this get accomplished? The
Subversion source looks for .wsf files for pre-commit hooks and runs
them the same way it runs .exe, .bat and .cmd files. .WSF is listed in
the system environment variable %PATHEXT% but when I have
pre-commit.bat dump that variable to a text file, it is populated as I
expect (not blank).
Has anyone successfully invoked a .WSF hook script yet?
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Dec 28 14:39:31 2006