Installation Troubleshooting

Deleaker is not shown in Visual Studio

In very rare cases, the Deleaker installer does not force Visual Studio to reload its extensions. As a result, Deleaker is not loaded and the Deleaker menu item does not appear in the Visual Studio main menu.

Visual Studio 2017

For Visual Studio 2017, run Deleaker.vsix from the Deleaker installation directory (usually %ProgramFiles(x86)%\Deleaker\Deleaker.vsix or %ProgramFiles%\Deleaker\Deleaker.vsix).

If Deleaker is still not available, please contact support.

Visual Studio 2005-2015

For earlier versions of Visual Studio, extensions must be reloaded manually using the command line.

Close all Visual Studio instances.

Run cmd.exe as Administrator:

Then execute the appropriate command for your Visual Studio version.

Visual Studio 2015:

"%VS140COMNTOOLS%..\IDE\devenv.exe" /setup

Visual Studio 2013:

"%VS120COMNTOOLS%..\IDE\devenv.exe" /setup

Visual Studio 2012:

"%VS110COMNTOOLS%..\IDE\devenv.exe" /setup

Visual Studio 2010:

"%VS100COMNTOOLS%..\IDE\devenv.exe" /setup

Visual Studio 2008:

"%VS90COMNTOOLS%..\IDE\devenv.exe" /setup

Visual Studio 2005:

"%VS80COMNTOOLS%..\IDE\devenv.exe" /setup

The command may take some time to complete. Please wait until it finishes.

After the command completes, start Visual Studio and verify that the Deleaker menu appears in the main menu.

If Deleaker is still missing, please contact support.

Visual Studio fails to load Deleaker

In some cases, Visual Studio may fail to load the Deleaker extension. When this happens, Visual Studio suggests reviewing ActivityLog.xml, which contains information about extension loading errors.

If you encounter the following error:

LegacySitePackage failed for package [Softanics.DeleakerVSPackage.DeleakerVSPackage, DeleakerVS, Version=1.0.0.0, Culture=neutral, PublicKeyToken=632a5f39d1d54ca6]
...
Error: Type 'SVsSolutionObject' and type 'SVsSolution' both have the same UUID.

You need to register Microsoft.VisualStudio.Shell.Interop.dll in the Global Assembly Cache (GAC).

Run cmd.exe as Administrator and execute the following commands (the path below is an example for Visual Studio 2017 Professional):

cd "V:\Program Files (x86)\Microsoft Visual Studio\2017\Professional"
gacutil -if Common7\IDE\PublicAssemblies\Microsoft.VisualStudio.Shell.Interop.dll

Deleaker installer does not detect installed Qt Creator instances

The Deleaker installer uses several methods to detect installed versions of Qt Creator. In rare cases, detection may fail.

If this happens, restart the installer with the switch /LOG="path to log file".

After the installation completes, send the generated log file to us along with a description of the problem: contact support.

Manual installation

Deleaker provides plugins for each supported Qt Creator version.

For example, for Qt Creator 4.9 (32-bit), the plugin file is <Deleaker installation directory>\DeleakerQtCreator_4.9.0_x86.dll.

Each Qt Creator installation has a plugin directory located at <Qt Creator installation directory>\lib\qtcreator\plugins.

To install Deleaker manually, copy the appropriate plugin file to this directory and restart Qt Creator.

Deleaker is not shown in RAD Studio

If the installer was run without administrative privileges, it may have been executed under a different user account. In this case, Deleaker is registered under a different HKEY_CURRENT_USER hive and is not visible in RAD Studio for the current user.

To install Deleaker manually in RAD Studio:

1. Start RAD Studio.
2. Select Component → Install Packages.
3. Click Add... and navigate to the Deleaker installation directory (usually C:\Program Files (x86)\Deleaker or C:\Program Files\Deleaker).
4. Select the appropriate package file from the table below.