FxCop

3.5
(6)

FxCop is intended for class library developers.

Work for FxCop?

Learning about FxCop?

We can help you find the solution that fits you best.

FxCop Reviews

Chat with a G2 Advisor
Write a Review
Filter Reviews
Filter Reviews
  • Ratings
  • Company Size
  • User Role
  • Industry
Ratings
Company Size
User Role
Industry
Showing 6 FxCop reviews
LinkedIn Connections
Yamel B.
Validated Reviewer
Verified Current User
Review Source
content
Business partner of the vendor or vendor's competitor, not included in G2 scores.

"FxCop to guard your .NET code quality"

What do you like best?

It is a simple tool that allows to check your .NET code based on a quality rule configuration. Sincé first versions Microsoft decided to integrate it in Visual Studio as their internal static code analysis tool. Latest versions are only released within the Microsoft IDE.

It comes with a bunch of code quality rules and it allows to extend them implementing your own rules despite not many documentation can be found to do that.

It allows to implement "supressions" for that rules that are false positives and can be integrated into your CI builds using a cmd version or using the code analysis solution's configuration and msbuild.

What do you dislike?

It analyzes assemblies, you should compile your projects before using it.

It only supports .NET code anaylsis, it cannot be extended for database (SQL) code anaylsis.

Not allowing to categorize the rule criticity (Blocker, critical, major, minor..) rules can only be errors, warnings or info.

The tools is being abandoned in some important code quality products such as SONARQube. Roslyn analyzers are being used also in the latest Visual Studio versions.

Recommendations to others considering the product:

Use at development but integrate with your CI builds to assure the code quality of your product builds.

What problems are you solving with the product? What benefits have you realized?

Implementing static code analysis checks during development and continuous integration builds.

Early detection of code quality problems helping to avoid introducing issues / bugs / problems into our systems.

Education with codding best practices.

Sign in to G2 to see what your connections have to say about FxCop
UI
User in Information Technology and Services
Validated Reviewer
Verified Current User
Review Source
content

"A Microsoft tool to help manage your .NET code"

What do you like best?

Fxcop is a free tool provided by Microsoft to help the .NET developers to manage their assembly code. Its easy to use to find if the standard guidelines has been followed in the code. It only analyze the compiled code and not the original source code.There are different types of rules to detect if any of the coding standards has been violated. Rules like :-

1) To find if any element is degrading the performance.

2) To find any loop hole in the code security.

3) To find if the proper naming convention is not followed.

4) To find if there is any design error or any incorrect usage of globalization and localization.

Some firms add their own rules to follow the company standards in their coding. Those rules then detect the violation of the same

This tool support graphical user interface as well as the command line. Its easy to download and install with easy steps. once installed, you can then load a project for analysis by providing the .dll and .exe path

What do you dislike?

1) You need to compile your .NET project first in order to analyze it. So, for every analysis, you have to compile the code.

2) Fxcop cannot analyze the proper use of comments, whitespaces or braces.

What problems are you solving with the product? What benefits have you realized?

Fxcop help us to manage and clean our .NET code. It sometimes show a message on how to solve an issue. Its easy and quick to use.

What Static Code Analysis solution do you use?

Thanks for letting us know!
Héctor G.
Validated Reviewer
Review Source
content

"Good tool for a quick code analysis"

What do you like best?

the fact that this tool lets anlyce the .NET in a quick and consise maner, Being able to analyce the complete object code and not just the source code makes easy to make sure that the compilation will meet the microsoft framewirk

What do you dislike?

That it would be better if its compatibility were bigger

Recommendations to others considering the product:

When starting to program, this tool is really helpfull for the new online pages, it gies you the confidence that it has been done correctly and lets you find the potential trats in an ordenated manner.

What problems are you solving with the product? What benefits have you realized?

When programing a new onlise site, it is easier to make sure a good security is in place and that there are no easy ways to brake it, checking for flaws in a fast way has also been really helpfull

UG
User in Government Administration
Validated Reviewer
Review Source
content

"Surface static code analysis but not much more than that."

What do you like best?

It's fairly quick and easy to scan your code (it checks compiled object code and not source code) to make sure it follows a set of rules.

Like the broken window theory, if someone sees a broken window and it is not fix there is a higher change all the other windows will become broken. This give you a quick analysis to make sure things are not broken. If the code is polished uniformly people will follow suit.

Lots of rules that come out of the box that you can configure for and has a GUI and a command prompt version that you can execute.

What do you dislike?

The number of rules can be limiting and it really just checks naming and coding standards. This is now a dated tool and appears to no longer be supported. I would suggest looking at other industry tools such as ReSharper or the built-in tools within Visual Studio.

Recommendations to others considering the product:

Take a look at JetBrains ReSharper and some of the features offered in Visual Studio that are now built in.

What problems are you solving with the product? What benefits have you realized?

Quick analysis to make sure developers are following the proper standards, at that point in time this tool was great for what needed to be done.

UI
User in Information Technology and Services
Validated Reviewer
Review Source
content

"Very good code analysis tool for .Net developers"

What do you like best?

It is a static code analysis tool from Microsoft that checks .NET managed code assemblies for conformance to Microsoft's .NET Framework Design Guidelines. Unlike StyleCop, FxCop analyzes the compiled object code and not the original source code.

Biggest plus, its a FREE tool.

What do you dislike?

FxCop has both command-line and GUI based interface. Command Line is little tricky to use.

Recommendations to others considering the product:

Since it is a free tool, it is definitely worth trying.

What problems are you solving with the product? What benefits have you realized?

It improves the code or product quality which you are developing.

U
User
Validated Reviewer
Review Source
content

"FxCop for .NET Development"

What do you like best?

Lint but customized for managed code. Works well and catches problems the compiler misses.

What do you dislike?

Only works well with Visual Studio. Have to use a different tool also if you have a mixed environment.

Recommendations to others considering the product:

If you are using Microsoft tools, it is a great product.

What problems are you solving with the product? What benefits have you realized?

Creating more robust code. Finding the kind of flaws that are missed by compilers but can cause problems with your project later.

Kate from G2

Learning about FxCop?

I can help.
* We monitor all FxCop reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. Validated reviews require the user to submit a screenshot of the product containing their user ID, in order to verify a user is an actual user of the product.