Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Port FxCop rule CA2006: UseSafeHandleToEncapsulateNativeResources #480

Closed
Tracked by #61964
ghost opened this issue Nov 21, 2015 · 2 comments
Closed
Tracked by #61964

Port FxCop rule CA2006: UseSafeHandleToEncapsulateNativeResources #480

ghost opened this issue Nov 21, 2015 · 2 comments

Comments

@ghost
Copy link

ghost commented Nov 21, 2015

Title: Use SafeHandle to encapsulate native resources

Description:

Use of IntPtr in managed code might indicate a potential security and reliability problem. All uses of IntPtr must be reviewed to determine whether use of a SafeHandle, or similar technology, is required in its place.

Dependency: None

Notes:

@AaronRobinsonMSFT
Copy link
Member

Interop team doesn't think this is useful. This can be closed.

@Evangelink
Copy link
Member

Closing this issue as won't be ported as per dotnet/runtime#61964 (comment).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants