Closing SafeHandle

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

valentin tihomirov - 29 Oct 2007 16:21 GMT

The SafeFileHandle is an extension of SafeHandle, which requires Close() or
Dispose() after used according to the docs. There are many examples on using
the named pipes in .Net. All the examples expoit
FileStream(CreateFile(PIPE_NAME)). You may look at
http://blog.paranoidferret.com/index.php/2007/07/25/interprocess-communication-u
sing-named-pipes-in-csharp/
for one. But none of the examples closes the handle nor the 'using'
directive is used!

Should I?

Reply to this Message

Henning Krause [MVP - Exchange] - 29 Oct 2007 18:09 GMT

Hello,

the SafeHandle will eventually disposed by its destructor. But calling the
Dispose method when you no longer need the SafeHandle is a very good idea -
it deterministically releases the unmanged handle and removes the instance
from the finalization queue which tracks all instances with a finalizer.

Kind regards,
Henning Krause

> The SafeFileHandle is an extension of SafeHandle, which requires Close()
> or Dispose() after used according to the docs. There are many examples on
[quoted text clipped - 5 lines]
>
> Should I?

Reply to this Message

Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...