[Rob-Hague]

And populate it in more places (where the error could not relate to any other path).

[drieseng]

@Rob-Hague, what's the rationale for this? Looking at thus on cell phone, so I surely missed the big picture.

[Rob-Hague]

Yes sorry I should have said:
Looking back through old issues, there are lots of complaints of unspecific exceptions in the SFTP layer. There is not a lot we can do about it, especially when the server sends just "Failure" code, but #1716 in 2025.1.0 improved it slightly by adding a base SftpException class with the SFTP error code, and added Path property to SftpPathNotFoundException. Here I figured Path can be provided in more cases where it would not be considered ambiguous, so the property can be moved to the base class.

This is not considered a breaking change in .NET guidelines: https://learn.microsoft.com/dotnet/core/compatibility/library-change-rules)

✔️ ALLOWED: Moving a member into a class higher in the hierarchy than the type from which it was removed