|
Parasoft's core static analysis capability provides the industry's most extensive support for .NET development.
The following are selected examples of items in each category. These are not comprehensive list. If you have questions about an item that is not
listed, please contact Parasoft to see if support is available
Defects*
- Security vulnerabilities
- Exceptions
- Resource & memory leaks
- Threads & synchronization
- Deadlocks & race conditions
- Performance degradation
- Initialization
- API Usage & Implementation
- Logical Errors
- Serialization
Technologies*
- C#
- VB.NET
- C++/CLI (ManagedC++)
- .NET Framework
- COM
- Windows Presentation Foundation
Build systems
- MSBuild
- NAnt
- CruiseControl
IDEs
- Visual Studio 2010
- Visual Studio 2008
- Visual Studio 2005
Source Control
- AccuRev
- CVS
- ClearCase
- Perforce
- Serena Dimensions
- StarTeam
- Subversion
- Synergy/CM
- Team Foundation Server (2005, 2008)
- Visual Source Safe
Metrics*
- Cyclomatic Complexity
- Maintainability Index
- Inheritance Depth
- Number of Method Parameters
Static Code Analysis Rules*
- Ensure that method return values are used
- Do not use floating point variables as loop indices
- Avoid assignment within a condition
- Do not compare value types to null
- Avoid calling Finalize directly
- Avoid throwing exceptions in Equals
- Avoid infinite recursive method calls
Data Flow Rules*
- Do not modify a collection while iterating over it
- Avoid division by zero
- Ensure resources are deallocated
* These are samples—not a comprehensive list. To see if a specific need is supported, contact Parasoft.
|
