v

FTPTask Support

FTPTask version Issue Description Status
1.0.85.41 FTPTask ignores <put> elements <ftp> task successfully logs into the remote server and lists the directory contents, then disconnects without executing any transfers. Under Investigation

Sample Script

<?xml version="1.0" encoding="utf-8" ?>
<project name="v108541a" default="testput" >

   <target name="testput">
      <connection id="myconn"
                  server="naha" username="anonymous" password="ftptask@spinthemoose.com" />
      <ftp connection="myconn"   
           verbose="true"
           localdir="c:\dev\nantftptask"
           remotedir="mirrors\test"
           showdironconnect="true"
           logfiles="true" >

         <put type="ascii" update="true">
            <include name="*.html" />
        
</put>
      </ftp>
   </target>

</project>

back to top

NAnt Logging Output

[ftp] Connecting to 'ftp.xxxx.com' as 'YYYY' ...
WARNING: 'edtftp.log.level' not found - logging switched off
[ftp] + Changing remote directory to 'clients.xxxx.com/wwwroot/yyy'
[ftp] Remote Directory Listing:
[ftp] + : 01-20-05 02:04PM <DIR> contactus
[ftp] + : 12-21-04 05:21PM <DIR> css
[ftp] + : 01-25-05 02:45PM <DIR> docs
[ftp] + : 10-19-04 01:30PM <DIR> footer
[ftp] + : 12-21-04 04:45PM <DIR> homepage
[ftp] + : 01-25-05 02:45PM <DIR> images
[ftp] + : 01-24-05 06:39PM 4476 index.html
[ftp] + : 01-17-05 12:31PM 807 spacer.gif
[ftp]
[ftp] Disconnecting from 'ftp.xxxxx.com'

back to top

Developer Details

The prj://Tasks/FTPTask.cs:InitializeTask method uses an XPath expression to select all <get> and <put> children of the <ftp> task. For some reason, the XPath expression that worked when I released v1.0.85.41 has stopped working.

Of course, i've also installed a new hard drive and reinstalled all my software, so i may be having config problems, but that doesn't explain why other users are having trouble. Has anyone been able to get this task working?

I'll spend more time on this as I'm able. In the meantime, support note can at least point other developers in the right direction.

back to top

Possible Solution

One user reported an xmlns attribute in his project element. When he removed that, this problem disappeared...

back to top