identify IOException?

  • Thread starter Thread starter Sergei Shelukhin
  • Start date Start date
S

Sergei Shelukhin

Hi. I catch IOException and want to separate the case when I receive
"The process cannot access the file because it is being used by
another process" error from other possible IOException-s. Checking the
message text is not an option because the app is multilingual and
might use a .NET version that is not English.

Is there any way to do it, some error code or something?
 
Sergei Shelukhin said:
Hi. I catch IOException and want to separate the case when I receive
"The process cannot access the file because it is being used by
another process" error from other possible IOException-s. Checking the
message text is not an option because the app is multilingual and
might use a .NET version that is not English.

Is there any way to do it, some error code or something?
Click to expand...


Call Marshal.GetLastWin32Error in your catch handler, and check the Win32
error code.

Willy.
 
That's depending a little bit too much on an implementation detail, IMO.
Granted, file access is probably ALWAYS going to be done through the
P/Invoke layer, but the assumption that there will be no calls to the
P/Invoke layer between the throwing of the exception and the next call to
GetLastWin32Error is a brittle suggestion, at best.

What the OP should really do is make the call to CreateFile himself, and
interpret the error code (if there is one).
 
If this is your concern just call Marshal.GetHRForException which returns
the HResult associated with the Exception thrown, mask the highest 16 bits
off and you have the Win32 error code.

Willy.


Nicholas Paldino said:
That's depending a little bit too much on an implementation detail,
IMO. Granted, file access is probably ALWAYS going to be done through the
P/Invoke layer, but the assumption that there will be no calls to the
P/Invoke layer between the throwing of the exception and the next call to
GetLastWin32Error is a brittle suggestion, at best.

What the OP should really do is make the call to CreateFile himself,
and interpret the error code (if there is one).

--
- Nicholas Paldino [.NET/C# MVP]
- (e-mail address removed)

Willy Denoyette said:
Call Marshal.GetLastWin32Error in your catch handler, and check the Win32
error code.

Willy.
Click to expand...
Click to expand...
 
Back
Top