Post a reply

Options
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)

Options

Topic review

martin

Re: Generated Powershell code breaks if there is a space in the path

The space should not be a problem.

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

To generate the session 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.
fishermanrow

Generated Powershell code breaks if there is a space in the path

I have generated a Powershell script from inside the transfer options in WinSCP.

$session.GetFiles("/outbound/*", "C:\Users\Market 2\Desktop\Backoffice\Batch\Crunch\").Check()


The path has a space in it, Market 2, and Powershell keeps breaking at \Market. The white space in the path is the problem. Does anyone know a way around this without having to rename my root directory?