Differences

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

2018-12-20 2019-03-12
5.14.2 Bug 1706: Command-line switch /comregistration for inspecting and clearing broken COM registrations. (martin) guide_microsoft_azure_function_sftp (martin)
Line 21: Line 21:
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 [[#gac|install the assembly into Global Assembly Cache (GAC)]]. 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 [[#gac|install the assembly into Global Assembly Cache (GAC)]].
-You may want to add ''winscp.exe'' to your Visual Studio project, to have it copied to the //Output path// automatically (by setting file property //Copy to Output Directory// to //Copy if newer//). The //Build Action// should be automatically set to //Content//, what means that the file will be included when deploying your application (e.g. an ASP.NET web application or [[guide_microsoft_azure_webjob_sftp#consoleapp|Azure WebJob application]]).+You may want to add ''winscp.exe'' to your Visual Studio project, to have it copied to the //Output path// automatically (by setting file property //Copy to Output Directory// to //Copy if newer//). The //Build Action// should be automatically set to //Content//, what means that the file will be included when deploying your application (e.g. an ASP.NET web application, [[guide_microsoft_azure_webjob_sftp#consoleapp|Azure WebJob]] or [[guide_microsoft_azure_function_sftp|Azure Function]]).
Easier, than setting up the reference manually, is using [[#nuget|WinSCP NuGet package]]. Easier, than setting up the reference manually, is using [[#nuget|WinSCP NuGet package]].

Last modified: by martin