Visual Lint ships as a single file MSI based installer which includes the Visual Lint interactive application (VisualLintGui), command line application (VisualLintConsole) and plug-ins for Microsoft Visual Studio and Eclipse. If required, the installer can be configured to perform silent installations.

When run, the installer will offer you a selection of the available components, which include both standalone and plug-in versions of Visual Lint:

Visual Lint installation components

It will then install the selected Visual Lint plug-ins, executables and supporting files to the specified installation directory (by default C:\Program Files\Riverblade\Visual Lint), and configure the supported development environments to load it.


Available Components

Visual Studio plug-in

The Visual Studio plug-in is a self-registering 32 bit DLL which will attempt to register itself with all supported versions of Microsoft Visual Studio.

If you have installed the plug-in for use with AVR Studio 5 or Atmel Studio 6 the plug-in will need to be manually registered with the IDE using a registry script - please see How do I register the Visual Lint plug-in with AVR Studio 5 or Atmel Studio 6? for details.

If you have installed the plug-in for use with Visual C++ 6.0 or eMbedded Visual C++ 4.0, the installer will attempt to register the plug-in with the IDE, but if this does not work (e.g. if you are using a different user account to that the installer was run from) you can register it manually by launching the IDE and registering the plug-in via the "Add-ins and Macros" page in the "Customize" dialog.


Eclipse plug-in

The Eclipse plug-in is implemented in two parts - a DLL (which resides within the Visual Lint installation folder) and a JAR file which should be copied to the "plugins" folder within the Eclipse installation. There are two versions of each - one for 32 bit versions of the JVM, and one for 64 bit.

If the Eclipse plug-in is selected for installation, the installer will prompt for the location of the Eclipse installation. If you need to manually configure an Eclipse installation to load the plugin please see How do I install the Visual Lint plug-in to multiple installations of Eclipse on the same computer?


Command line Application

If VisualLintConsole (the command line version of Visual Lint) is selected for installation, a shortcut titled "Visual Lint command prompt" will be created within the Windows Start menu/screen. From the shortcut you can invoke VisualLintConsole directly without specifying its path - otherwise you will need to either specify the full path to VisualLintConsole.exe or add the its installation folder to the system path.

Please see Command Line Options for details of the VisualLintConsole command line.


Standalone Application

VisualLintGui is the standalone version of Visual Lint, and can analyse any project compatible with the plug-in versions of Visual Lint or VisualLintConsole.

If selected for installation, it can be invoked by a shortcut within the Windows Start menu/screen.


After installation...

The next time Visual Lint starts, it will guide you though the configuration process for that environment. Once installed, Visual Lint commands can be invoked by selecting the "Visual Lint" command on the "Tools" menu (where available*) or from the corresponding toolbar:

For full details of the commands available, please see the Reference Guide.

* Visual C+ 6.0 and eMbedded Visual C++ 4.0 do not provide a means for third party extensions to add items to their menubar. However, this capability is fully supported in later versions of Visual Studio (i.e. from Visual Studio .NET 2002 onwards) and in Eclipse.

Copyright © 2004 - 2015 by Riverblade Ltd. All rights reserved.