Seems there are quite a few places where SSH.Net does not handle paths that start with "~" properly. This particular case is a regression in the latest beta since this used to work now no longer does.
To reproduce, simply try to download or upload a file whose path starts with "~".
Comments: ** Comment from web user: da_rinkes **
To reproduce, simply try to download or upload a file whose path starts with "~".
Comments: ** Comment from web user: da_rinkes **
AFAIK '~' is a shell feature.
WinSCP also can't handle $HOME, '~' and so on.