Currently, SSH.NET considers remote directory names to be case sensitive, which they are not. Even on ODS-5 volumes, where file and directory names can be mixed case, they are not case sensitive. In other words, [FRED], [Fred], and [fred] are all the same directory.
The SSH.NET code, however, treats them as case-sensitive. If a directory on windows was originally synced in, say, lowercase, and then the case changes on Windows, subsequent syncs will fail because it will try to create a NEW directory matching the current case on Windows, but on VMS the directory already exists, and an exception is thrown.
Until the code is fixed, a workaround is to manually rename the folder on VMS at the same time as it is renamed on Windows.
Currently, SSH.NET considers remote directory names to be case sensitive, which they are not. Even on ODS-5 volumes, where file and directory names can be mixed case, they are not case sensitive. In other words, [FRED], [Fred], and [fred] are all the same directory.
The SSH.NET code, however, treats them as case-sensitive. If a directory on windows was originally synced in, say, lowercase, and then the case changes on Windows, subsequent syncs will fail because it will try to create a NEW directory matching the current case on Windows, but on VMS the directory already exists, and an exception is thrown.
Until the code is fixed, a workaround is to manually rename the folder on VMS at the same time as it is renamed on Windows.