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 **
To clarify why I'm saying this is a regression...
In the previous beta I added the following into SftpSession.GetFullRemotePath to fix the issue:
```
if (string.IsNullOrEmpty(path) || path[0] == '~')
{
return path;
}
```
I did the same with the latest beta code but this time my fix did not resolve the issue. So the latest beta must have some new path manipulation code somewhere else that also doesn't handle '~' properly.
