Forum Discussion
Philip_Baird
12 years agoCommunity Hero
Hi Paul, sorry I haven't replied sooner, I was on holiday on Friday :)
The WinSCP .Net Assembly is basically a wrapper around the WinSCP executable and a Session maintains a non shell, background Process (you can see how it works using a decompiler such as ILSpy or dotPeek).
Therefore, if you use the Assembly, WinSCP will need to be installed (exactly as if you were driving WinSCP via the GUI) and the Assembly needs to reside in the same directory as the WinSCP executable (on my machine this is C:\Program Files (x86)\WinSCP). You will also need to consider the version of WinSCP installed as the Assembly requires a leter version.
One other thing is that like all .Net Assemblies, the WinSCP Assembly needs to be able to access all its referenced Assemblies. I found the easiest way to do this was to register the Assembly in the GAC rather than trying to indentify the referenced Assemblies and manually placing them where the WinSCP Assembly could find them.
Hope this helps,
Phil
The WinSCP .Net Assembly is basically a wrapper around the WinSCP executable and a Session maintains a non shell, background Process (you can see how it works using a decompiler such as ILSpy or dotPeek).
Therefore, if you use the Assembly, WinSCP will need to be installed (exactly as if you were driving WinSCP via the GUI) and the Assembly needs to reside in the same directory as the WinSCP executable (on my machine this is C:\Program Files (x86)\WinSCP). You will also need to consider the version of WinSCP installed as the Assembly requires a leter version.
One other thing is that like all .Net Assemblies, the WinSCP Assembly needs to be able to access all its referenced Assemblies. I found the easiest way to do this was to register the Assembly in the GAC rather than trying to indentify the referenced Assemblies and manually placing them where the WinSCP Assembly could find them.
Hope this helps,
Phil