Generate Session URL/Code/Transfer Code Dialog

Use the URL tab to generate a session URL or a file URL. The tab is not available when generating a file transfer code.

The generated URL always includes a protocol and a host name portions. Other parts can be included optionally.

Check the User name to include username into the URL. The option is not available when the dialog is opened from the Login dialog and the user name was not specified; or (rarely) when the current session did not require the user name.

Check the Password to include password into the URL. Make sure you protect an URL that includes the password appropriately. The option is not available when the dialog is opened from the Login dialog and the password was not specified; or when the current session does not use a password authentication; or when the password was not stored nor remembered.

Check the Initial directory to include an initial remote directory into the URL. When the dialog is opened from the Login dialog, Remote directory as specified on the Advanced site settings dialog is used. When opened from the main window, the current working remote directory is used. The option is not available when generating an URL for selected file(s) as a path to the file(s) is used instead.

Check the SSH host key to include an SSH host key fingerprint into the URL. The option is available for an SFTP and an SCP (SSH-based) sessions only. The option is not available, if no session was opened to the host as the host key is not known yet. Note that some (most) SSH clients need not understand a session URL that includes the host key fingerprint.

Check the WinSCP-specific to generate an WinSCP-specific URL. Note that you need to enable the option with the WebDAV protocol, if you want WinSCP to handle the URL, as WinSCP never registers for the http protocol.

Check the Save extension to include a save extension into the URL. As the extension is WinSCP-specific, the option WinSCP-specific should be selected along.

Check the Advanced settings to serialize all advanced site settings into the URL. As the generated syntax is WinSCP-specific, the option WinSCP-specific should be selected along.

The generated URL(s) is shown in the bottom box. When generating an URL for a site, only one URL is displayed. When generating an URL for a selected file(s), one URL per a file is displayed.

Use the Script tab to generate a WinSCP script template for the session or the file transfer.

The script will include:

• the open command with the session URL and all other switches needed to configure the session.
• (When generating a code for a session) a placeholder text to be replaced with commands.
• (When generating a code for a file transfer) the cd and lcd commands to navigate to the source and destination folders of the transfer and the put or get commands to actually transfer the files (with all needed switches to setup any non-default transfer settings).
  • If you had all files selected in the source panel, a code to upload all files from the source directory will be generated.
  • If you had only some files selected in the source panel, a code to upload only the selected files (but three at most) will be generated. If file names contain any file mask special characters, they will be escaped.
• the exit command to end the script.

Use the Format to select a format of the script to generate:

• Script file – Generates a script file template that you execute using the /script command-line switch.
• Batch file – Generates a Windows batch file (.bat) template that executes the winscp.com with the above commands, specified using the /command command-line switch. Additionally the batch file enables session logging using the /log switch and isolates the script run from a GUI configuration using the /ini=nul switch. At the end, the batch file checks WinSCP exit code to choose further actions to take; and propagates the WinSCP exit code to a batch file exit code using the exit /b command. Make sure you keep the exact format of the multi-line winscp.com command, as multi-line batch file commands are fragile.
• Command-line – Generates a command-line for the winscp.exe (but usable for winscp.com too) with the above commands, session logging and configuration isolation (see the previous point). The command-line is suitable for task managers of all kinds, like Windows Scheduler or SSIS. Depending on your requirements, you may want prepend the /console switch to make the script console visible, while the script is running.
• PowerShell script – Generates a PowerShell script file (.ps1) template that executes the winscp.com with the above commands, specified using the /command command-line switch. Additionally the script file enables session logging using the /log switch and isolates the script run from a GUI configuration using the /ini=nul switch. At the end, the script file checks WinSCP exit code to choose further actions to take; and propagates the WinSCP exit code to a script exit code using the exit keyword. The script additionally sets $PSNativeCommandArgumentPassing to “Legacy”, what is needed for PowerShell 7.3 and newer to be able to pass the arguments properly to WinSCP.1 Instead of running winscp.com, consider Using WinSCP .NET assembly from PowerShell.

In the Command-line (and possibly also in the Batch file), you should modify a path to a session log file in the /log switch.

The script will not include options to verify a host key or an untrusted certificate, if the session was not opened before yet. Open the session at least once, before generating the script.

You can click on script commands and switches and command-line switches to open their respective help pages.

Use the .NET assembly tab to generate a code template using WinSCP .NET assembly for the session or the file transfer.

The code will:

• Set up SessionOptions with all properties needed to configure the session.
• Create Session instance.
• Open the session using Session.Open
• (When generating a code for a session) Include a placeholder text to be replaced with calls to Session methods.
• (When generating a code for a file transfer) Transfer files using Session.PutFiles or Session.GetFiles. The TransferOptions class instance will be constructed and set up, if any non-default transfer settings are used. The OperationResultBase.Check method will be called on results of the methods to throw an exception on any error.
  • If you had all files selected in the source panel, a code to upload all files from the source directory will be generated.
  • If you had only some files selected in the source panel, a code to upload only the selected files (but three at most) will be generated. If file names contain any file mask special characters, the RemotePath.EscapeFileMask method will be called to escape them.
• Dispose the Session instance.

Use the Language to select a language to generate the template for. Available languages are C#, VB.NET and PowerShell.

The code will not set properties to verify a host key (SessionOptions.SshHostKeyFingerprint) or an untrusted certificate (SessionOptions.TlsHostCertificateFingerprint), if the session was not opened before yet. Open the session at least once, before generating the code.

You can click on classes, methods and properties to open their respective help pages.

Use Copy to Clipboard to copy generated URL(s) or code to a clipboard.

WinSCP GUI cannot be aware of path limitations of your server. So even if your server requires you to start in a specific folder, WinSCP will not generate a code that will start in that folder. You need to add that manually. See How to connect to a server that does not allow an access to the root path?