Differences
This shows you the differences between the selected revisions of the page.
| 2015-02-11 | 2015-02-18 | ||
| windows sdk is in 32-bit program files + tags (martin) | 5.7 Executable winscp.exe is included in .NET assembly package. (martin) | ||
| Line 1: | Line 1: | ||
| ====== Downloading and Installing WinSCP .NET Assembly ====== | ====== Downloading and Installing WinSCP .NET Assembly ====== | ||
| - | ===== Downloading ===== | + | ===== Downloading and Installing ===== |
| - | [[library|WinSCP .NET assembly]] is available in a separate package named ''winscpXXXautomation.zip'' on [[&download|WinSCP download page]]. Follow the //%%.NET assembly/COM library%%// link.· | + | [[library|WinSCP .NET assembly]] is available in a package named ''winscpXXXautomation.zip'' on [[&download|WinSCP download page]]. Follow the //%%.NET assembly/COM library%%// link. |
| - | To use the assembly, you need to have WinSCP [[installation|installed]] (or download the [[portable|portable package]]). You have to use the same version of the assembly as your version of WinSCP. | + | ===== [[executablepath]] Installed Binaries ===== |
| - | ===== Installing ===== | + | The package includes the assembly itself (''winscpnet.dll'') and a required dependency, WinSCP [[executables|executable]] ''winscp.exe''. |
| - | WinSCP .NET assembly interacts with WinSCP ''[[executables|winscp.exe]]''. By default it looks for the ''winscp.exe'' in the same folder, where the assembly is stored. For that reason, you should extract the package into the same folder, where you have WinSCP installed/extracted. You can also copy all binaries, ''winscp.exe'' and ''winscpnet.dll'', into separate folder. | + | |
| - | ==== [[executablepath]] Installing to Alternative Location ==== | + | The binaries interactive with each other and must be kept in the same folder for the assembly to work. In rare situations this is not possible (e.g. when [[library_install#gac|installing the assembly to GAC]]), make use of ''[[library_session#properties|Session.ExecutablePath]]'' property to force the assembly to look for the ''winscp.exe'' in a different location. |
| - | If you cannot store the assembly into the same folder, you can alternatively make use of ''[[library_session#properties|Session.ExecutablePath]]'' property to force the assembly to look for the ''winscp.exe'' in a different location. | + | |
| ==== [[vs]] Using from Visual Studio or other Development or Runtime Environment ==== | ==== [[vs]] Using from Visual Studio or other Development or Runtime Environment ==== | ||
| Line 29: | Line 27: | ||
| In special cases, you may need to install the assembly into Global Assembly Cache (%%GAC%%), particularly to use it from [[library_ssis|SSIS]]. | In special cases, you may need to install the assembly into Global Assembly Cache (%%GAC%%), particularly to use it from [[library_ssis|SSIS]]. | ||
| - | When you install the assembly to %%GAC%%, you need to use it, as if it is [[#executablepath|installed to alternative location]]. | + | When you install the assembly to %%GAC%%, you need to [[#executablepath|configure a path to WinSCP executable]]. |
| ==== On Development Machine ==== | ==== On Development Machine ==== | ||