Frequently Asked Questions

If you can’t find an answer to your question here, please contact support@indefiant.com.

Installation

The Recode menu is missing from Visual Studio

This can occur due to an error or conflict during the Visual Studio extension installation process.

Firstly, check the Tools -> Extensions and Updates... menu to see if Recode is installed but disabled. If Recode is listed as disabled attempt to enable it and restart VS.

If Recode is not listed in the Extensions and Updates dialog, try the following to attempt a manual installation:

  1. Open your Recode installation folder (typically: C:\Program Files (x86)\Recode\).
  2. Run RecodeVSP.vsix to start the VSIX installer.
  3. Select the Visual Studio versions you want to use with Recode.
  4. Click install.
  5. Once completed, open Visual Studio and confirm Recode is integrated.

If this doesn’t solve your problem, try uninstalling Recode via the Programs and Features control panel. Should that still not succeed, contact support@indefiant.com for further assistance.

Can I use Recode with Visual Studio Express?

Unfortunately not. Microsoft do not allow the use of Visual Studio extensions (such as Recode) with the Express edition of Visual Studio. However, the new Visual Studio Community Edition is fully compatible.

Can I use Recode with Visual Studio Community Edition?

Yes! The new Visual Studio Community Editions support Visual Studio extensions which means Recode works without any problems.

Usage

Recode fails with: fatal error C1041

If you see the C1041 compiler error during a Recode:

fatal error C1041: cannot open program database 'c:\path\to\vc120.idb'; if multiple CL.EXE write to the same .PDB file, please use /FS

This typically means you have Visual Studio Edit and Continue enabled for native code. In certain cases this will lock the idb file preventing later Recodes from succeeding after the first Recode.

Disable Edit and Continue via Tools -> Options -> Debugging -> Edit and Continue to avoid this issue.

Duplicate breakpoints appear after Recoding

Recode attempts to cull obsolete breakpoints after every Recode. If this does not occur as expected, and you have multiple breakpoints appearing, please check that the Visual Studio option Debug > Options > Require source files to exactly match the original version is enabled.

Support

Recode keeps failing, what can I do?

Tell us! Please send an email to support@indefiant.com describing the issue you encountered and giving as many details as you can, including:

  • The reproduction rate (ie. does it happen reliably/intermittently/rarely?)
  • Are there any patterns to the failure (ie. only one file; only after the second Recode etc)
  • The Recode log.
  • Snippets of the code at the lines mentioned by any code errors/warnings in the Recode log.
  • The version of Visual Studio you’re using.
  • Any other details you think may be useful.