Remove sourceFullPath from Unix FileSystem.MoveDirectory exception

[steveberdy]

Summary

Removes the sourceFullPath argument from the exception thrown when a destination file path for Directory.Move has a parent that doesn't exist in Unix. This matches the functionality of Windows. The results should be more consistent and less confusing exceptions from the Directory.Move method on both Unix and Windows platforms.

For reference, see the first possible solution for this problem #50833 (comment):

I see 2 possible solutions:

• Remove the path from the error message of the exception, as done on Windows side.
• Add extra checks (on Windows and Unix sides) to ensure the parent (destination) directory exists.

Other minor fixes

• Typos in documentation fixed

Fixes#50833

[ghost]

Tagging subscribers to this area: @dotnet/area-system-io
See info in area-owners.md if you want to be subscribed.

Issue Details

---

Summary

Removes the sourceFullPath argument from the exception thrown when a destination file path for Directory.Move has a parent that doesn't exist in Unix. This matches the functionality of Windows. The results should be more consistent and less confusing exceptions from the Directory.Move method on both Unix and Windows platforms.

For reference, see the first possible solution for this problem (#50833 (comment)):

I see 2 possible solutions:

• Remove the path from the error message of the exception, as done on Windows side.
• Add extra checks (on Windows and Unix sides) to ensure the parent (destination) directory exists.

Other minor fixes

• Multiple if-statements were condensed to one switch, making code more performant
• Typos in documentation fixed

Fixes #50833

Author:	steveberdy
Assignees:	-
Labels:	area-System.IO
Milestone:	-

[stephentoub]

Multiple if-statements were condensed to one switch, making code more performant

For reference, not really. The compiler's still going to generate cascading ifs, similar to the original source code:
sharplab

[stephentoub]

Thanks.