torix wrote:

1. SynchronizeFiles failing/exiting when encountering locked files in a sequence of multiple files.
We had some discussions on possible (temporary?) workarounds where one was to enumerate the files and then "for-each" process each file. We agree that this provided robustness but it resulted in a performance-drop in the negative direction. Has this been handled in later versions of the .Net library prior to version 5.7.6.0?

No change there.

2. Although not a bug but when moving files, the root folder is deleted as well. For us, the root folder is often a Windows share (e.g. E:\DATA\OUR_SHARE\), but we want to keep that one afterwards. We tried using the filemask in some creative ways but found that it just resulted in the source folder files where omitted but sub folders and file content being moved. Any news after 5.7.6.0 build? Could this be implemented through a parameter e.g. "PreserveRootFolder" in the library to make this handling optional? New creative ways to solve it with a file mask it will be ok too.

This is about GetFiles, not about synchronization, right?

You just need to call it like:

session.GetFiles("/remote/path/*", @"C:\local\path\", true);

Not like:

session.GetFiles("/remote/path", @"C:\local\path", true);

Hi,

This is a summary of two topics that we had some discussions on 6+ months ago. Since then a long list of new builds has appeared (not tested) but I would appreciate an update on the following topics:

1. SynchronizeFiles failing/exiting when encountering locked files in a sequence of multiple files.
We had some discussions on possible (temporary?) workarounds where one was to enumerate the files and then "for-each" process each file. We agree that this provided robustness but it resulted in a performance-drop in the negative direction. Has this been handled in later versions of the .Net library prior to version 5.7.6.0?

2. Although not a bug but when moving files, the root folder is deleted as well. For us, the root folder is often a Windows share (e.g. E:\DATA\OUR_SHARE\), but we want to keep that one afterwards. We tried using the filemask in some creative ways but found that it just resulted in the source folder files where omitted but sub folders and file content being moved. Any news after 5.7.6.0 build? Could this be implemented through a parameter e.g. "PreserveRootFolder" in the library to make this handling optional? New creative ways to solve it with a file mask it will be ok too.

Best regards