Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
If I call System.IO.File.Delete() and pass it a directory name I get UnauthorizedAccessException although the problem has nothing to deal with any kind of permissions and I guess InvalidOperationException would be much more suitable here.
Why is this specific exception being thrown? Is it a design fault or is there any reason for that?
No idea, but it smells like a design fault because the Directory.Delete has a different behavior that File.Delete. Directory.Delete will throw a DirectoryNotFoundException if the path actually refers to a file instead of directory. One would expect that the same kind of exception would be thrown in these two cases.