The first public build of Visual Lint 6.0 has just been uploaded to our website.
As of today, Visual Lint 6.0 replaces Visual Lint 5.5 as the current supported Visual Lint version. Customers with active Visual Lint 5.x priority support, floating and site licence subscriptions should shortly be receiving updated licence keys for the new version, and upgrades for Visual Lint 1.x, 2.x, 3.x, 4.x and 5.x per user licences should become available in our online store shortly.
If you have purchased any full per-user Visual Lint licences since the start of October, your licence keys are already v6.x compatible so can start using the new version of the software right now without any need to upgrade. If you have purchased any upgrade licences during the same period, you will shortly receive new Visual Lint 6.x compatible licence keys.
The new version adds more complete support for the forthcoming PC-lint Plus, as well as support for Visual Studio 2017 RC and many other improvements.
Full details of the changes in this version are as follows:
- Added support for analysing standalone makefile projects.
- Added support for makefiles within custom project (.vlproj) files. This allows makefiles requiring additional parameters to be analysed more easily.
- Added support for Visual Studio 2017 RC. Note that the IDE will currently issue a warning that the extension is not compatible during installation.
- Speeded up the loading of solutions and workspaces by loading the projects within them in parallel.
- PC-lint Plus crashes ("Serious Errors") are now parsed and reported as Fatal Errors with ID 399.
- PC-lint Plus messages 890-897 are now correctly recognised as referencing ("supplemental", in PC-lint Plus parlance) issues.
- Added PC-lint Plus specific compiler indirect files co-rb-vs2012.lnt, co-rb-vs2013.lnt, co-rb-vs2015.lnt and co-rb-vs2017.lnt, as well as a PC-lint Plus version of lib-rb-win32.lnt. All such indirect files are installed into the Visual Lint installation folder and referenced via -i directives on the generated PC-lint Plus command line.
- When a PC-lint Plus per-project analysis task which uses more than one thread is running, Visual Lint can now dynamically reduce the number of active analysis tasks to take account of the number of analysis threads launched by the analysis task. [Visual Lint Professional and Enterprise Editions]
- PC-lint and PC-lint Plus project indirect (project.lnt) files are now written when analysis tasks requiring them are created rather than when a solution/workspace is loaded.
- If the Visual Studio plug-in is selected for installation, a VSIX extension (VisualLintPackage.vsix) supporting Visual Studio 2017 RC is now installed into the Visual Lint installation folder. If Visual Studio 2017 is installed on the target system, the installer will automatically attempt to run the appropriate instance of VsixInstaller.exe to install the extension into Visual Studio 2017 RC.
- When invoked, the Configuration Wizard now opens on the Analysis Tools page. As a result, the "Introductory" page has been removed.
- The indirect files listed in the Configuration Wizard PC-lint Compiler Configuration page are now sorted primarily by description rather than filename. This works better than sorting by filename as the naming conventions for MSVC compiler indirect files between PC-lint and PC-lint Plus are slightly different.
- Added an "analysis threads" option to the Command Line Options page to allow the value of the PC-lint Plus -max_threads option to be set on the command line in per-project analysis. [Visual Lint Professional and Enterprise Editions]
- Renamed the "Maximum background analysis thread count" option on the Analysis Options page to "Maximum background analysis tasks".
- Added a new Projects Display to VisualLintGui to provide a way of viewing the structure and properties of projects.
- Added a new Project Properties Dialog to provide a way of viewing (and in the case of custom projects, editing) project properties. The dialog is available via context menu commands in the Projects Display and Analysis Status Display..
- Added a new Project Variables Dialog to display the build variables defined in the associated project configuration.
- Added an "Issue IDs" control (similar to the one in the Analysis Statistics Display) to the Display Filter Dialog as an alternative to editing the raw issue filter directly. Note that this control will be hidden if the dialog does not have access to a list of the issues which can be detected by the current analysis tool.
- Added a new Makefile Properties Dialog. Where appropriate, the makefile command line can be edited here and the makefile output seen immediately.
- Replaced the discrete "Clear Text Filter" buttons in the primary displays with integrated ones built into the corresponding text filter edit controls.
- Added infotips to the Analysis Statistics Display.
- When the current host environment is changed (e.g. when projects for different versions of Visual Studio are loaded) the details are now reflected in the Status View.
- The "Analysis Tool:" message displayed in the Status View when Visual Lint starts now shows which host environment/project type the active analysis tool relates to.
- Added an "Export Project" command to the Analysis Status Display context menu to export the current project as a custom project (.vlproj) file.
- Added an "Export Analysis Results" context menu command to the Analysis Status Display context menu.
- Added a "File | New Project" command to VisualLintGui to allow new custom projects to be created directly within the environment.
- Rearranged the VisualLintGui "File" menu and added accelerators to the "File | Open | Solution/Workspace/Project..." and "File | Open | Eclipse Workspace..." commands.
- Added a "Send Feedback" command to the main menus in VisualLintGui and the Visual Studio and Eclipse plug-ins.
- HTML analysis reports are now displayed in the internal browser of the host environment (if available) by default.
- The platform name is now inferred from the targetPlatform element while reading Eclipse C/C++ (.cproject) project files.
- Variables within file paths are now expanded correctly while reading IAR Embedded Workbench project files.
- The Analysis Status Display "Troubleshooting | View Project Indirect File" context menu command is now disabled if Visual Lint has not been configured for PC-lint analysis of the associated project type, or if the project is still loading.
- Fixed a bug relating to ProjectVersion elements within Atmel AVR Studio 5.0 project files.
- Fixed a potential bug when interfacing to CppCheck, which could have caused cppcheck.exe to be omitted from the analysis tool pathname under some conditions - potentially causing analysis errors.
Download Visual Lint 220.127.116.113