Code analysis - Standards verifiers
Display options and filters
|
Built for .NET
|
|
Free or free version available
|
|
Built for Mono
|
|
|
Built for .NET 2
|
|
Source code provided
|
|
Sold as a service
|
|
|
Library
|
|
Built for the Compact Framework
|
|
Discontinued
| |
|
Add-in
|
| | | | |
Updating...
 Home Page
| Categories: |
|
| Author: |
RedHill Consulting |
| Latest version: |
2.2.8 |
| Description: |
Simian (Similarity Analyser) identifies duplication in Java, C#, C, C++, COBOL, Ruby, JSP, HTML, XML and Visual Basic source code. Simian can also be used on any human readable files such as plain text files.
Especially on large enterprise projects, it can be difficult for any one developer to keep track of all the features (classes, methods, etc.) of the system. Simian can be used as part of the build process during development or as a guide when re-factoring. Think of Simian as an independent pair of eyes that will assist in raising the quality of your software. |
| Added: |
2004-01-28 |
| Updated: |
2005-04-12 |
| Attributes: |
 [BuiltForDotNet]  [FreeVersionAvailable] |
Home Page
| Categories: |
|
| Author: |
Joel Fjordén |
| Latest version: |
2.0 |
| Description: |
Plug-in for Visual Studio that checks the code against a configurable code standard and best practices.
Code Style Enforcer is developed for C#, but some of the rules will also work for VB .NET, though not tested. The code standard is configurable with the following rules:
- Name rules, where it is possible to have different rules for different members, i.e. fields, constants, variables, methods, properties and so on.
- Visibility rules, where you can specify the visibility that is valid for different members. It is also possible to specify that the visibility has to be specified explicitly.
- Implementation rules, where it is possible to specify that interface implementations are to be made explicitly or implicitly.
The default rules are based on the C# Coding Standard from IDesign. |
| Added: |
2006-10-06 |
| Attributes: |
[BuiltForDotNet]  [BuilfForDotNet2]  [AddIn] [FreeVersionAvailable] |
Home Page
| Categories: |
|
| Author: |
Universal Software |
| Latest version: |
6.0 |
| Description: |
Generic reverse engineering software for analysis and automatic documentation of source codes (program/header/form files).
Universal Report's goal is to analyse and generate a structured and formatted overview of a given set of program codes. A session can be achieved either in a step-by-step way or in a completely automatic way.
Universal Report is not focused on a specific programming language (will run with codes in Basic, C, C++, Fortran, Java, Matlab, Pascal, Visual Basic, Borland C++ Builder, Delphi, Kylix, Visual C++, Visual Basic .Net, Visual C#, Visual J++, etc....), and you can get reports in several common formats (text, latex, html) and languages (English, French, German, Spanish, Portuguese, and Italian). The universality is due to heuristics that use programming languages intersection as well as possible, and examine further specific points. The tool is parameterizable both in the behavior point of view and the quality of the outputs. Moreover, some additional features are available, including spell checking, general pattern research, automatic information extraction, automatic code formating, glossary generator, graphics generator, routines reviewing system, protection with password, and more. |
| Added: |
2004-12-21 |
| Attributes: |
[BuiltForDotNet] |
Home Page
| Categories: |
|
| Author: |
McCabe Software |
| Description: |
Interactive, visual environment for managing software quality through static analysis and test/code coverage.
McCabeIQ comes in three editions: Developers, Test Team, Enterprise.
Features include:
- Software metrics: McCabe Cyclomatic Complexity; McCabe Essential Complexity; Module Design Complexity; Integration Complexity; Lines of Code; Halstead.
- Color-coded structure Battlemaps, scatter plot diagrams, and flow graphs
- Metric Trend Reports: track a system's metric values over time to document the progress made in improving the overall stability and quality of the project
- Customized reporting
- Plan software testing resources in advance, identifying test paths and the number of tests required
- Code coverage
- McCabe Compare: helps you locate redundant code so you can either delete or reengineer it
- McCabe Data: track data use within your programs and anticipate complexity
- McCabe Change: identify the modules in your program that have changed since the first time you parsed your code
- McCabe Slice: uncover your program’s internal architecture
- Supports Ada, ASM86/95, C, C#, C++.NET, C++, Cobol, Fortran, Java, JSP, Perl, PL1, VB, VB.NET
- Enterprise Edition provides all the functionality of the Developers and Test Team Editions. In addition, it provides enterprise reporting, reengineering capabilities, change analysis, and secure web-enabled test data collection. |
| Added: |
2008-09-15 |
| Attributes: |
[BuiltForDotNet] |
Home Page
| Categories: |
|
| Author: |
Omnicore Software |
| Latest version: |
1.1 |
| Description: |
Productivity add-in that enhances Visual Studio with solution-wide on-the-fly error checking, code navigation features, refactoring and other coding tools for C#, J# and VB.NET, HTML, ASP.NET and Javascript.
JustCode! detects errors throughout the current solution in real time, like a background compiler. The code analysis engine is designed to work incrementally in the background. Whenever the code is changed the error results are made available almost immediately so that one can see how changes in a file affect other files.
Features include:
- Code assistance: on-the-fly error checking of the whole solution; Various status indicators; On-the-fly DLL to source conversion (signature and doc); ...
- Navigation: Find usages; Find sub classes; Find inheritors; ...
- Coding features: code templates; Rename variable, property, method, field, class; Create property on field; Organize usings; ...
- Cross-language code analysis engine: C#, J# and Visual Basic.NET are supported.
- Supports Visual Studio 2003 and 2005. |
| Added: |
2005-11-17 |
| Updated: |
2006-06-05 |
| Attributes: |
[BuiltForDotNet] [BuilfForDotNet2] [AddIn] |
Home Page
| Categories: |
|
| Author: |
bitwidgets |
| Latest version: |
1.3.0.8 |
| Description: |
Assembly comparison tool.
BitDiffer allows you to compare multiple versions of assemblies for all types of changes and drill down to find the smallest changes, public or private.
Features include:
- View changes in a GUI interface, which highlights breaking changes and publicly visible changes. Browse through the grid of changes in order to determine their impact, or export reports to keep a record.
- Compare implementation of methods and properties, not just the declarations. You can compare protected, internal and private items as well as just the exported public types.
- Will catalog and compare: classes, interfaces, properties, fields, methods, attributes, events, assembly attributes
- Compare across time. You can also load up a series of versions and review them side-by-side to see how they all changed across time.
- Load assemblies with the strong name from different locations and compare across them.
- Compare entire directories of assemblies at once, to perform complete build comparisons in one click.
- Command-line support |
| Added: |
2008-01-24 |
| Attributes: |
[BuilfForDotNet2] |
Home Page
| Categories: |
|
| Author: |
Microsoft |
| Latest version: |
4.3 |
| Description: |
StyleCop, also known as Source Analysis, analyzes C# source code to enforce a set of best practice style and consistency rules.
Source Analysis is similar in many ways to FxCop, but FxCop performs its analysis on compiled binaries, while Source Analysis analyzes the source code directly. For this reason, FxCop focuses more on the design of the code, while Source Analysis focuses on layout, readability and documentation. Most of that information is stripped away during the compilation process, and thus cannot be analyzed by FxCop.
Source Analysis comes with a set of default rules analyzers covering approximately 200 best practice rules. These rules are full compatible with the default layout settings in Visual Studio 2005 and Visual Studio 2008.
Specifically, these rules cover the following, in no particular order:
- Layout of elements, statements, expressions, and query clauses
- Placement of curly brackets, parenthesis, square brackets, etc
- Spacing around keywords and operator symbols
- Line spacing
- Placement of method parameters within method declarations or method calls
- Standard ordering of elements within a class
- Formatting of documentation within element headers and file headers
- Naming of elements, fields and variables
- Use of the built-in types
- Use of access modifiers
- Allowed contents of files
- Debugging text
After installation, Source Analysis can be run from within the Visual Studio IDE, and can also be integrated into MSBuild-based command line builds. |
| Added: |
2008-05-23 |
| Updated: |
2008-08-21 |
| Attributes: |
[BuilfForDotNet2] [AddIn] [FreeVersionAvailable] |
Home Page
| Categories: |
|
| Author: |
JetBrains |
| Latest version: |
4.5 |
| Description: |
IDE-independent integrated team environment.
TeamCity automates and coordinates key collaborative processes to eliminate manual systems and delays, providing integration with multiple build and test tools, real-time unit test frequency, server-side inspections and code coverage analysis.
Features include:
- continuous integration and testing
- server-side code analysis
- build management
- automated team communication
- code coverage analysis and reporting
- web-based interface and project dashboard
- extensibility
- IntelliJ IDEA, Eclipse and Visual Studio integration
- pre-tested (delayed) commit
- remote run for personal builds
Supported environments:
- Ant, Maven, NAnt, MSBuild
- Having an IntelliJ IDEA project or a Visual Studio solution, you can build your application with TeamCity, even without providing a build script
- Supports JUnit and NUnit
- Integrates with Perforce, CVS, Subversion, Visual SourceSafe, StarTeam |
| Added: |
2006-07-21 |
| Updated: |
2009-06-12 |
| Attributes: |
[BuilfForDotNet2] [AddIn] [FreeVersionAvailable] |
Home Page
| Categories: |
|
| Author: |
Patrick Smacchia |
| Latest version: |
2.10.1 |
| Description: |
Analyses an application's assemblies and generates reports containing design quality metrics, warnings and diagrams.
NDepend allows you to measure the quality of a design in terms of its extensibility, reusability and maintainability to manage and control the assemblies’ dependencies of your .NET applications. Moreover, NDepend helps you to get a view of the topology of your application, both at component and at type level.
Features include:
- Code Query Language (CQL): NDepend considers your code as a database and CQL allows to query and check some assertions on this database. CQL allows you to write: Code quality constraints, Naming constraints, Encapsulation constraints, Queries on the graph of dependencies, Queries on the inheritance tree, Design constraints, Queries to get the biggest or smallest code elements according to almost 30 metrics.
- Compare builds
- 82 code metrics
- Manage complexity and dependencies
- Detect dependency cycles
- Harness test coverage data
- Enforce immutability and purity
- Warnings about the health of your build process
- Generate custom report from your build process
- Diagrams and interactive code dependencies graphs
- Facilities to cope with real-world environment |
| Added: |
2004-04-27 |
| Updated: |
2008-09-15 |
| Attributes: |
[BuiltForDotNet] [BuilfForDotNet2] [FreeVersionAvailable]  [SourceCodeProvided] |
Ignore this
|
Help the .NET community get a consensus on great tools. Display your favorite tools on your own website or on your blog.
Keep track of your favorite tools. Build your personal watch list.
|