>> -----Original Message-----
>> From: Shawn Talbert [mailto:stalbert_at_exploreconsulting.com]
>>
>> I hate the inefficiency of the
>> launch-cmd.exe-then-launch-PS.exe-then-your-script.
>>
>> When I looked into this, I seem to recall it was a limitation
>> of the portable library svn uses - it does not launch the
>> hook scripts via the Windows shell, so just adding a file
>> association won't work. At least I think that was the issue...
>>
>> In any case, we currently just write our scripts in C# and
>> compile them.
>> This works pretty well since compilation is trivial and the
>> scripts execute quickly. Also nice having the full richness
>> of C# at hand (part of that richness is one reason PowerShell
>> would be attractive over other scripting
>> technologies)
> ------8<------------
>
> I totally agree. When evaluating Subversion, I wrote a C# command-line
> app to act as a pre-commit hook, and it worked like a charm. In my
> case, it called the svn dos commands. I believe there is an API
> available (did you use it, and if so, where can I get it?) that takes
> out the shell overhead. With just a little extra work, I can make this
> one executable configuratble to the extreme.
>
> --
> David
True... but we're developing this environment and want to leave it as open
as possible (all our collegues must be able to script it). That means that
I'm stuck with using the CMD file... Or writing a hook that executes the
powershell script. To leave it as open as possible, the CMD script would
be the best choice.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-01-17 15:03:16 CET