BullseyeCoverage
It is recommended to launch Visual Studio at least once before installing BullseyeCoverage.
Otherwise,
integration of the Visual Studio Tools menu may fail.
The BullseyeCoverage installer automatically integrates with all supported versions of Visual Studio that are installed for the current user.
The compiler wrapper is BullseyeCoverage\bin\cl.exe and
the linker wrapper is BullseyeCoverage\bin\link.exe.
If these files do not exist,
run the BullseyeCoverage Browser,
use the menu command Tools Options
and enable your Microsoft Visual Studio version.
Enabling integration for Visual Studio adds the BullseyeCoverage\bin to the front of the Executable Directories setting.
The modified Executable Directories setting is stored in files named
%LOCALAPPDATA%\Microsoft\MSBuild\MSBuildToolsVersion\Microsoft.Common.targets\ImportAfter\BullseyeCoverage.targets.
The BullseyeCoverage integration adds a command into the Microsoft
Visual Studio Tools menu to enable and disable coverage build.
After enabling or disabling coverage build,
rebuild your project using command
Build Rebuild.
With Visual Studio 2010 Express, use the menu command Tools Settings Expert Settings prior to installing BullseyeCoverage.
If you already installed BullseyeCoverage before making this change, install BullseyeCoverage again.
If you do not see the BullseyeCoverage menu entry,
you can make this change manually using the Visual Studio menu command Tools External Tools.
The settings should appear as shown in the image below.
The Command setting is c:\Program Files\BullseyeCoverage\bin\CoverageBrowser.exe.
For Visual Studio 2017 and later, External Tools are stored in the files named below.
%LOCALAPPDATA%\Microsoft\VisualStudio\*\Settings\CurrentSettings.vssettings
(Visual Studio 2017 15.3 and later)
%USERPROFILE%\Documents\Visual Studio *\Settings\CurrentSettings.vssettings
(Visual Studio 2017 15.0 to 15.2)
For Visual Studio 2015 and earlier,
External Tools are stored in the registry at HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\version\External Tools.
You can build with BullseyeCoverage from the command prompt just as you normally do.
Enable coverage build with the command cov01 -1 before building.
If you build with devenv or msbuild,
you must have the BullseyeCoverage/bin in the Visual Studio Executable Directories as described above.
The BullseyeCoverage integration modifies the files listed below to add the BullseyeCoverage\bin directory to the PATH setting, if permissions allow.
Microsoft Visual Studio\Common7\Tools\vsdevcmd.bat Microsoft Visual Studio\Common7\Tools\vsdevcmd\ext\vcvars.bat Microsoft Visual Studio\Common7\Tools\vsvars32.bat Microsoft Visual Studio\VC\Auxiliary\Build\vcvarsall.bat Microsoft Visual Studio\VC\bin\amd64\vcvars64.bat Microsoft Visual Studio\VC\bin\amd64_arm\vcvarsamd64_arm.bat Microsoft Visual Studio\VC\bin\amd64_x86\vcvarsamd64_x86.bat Microsoft Visual Studio\VC\bin\arm\vcvarsarm.bat Microsoft Visual Studio\VC\bin\vcvars32.bat Microsoft Visual Studio\VC\bin\x86_amd64\vcvarsx86_amd64.bat Microsoft Visual Studio\VC\bin\x86_arm\vcvarsx86_arm.bat
Updated: 10 Apr 2026
Copyright © Bullseye Testing Technology. All Rights Reserved.