Differences
This shows you the differences between the selected revisions of the page.
| 2012-03-22 | 2012-05-31 | ||
| no need to register the assembly if not used a com library (martin) | com note with gac does not make much sense (martin) | ||
| Line 11: | Line 11: | ||
| 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), 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). |
| ===== [[registering]] Registering for COM ===== | ===== [[registering]] Registering for COM ===== | ||