Important Notice: Our web hosting provider recently started charging us for additional visits, which was unexpected. In response, we're seeking donations. Depending on the situation, we may explore different monetization options for our Community and Expert Contributors. It's crucial to provide more returns for their expertise and offer more Expert Validated Answers or AI Validated Answers. Learn more about our hosting issue here.

How does Total .NET Analyzer compare with FXCop from Microsoft?

April 26, 2017analyzer compare fxcop Microsoft total

0

Posted

How does Total .NET Analyzer compare with FXCop from Microsoft?

1 Answer

0

Posted

Microsoft designed FXCop to be an internal tool to test compliance with CLS/CLR standards for published components. If you are developing a .NET component, control, or other assembly that is going to be consumed by others, FXCop does a good job of detecting problems with naming conventions and language interoperability. However, FXCop does not have any of the advanced analysis that Total .NET Analyzer offers. For example, FXCop does not detect calls to legacy libraries, or unused code, nor does it detect possible bugs or programming defects. Finally, FXCop only runs on assemblies, not source code. By directly analyzing C# and Visual Basic .NET source code, Total .NET Analyzer can find issues that no assembly inspection can reveal.