MS Build Community Tasks - SVNCHECKOUT: can't find svn.exe even though it is in PATH

Note: this question app开发者_如何转开发lies to using the MSBUILDCOMMUNITYTASKS add-in for MSBUILD. Specificly the functionality of SVNCHECKOUT and its inablity to find the svn.exe file even when it is located in a directory included in the PATH environment variable.

So I might be missing something obvious here but help at this point would be greatly appreciated.

I have some pretty sophisticated msbuild scripts that are running fine on 3 different Windows XP systems (and have been for 2 years).

I'm in the process of porting them to run on 64bit windows currently on a Windows 2008 Server. I'm working through all of the differences in directories and me having used the wrong environment variables in the past that made stuff not work as I moved to a new operating system.

But I am stuck now with the SVNCHECKOUT command giving me this error:

C:\Program Files (x86)\MSBuild\somedirectory\someprojfile.proj(44,5): error MSB4018: The "SvnCheckout" task failed unexpectedly.\r
C:\Program Files (x86)\MSBuild\somedirectory\someprojfile.proj(44,5): error MSB4018: System.Exception: Could not find svn.exe.  Looked in PATH locations and various common folders inside Program Files.\r

the following directory IS in the PATH:

C:\Program Files (x86)\CollabNet\Subversion Client\

and I can run svn.exe from there

I'd be OK using the SVNCLIENT directive to point to where the file is, but I've had no luck doing that.

Version wise I'm using

msbuild: Framework v3.5

msbuildcommunitytasks: nightly build from 12/10/2008 (it fixed bugs that kept me from using the "stable"version)

os: windows server 2008R2 SP1

If you are running a batch script, I would set the path in the batch script first

set path=$path;'new path'; <--- please check this syntax as i used it a long time ago

If you are running it from Visual Studio environment, make sure it does uses the Windows Path variable, if not, include your path there somehow.

For a quick debugging, you can always use exact path and if that works, then work on path variable. It is possible that something else could be wrong.

Well, it was clearly a bug in MSBUILDCOMMUNITYTASKS

I installed the nightly build create 2011-06-27 and it works now. This always makes me nervous with their software because it APPEARS to not be supported, but up to this point, I'll give the developers credit--they've yet to break anything I needed with newer code.

version that works:
Version: 1.3.0.514 Date: 6/27/2011