Post a reply

Before posting, please read how to report bug or request support effectively.

Bug reports without an attached log file are usually useless.

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


Re: Does WinSCP .NET assembly support multiline commands?

Please attach a full session log file showing the problem (using the latest version of WinSCP).

To generate log file, set Session.SessionLogPath. Submit the log with your post as an attachment. Note that passwords and passphrases not stored in the log. You may want to remove other data you consider sensitive though, such as host names, IP addresses, account names or file names (unless they are relevant to the problem). If you do not want to post the log publicly, you can mark the attachment as private.

Does WinSCP .NET assembly support multiline commands?


set -v; /opt/bin/cmd > /tmp/my.log <<!!

sent as:
"set -v; /opt/bin/cmd > /tmp/my.log <<!!\r\nLine1_CommandInput\r\nLine2_CommandInput\r\nquit;\r\n!!\r\n"

Is there any reason WinSCP would have trouble with this? I'm getting a 60 second wait and then "Terminated by user." SessionRemoteException

Also, is there a limit to the character length that can be sent via session.ExecuteCommand?