![]() I have a ton of scripts that I need to move over from me manually copying a data file in place before running the script to the script going out and grabbing the data file via SFTP. However, that brings me to where I'm at today. I am the one who messed up and didn't included the executable with the assembly in my script folder, after all. ![]() All told, that should have been expected of course. NET Core version - Everything worked just fine for a while until I updated my installed version of WinSCP from 5.19 to 5.19.2 - At that point the script stopped working and started yelling about an assembly mismatch from the executable. NET 4.0 version of winscp.dll, leaving only the. From there I had some reading comprehension issues (ie, I assumed things like a dummy) and inadvertently deleted the bundled winscp.exe file and the. NET assembly, I downloaded and extracted the assembly into the same folder as the script. When I had only a single script using the. NET Core version of the assembly with the software by default. Ultimately things would be super simple if they'd just include the. NET 4.0 (meaning it doesn't work with PowerShell 7, only PowerShell 5). ![]() dll file located in C:\Program Files (x86)\WinSCP is the version that's compatible with. WinSCP is installed on my machine, but as I said I'm using PowerShell 7 and the. I'm interested in how others are solving the same problem. I ran into a small issue that I was able to resolve recently with an automated workflow I created. I'm about to embark on writing a bunch of PowerShell 7 scripts that will use SFTP.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |