VisualGDB Not Showing Up in VS 2010

[MikeGranby]

VisualGDB is showing up in my VS 2019 installation, but has disappeared from VS 2010. It shows up in the VS 2010 Extension dialog, but not in the menus. I’ve tried repairing, reinstalling, refreshing the extension cache by removing and reinstalling an extension, but it’s still not there. Help!

Attachments:

You must be logged in to view attached files.

[support]

Hi,

Please try installing any other extension via Tools->Extensions and Updates. This should force Visual Studio to rebuild the menu cache.

If it doesn’t help, please double-check whether VisualGDB commands appear under Tools->Customize.

[MikeGranby]

Had already installed and remove an arbitrary extension to refresh the cache, but tried again (Hide Main Menu, FWIW) and still no joy. The VisualGDB commands do not appear in the Customize dialog.

[support]

Sorry, that would be a tricky one to diagnose. Visual Studio uses an opaque cache object to store the menu commands from various extensions, and if it gets corrupt, there is no known way to deterministically repair it.

We could recommend a few workarounds, but none of them is guaranteed to work 100%:

1. Try running devenv.exe /Log and checking the ActivityLog.xml file. If it shows a specific reason why VisualGDB is not loading, it might give some troubleshooting clues.
2. If VisualGDB is just not mentioned in the log file, try creating another temporary user account on that machine and see if VisualGDB menus appear there. If they do, try moving out the Visual Studio’s per-user registry keys and folders (under %LOCALAPPDATA% and %APPDATA%) and restarting it. This will reset all per-user settings and should get VisualGDB to show again.
3. Also reinstalling or repairing VS via Add/Remove programs might help.

[MikeGranby]

Here are the extracts from the startup log that mention GDB…

  <entry>
    <record>127</record>
    <time>2019/10/27 16:22:34.449</time>
    <type>Information</type>
    <source>Extension Manager</source>
    <description>Successfully loaded extension...</description>
    <path>C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\Extensions\Sysprogs\VisualGDB\</path>
  </entry>
  <entry>
    <record>128</record>
    <time>2019/10/27 16:22:34.450</time>
    <type>Information</type>
    <source>Extension Manager</source>
    <description>Extension is enabled...</description>
    <path>C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\Extensions\Sysprogs\VisualGDB\</path>
  </entry>
 
...
 
  <entry>
    <record>189</record>
    <time>2019/10/27 16:22:34.503</time>
    <type>Information</type>
    <source>Microsoft.VisualStudio.CommonIDE.ExtensibilityHosting.VsShellComponentModelHost</source>
    <description>Successfully loaded component assembly from cache</description>
    <path>C:\Program Files (x86)\Sysprogs\VisualGDB\VisualGDBPackage2010.dll</path>
  </entry>
 
...
 
  <entry>
    <record>275</record>
    <time>2019/10/27 16:22:38.805</time>
    <type>Warning</type>
    <source>Microsoft.VisualStudio.CommonIDE.ExtensibilityHosting.VsShellComponentModelHost</source>
    <description>The component assembly doesn&apos;t exist:</description>
    <path>C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\Extensions\Sysprogs\VisualGDB\SysprogsBuildUpToDateCheck2015.dll</path>
  </entry>
 
...
 
  <entry>
    <record>309</record>
    <time>2019/10/27 16:22:39.145</time>
    <type>Information</type>
    <source>VSCommands</source>
    <description>Installed Extensions
	Process Template Editor
	State	=	Enabled
	Version	=	2.0

	WITDesigner
	State	=	Enabled
	Version	=	2.0.0.0

	VisualGDB
	State	=	Enabled
	Version	=	5.4

	Productivity Power Tools
	State	=	Enabled
	Version	=	10.0.20626.18

	Align Assignments
	State	=	Enabled
	Version	=	1.3

	VSCommands for Visual Studio 2010
	State	=	Enabled
	Version	=	10.3.9.12

	Wix Toolset Visual Studio 2010 Extension
	State	=	Enabled
	Version	=	1.0.0.4

</description>
  </entry>

[support]

Sorry, the log doesn’t seem to have anything out of the ordinary, so the only other option would be to try various reset/reinstall steps suggested earlier.

You can also try using the /ResetSkipPkgs option, although it may not work either.

[MikeGranby]

The most obvious bit is…

The component assembly doesn’t exist:
C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\Extensions\SysprogsVisualGDB\Sysprogs\BuildUpToDateCheck2015.dll

…and indeed that file does not exist.

• This reply was modified 5 years ago by MikeGranby.
• This reply was modified 5 years ago by MikeGranby.
• This reply was modified 5 years ago by MikeGranby.

[support]

Hi,

This part is only relevant for VS2015+ that supports fast up-to-date check plugins (invoked before showing the “Project XXX is out of date” message). It should not affect any other functionality and can be safely ignored.

[bernardofca]

Exactly the same problem here. I have used VS2010  with Visual GDB for many years. I recently installed VS2019 community edition and renewed my Visual GDB support. After downloading the latest Visual GDB and installing it, I have the exact same behavior as the OP.

[support]

Hi,

Please follow the instructions described on this page. They go through the most common causes of this problem.

If nothing helps, please let us know more details (per instructions) and we will help you get it to work.

[Author]

Posts