Remove calls to GC.KeepAlive
Important This document may not represent best practices for current development, links to downloads and other resources may no longer be valid. Current recommended version can be found here. ArchiveDisclaimer

Remove calls to GC.KeepAlive







Breaking Change


Classes use SafeHandle but still contain calls to GC.KeepAlive.

If converting to SafeHandle usage, remove all calls to GC.KeepAlive (object). In this case, classes should not have to call GC.KeepAlive, assuming they do not have a finalizer but rely on SafeHandle to finalize the OS handle for them. Even though the cost of leaving in a call to GC.KeepAlive might be negligible in terms of performance, the perception that a call to GC.KeepAlive is either necessary or sufficient to solve a lifetime issue that might no longer exist makes the code harder to maintain.

Remove calls to GC.KeepAlive.

You can exclude this warning only if it is not technically correct to convert to SafeHandle usage in your class.

© 2015 Microsoft