I would like to suggest implementing an enhanced scripting error handling. I want to be able for example to tell if an OPEN sftp command was successful or not.
This especially is very critical in our corporate environment. Let me explain why: if an user password has expired and he /she keeps trying to connect to the remote UNIX directory using our VB.net application, then the account locks and it may take a couple of days to unlock it. There are many steps to execute in the code, like moving, renaming files, etc. Not all of these steps can be checked for successful execution. I want to be able to stop execution at any time and display a meaningful error message.
It would be very useful to be able to display a message like "Authentication failed" or similar if an OPEN sftp command fails and also for every single WINSCP scripting command.
M.R. - Toronto