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: BitFlipper **
To reproduce, simply try to download or upload a file whose path starts with "~".
Comments: ** Comment from web user: BitFlipper **
That is true, however there are places where SSH.Net appends the WorkingDirectory to any path that doesn't start with '/'. At a minimum it should consider a path starting with '~' as an absolute path and not a relative path.
Take a look at SftpSession.GetFullRemotePath to see how it will convert "~/somedir" to "/workingdir/~/somedir".