Differences
This shows you the differences between the selected revisions of the page.
| 2012-05-31 | 2012-05-31 | ||
| com note with gac does not make much sense (martin) | installing to gac (martin) | ||
| Line 9: | Line 9: | ||
| 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 ''winscp.dll'') into separate folder. | 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 ''winscp.dll'') into separate folder. | ||
| + | ==== [[executablepath]] Installing to Alternative 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. | 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. | ||
| Note that your runtime or development environment may copy the assembly into an another location. In that case you need to copy ''winscp.exe'' into that location too. E.g. If you reference WinSCP assembly from your project in Microsoft Visual Studio, it copies the assembly during build into the project //Output path// (e.g. ''<your_project_path>/obj/Debug''). Similar case is when you install the assembly into Global Assembly Cache (GAC). | Note that your runtime or development environment may copy the assembly into an another location. In that case you need to copy ''winscp.exe'' into that location too. E.g. If you reference WinSCP assembly from your project in Microsoft Visual Studio, it copies the assembly during build into the project //Output path// (e.g. ''<your_project_path>/obj/Debug''). Similar case is when you install the assembly into Global Assembly Cache (GAC). | ||
| + | |||
| + | ==== [[gac]] Installing to GAC ==== | ||
| + | If you want to install the assembly into Global Assembly Cache (GAC), particularly to use in from SSIS, use following command: | ||
| + | <code> | ||
| + | %WINDIR%\Microsoft.NET\Framework\v1.1.4322\gacutil.exe /i WinSCP.dll | ||
| + | </code> | ||
| + | |||
| + | When you install the assembly to GAC, you need to use it, as if it is [[library_install#executablepath|installed to alternative location]]. | ||
| ===== [[registering]] Registering for COM ===== | ===== [[registering]] Registering for COM ===== | ||