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

Jump to bottom

Port FxCop rule CA2001: AvoidCallingProblematicMethods #477

Open
Tracked by #61964
ghost opened this issue Nov 21, 2015 · 3 comments
Open
Tracked by #61964

Port FxCop rule CA2001: AvoidCallingProblematicMethods #477

ghost opened this issue Nov 21, 2015 · 3 comments
Labels
Blocked FxCop-Port Needs-Review
Milestone
Unknown

Comments

@ghost
Copy link

ghost commented Nov 21, 2015

Title: Avoid calling problematic methods

Description:

A member calls a potentially dangerous or problematic method.

Dependency: None

Notes:
@ghost ghost added the FxCop-Port label Nov 21, 2015
@ghost ghost closed this as completed in 9a22626 Apr 15, 2016
@ghost
Copy link
Author

ghost commented Apr 15, 2016

Wrong issue got closed.

@ghost ghost reopened this Apr 15, 2016
@333fred
Copy link
Member

333fred commented May 3, 2017

This analyzer also should be moved to the Microsoft.CodeQuality.Analyzers package, currently it's in Microsoft.CodeQuality.CSharp.Analyzers. /cc @mavasani.

@jinujoseph jinujoseph added this to the Unknown milestone Nov 26, 2017
@Evangelink
Copy link
Member

@mavasani Could you confirm that's still ok to implement this rule?

@Evangelink Evangelink mentioned this issue Nov 23, 2021
Open
31 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Blocked FxCop-Port Needs-Review
Projects
None yet
Milestone
Unknown
Development

No branches or pull requests
4 participants
@333fred @mavasani @Evangelink @jinujoseph