Visual Lint is available in four editions: Free, Standard , Professional and Enterprise:

• Visual Lint Enterprise Edition is recommended for large development teams with detailed analysis configuration and reporting requirements. In addition to automated background analysis of entire Visual Studio solutions and workspaces and the other facilities of the Professional Edition, Visual Lint Enterprise Edition provides detailed HTML reporting, viewing of analysis history and the most customisable analysis configuration of any Visual Lint edition.
  
  
• Visual Lint Professional Edition is recommended for development teams who deal with large codebases or require customised analysis configurations. In addition to automated background analysis of entire Visual Studio solutions and workspaces and the other facilities of the Standard Edition, Visual Lint Professional Edition allows selective inclusion/exclusion of specific files or projects, whole project analysis and highly customisable analysis configurations.
  
  
• Visual Lint Standard Edition is recommended for small teams and individual developers with relatively small codebases. In addition to the manual analysis conventionally offered by PC-Lint integration solutions, Visual Lint Standard Edition also offers the capability for automated background lint analysis of entire Visual Studio solutions and workspaces.
  
  
• Visual Lint Free Edition provides single file manual analysis capabilities and is designed for non-commercial use on small projects.

The benefits and features available in each Visual Lint edition are summarised in the table below:

Feature	Free Edition (non-commercial use only)	Standard Edition (pricing)	Professional Edition (pricing)	Enterprise Edition (pricing)
Licenced for commercial use	-
Integrates PC-Lint 7.50 or later closely within the development environment
Compatible with eMbedded Visual C++ 4.0, Visual C++ 6.0, Visual Studio .NET 2002, Visual Studio .NET 2003, Visual Studio 2005 and Visual Studio 2008
Compatible with the Intel C++ Compiler (version 9.1 or later)	-	-
Designed for large codebases	-	-
Dedicated command to view the PC-Lint manual within the development environment
Dedicated commands to edit PC-Lint configuration files directly within the development environment
Analysis of implementation files automatically takes into account project settings and active configuration
The active file can be manually analysed from the context menu of the code editor at any time
Double clicking on a lint issue opens the corresponding source file and shows the meaning of the issue
Single file ("unit checkout") manual analysis
Automated background lint analysis of the entire solution or workspace	-
Selective inclusion or exclusion of individual projects and files from background lint analysis	-	-
Whole project analysis	-	-
Analysis results automatically made available when a window is activated	-
When a file is saved, it is automatically queued for re-analysis	-
A dedicated Analysis Results Display presents analysis results in an easy to interpret, colour coded form
Analysis Results Display "Issue Count by Category" view	-	-
Analysis Results Display "Issue Count by Message Number" view	-	-	-
A dedicated Message Lookup Display provides the ability to directly look up the meaning of any PC-Lint message
A dedicated Analysis Status Display shows detailed information upon the current status of analysis within the solution	-
A dedicated Analysis History Display showing information upon the analysis history of a specified file, project or the entire solution.	-	-	-
HTML Reports	-
User defined HTML report stylesheets	-	-
Solution and project reports include detailed breakdowns (in chart and tabular form) of which PC-Lint messages have been reported, and where.	-	-	-
Customisable and user definable lint issue categories	-	-
Customisable per solution and per project analysis configurations	-	-
Per solution analysis configuration (.vloptions) files	-	-
Per project analysis configuration (.vloptions) files	-	-	-

Finally, Visual Lint is designed by developers for developers. We have the same problems you do, so if you have a feature you would like to see included, please let us know.