When I try to use "WinSCP scripting interface .NET wrapper" from Visual Basic 6 or VBA, all I get is the classnames without any functions or properties. All I can see is the enumerations and the events of the session-class.
Using newest winscp v18.104.22.16852 and winscp-dll v22.214.171.12452.
Using "OleView.exe/View Typelib..." I can see that all interfaces in the TLB-File are blank (no methods or properties), such as "_Session" (WinSCP.Session) and "_SessionOptions" (WinSCP.SessionOptions).
The only interface containing methods is "ISessionEvents" (WinSCP.ISessionEvents).
Without this info I have to guess funtions, parameters and return values in vb6/vba.
Is this meant to be this way or is this a bug?