Post a reply

Add an Attachment

If you do not want to add an Attachment to your Post, please leave the Fields blank.

(maximum 10 MB; please compress large files; only common media, archive, text and programming file formats are allowed)


Topic review


No combination of parameters caused the synchronize command to behave this way:

- Leave alone remote files not present locally
- Upload local files that do not exist remotely
- Resume remote files where the local copy is larger
- Skip remote files where the local copy is the same size

I tried many combinations and could sometimes satisfy a set of those requirements but never all.

What does it mean "doesn't seem to correctly resume or skip"?

As a script at least using, synchronize doesn't seem to correctly resume or skip regardless of options set when using FTPS. I had started there but gave up using it when I found success with put. Does it behave differently here?

.NET assembly equivalent of -neweronly for PutFiles()?


I've been experimenting with WinSCP for uploading to an FTPS file server. Using a script file, I can upload files and automatically resume or skip existing files as is appropriate using:

put <localpath> <remotepath> -resume -neweronly

However, I've been trying to replicate this behavior using the .NET assembly and have not found an equivalent to the -neweronly flag available in Neither the session options class nor transfer options class seems to have criteria for when to resume.

Is this feature available? Some files I'm uploading are hundreds of megabytes, so this could potentially consume a large amount of time for data which is already on the server.