Differences
This shows you the differences between the selected revisions of the page.
| 2019-04-16 | 2019-08-18 | ||
| 5_14_automation anchor (martin) | DisableVersionCheck will not be obsoleted (martin) | ||
| Line 59: | Line 59: | ||
| * 5.12.1: ''Session.ScanFingerprint'' has a new mandatory ''algorithm'' parameter. To keep the previous behavior use ''%%MD5%%'' as a parameter value (though for new development, use ''%%SHA-256%%''). | * 5.12.1: ''Session.ScanFingerprint'' has a new mandatory ''algorithm'' parameter. To keep the previous behavior use ''%%MD5%%'' as a parameter value (though for new development, use ''%%SHA-256%%''). | ||
| * 5.10: When executing script file or script commands provided on command-line, default reconnect time is set to 120 seconds, if not limited yet by configuration. Previously, WinSCP tried to reconnect indefinitely by default. To revert to the previous behavior, in scripting use ''option reconnecttime 0'', in .NET assembly use ''Session.ReconnectTime = TimeSpan.MaxValue''. | * 5.10: When executing script file or script commands provided on command-line, default reconnect time is set to 120 seconds, if not limited yet by configuration. Previously, WinSCP tried to reconnect indefinitely by default. To revert to the previous behavior, in scripting use ''option reconnecttime 0'', in .NET assembly use ''Session.ReconnectTime = TimeSpan.MaxValue''. | ||
| - | * 5.10: Change: Deprecating ''Session.DisableVersionCheck''. Always use the same version of WinSCP and WinSCP .NET assembly. | ||
| * 5.9.1: ''[[library_session_enumerateremotefiles|Session.EnumerateRemoteFiles]]'' does not throw when reading subdirectory fails. To capture errors, use the ''[[library_session_failed|Session.Failed]]'' event. | * 5.9.1: ''[[library_session_enumerateremotefiles|Session.EnumerateRemoteFiles]]'' does not throw when reading subdirectory fails. To capture errors, use the ''[[library_session_failed|Session.Failed]]'' event. | ||
| * 5.8.3: A complete remote error message is stored into a single instance of ''SessionRemoteException'', instead of separating error details into an inner exception. This should have any impact only, if your code checks for specific error message in inner exception. This is not recommended though. | * 5.8.3: A complete remote error message is stored into a single instance of ''SessionRemoteException'', instead of separating error details into an inner exception. This should have any impact only, if your code checks for specific error message in inner exception. This is not recommended though. | ||