Thank You!
Excellent. Generating the assembly from the Client Application worked perfectly.
Thank you again!
Thank you again!
- msdev7807
Post a reply
Topic review
- martin
Re: WinSCP Settings Profile Verses Setting them in .Net Assembly Properties
See https://winscp.net/eng/docs/faq_hostkey#automation
Though you better have the WinSCP GUI generate a complete code template for you:
https://winscp.net/eng/docs/ui_generateurl#code
Though you better have the WinSCP GUI generate a complete code template for you:
https://winscp.net/eng/docs/ui_generateurl#code
- msdev7807
WinSCP Settings Profile Verses Setting them in .Net Assembly Properties
In the WinSCP client, I have a defined connection setup that works fine. I am trying to mirror the same steps through the .NET assembly. I looked at the WinSCP .INI file and the SSH setting, but it seems to be encrypted some how. It doesn't match the ssh- rsa2048 xx: xx: xx: xx: format that I need to properly connect. I have tried .GiveUpSecurityAndAcceptAnySshHostKey = True but that didn't work. In a previous FTP client that we used, you could load the profile directly and it mapped to all of the various FTP object properties. I know I can contact the site owner and request a new SSH key. But since it working correctly in the client, I was hoping to either use the connection profile, or derive the SSH Key... I noticed the Preferred SFTP Protocol Version is set to 6... For example.
Any ideas?
Any ideas?