Well, it's all moot now since I replaced WinSCP with SSH.NET, which is a much better SSH solution. I wasn't the one picked WinSCP for SFTP upload/download in ASP.NET anyway; that was my predecessor.
WinSCP.EXEso it doesn't end up in the web site root folder. The one in
~/binis all I need.
WinSCP.Sessionto make sure the WinSCP .NET assembly is linked in (probably not needed)
Content/C_C/Users/<username>/Source/Repos/<git repository name>/<project name>/obj/Release - Production/Package/PackageTmp/WinSCP.EXE
Content/C_C/Users/<username>/Source/Repos/<git repository name>/<project name>/obj/Release - Production/Package/PackageTmp/bin/WinSCP.EXE
web.config, etc. The second path contains the compiled DLLs.
WinSCP.targetsfile looks OK:
WinSCP.exein the zip file. In:
winscp.exe– in the root. And there's no
binfolder. Though I have VS 2019. Did something change?
/bindirectory in the publish zip file. How do I keep it out of the root folder and just leave it in