Thats great news! :) Thanks Martin!
- daffyd
Post a reply
Topic review
- martin
Re: Synchronization preview support for .NET assembly
There actually is
https://winscp.net/eng/docs/library_session_comparedirectories
Session.CompareDirectories:
https://winscp.net/eng/docs/library_session_comparedirectories
- daffyd
Synchronization preview support for .NET assembly
Hi good folks of the WinSCP community,
I've been trying to figure out how to preview synchronization changes with the .NET assembly. According to this bug tracker it should already be closed and supported, but i cannot for the life of me figure out how.
Martin posted a great solution for non-recursive compare here, which i guess could be turned into a recursive version with not too much work. However it would simply the scripting greatly to have this feature natively supported, as it now is for scripting with the -preview parameter.
Ciantic proposed creating this as a seperate function call (Session.CompareDirectories) rather than expanding on SynchronizeDirectories, which sounds like a good idea.
So, am I missing out on something? Is this feature still missing for .NET assembly? Is it still being worked on? Or has it been rejected for reasons not mentioned in the bug tracker?
I've been trying to figure out how to preview synchronization changes with the .NET assembly. According to this bug tracker it should already be closed and supported, but i cannot for the life of me figure out how.
Martin posted a great solution for non-recursive compare here, which i guess could be turned into a recursive version with not too much work. However it would simply the scripting greatly to have this feature natively supported, as it now is for scripting with the -preview parameter.
Ciantic proposed creating this as a seperate function call (Session.CompareDirectories) rather than expanding on SynchronizeDirectories, which sounds like a good idea.
So, am I missing out on something? Is this feature still missing for .NET assembly? Is it still being worked on? Or has it been rejected for reasons not mentioned in the bug tracker?