Differences
This shows you the differences between the selected revisions of the page.
| 2012-02-10 | 2012-02-16 | ||
| &future_feature (martin) | no winscp.com (martin) | ||
| Line 7: | Line 7: | ||
| ===== Installing ===== | ===== Installing ===== | ||
| - | WinSCP .NET assembly interacts with WinSCP [[executables|executables]] (''winscp.com'' and ''winscp.exe''). By default it looks for the executables 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.com'', ''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. |
| - | 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 executables 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 executables 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), e.g. when registering the assembly for COM. | + | 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), e.g. when registering the assembly for COM. |
| ===== [[registering]] Registering for COM ===== | ===== [[registering]] Registering for COM ===== | ||
| Line 26: | Line 26: | ||
| ===== Deploying ===== | ===== Deploying ===== | ||
| - | When deploying the assembly, make sure that WinSCP is installed along with the assembly on the target system and that WinSCP assembly can find the WinSCP executables. | + | When deploying the assembly, make sure that WinSCP is installed along with the assembly on the target system and that WinSCP assembly can find the ''winscp.exe''. |