Differences

This shows you the differences between the selected revisions of the page.

2012-07-01 2012-07-01
seo (Petr) seo (Petr)
Line 54: Line 54:
To automate file upload use scripting command ''[[scriptcommand_put|put]]'' or .NET assembly method ''[[library_session_putfiles|Session.PutFiles]]''. To automate file upload use scripting command ''[[scriptcommand_put|put]]'' or .NET assembly method ''[[library_session_putfiles|Session.PutFiles]]''.
-===== Upload/Download Buttons =====+===== Buttons for File Upload·/ File Download =====
In [[ui_commander|Commander interface]] you can use toolbar with Upload/Download buttons to transfer files. You will want to use these particularly, if you want to transfer files, without having the [[ui_file_panel|panel]] with source directory active. In [[ui_commander|Commander interface]] you can use toolbar with Upload/Download buttons to transfer files. You will want to use these particularly, if you want to transfer files, without having the [[ui_file_panel|panel]] with source directory active.
===== [[unc]] Uploading Files From UNC Paths (Network shares) ===== ===== [[unc]] Uploading Files From UNC Paths (Network shares) =====
While WinSCP cannot browse UNC paths (network shares) in local [[ui_file_panel|panel]] of [[ui_commander|Commander interface]], it can upload files from there. You can [[task_upload#dragdrop|drag]] the files from Windows Explorer or another application, you can use UNC paths in [[scripting]], or use any other mean of uploading as described on this page. While WinSCP cannot browse UNC paths (network shares) in local [[ui_file_panel|panel]] of [[ui_commander|Commander interface]], it can upload files from there. You can [[task_upload#dragdrop|drag]] the files from Windows Explorer or another application, you can use UNC paths in [[scripting]], or use any other mean of uploading as described on this page.

Last modified: by Petr