Verify MMX for VS2005 and VS 2008 IDE integration

This document explains how to verify your ModelMaker Code Explorer for Visual Studio 2005 / 2008 installation and how to solve installation problems.
Applicable to versions MMXVS 1.x and 2.x. The text assumes a MMX 2.00 installation, substitute the actual version where applicable. Also, the text assumes VS 2005, read VS 2008 where appropriate.

Directories and files

You should have these directories (actual path names depending on your actual install dir / drive)

  • C:\program files\ModelMakerTools
    The root directory, does not contain files
  • C:\program files\ModelMakerTools\MMX_VS2005\2.00
    Or whatever version or you installed. Contains all explorer related files such as MMX_VS2005.dll, MMXVSHost.ocx, Interop.MMXVSHost.dll, the user manual etc.
  • C:\program files\ModelMakerTools\Shared
    The directory containing files shared with other ModelMaker Tools products. No files required in this directory, but it can contain auto-created files like SharedSettings.ini.
  • C:\program files\ModelMakerTools\Shared\Templates
    This directory should contain the predefined templates and other templates you added. For example ArrayProp_List.pas.

If any of these directories or files is missing you need to run the installer again.

Registry settings: HKEY_LOCAL_MACHINE

You should have these keys:

  • HKLM\SOFTWARE\ModelMaker\MMXVS\2.0\VS2005
    containing at least a string value named InstallDir pointing to the actual install path. For example: "C:\program files\ModelMakerTools\MMX_VS2005\2.00" (omit quotes).
  • HKLM\Software\ModelMaker\Shared
    containing at least has a string value named RootDir pointing to the Shared directory. For example: "C:\program files\ModelMakerTools\Shared" (omit quotes).
  • HKLM\Software\ModelMaker\Shared\Templates
    containing at least has a string value named RootDir pointing to the Templates directory. For example: "C:\program files\ModelMakerTools\Shared\Templates" (omit quotes).

If any of these keys / values is missing, you may either run the installer again or manually add them. Make sure you enter the correct directory names.

Registry settings: HKEY_CURRENT_USER

You should have these keys:

  • HKCU\Software\ModelMaker\Shared\Templates
    containing values that are the registered templates. For example:
    value name=Simple Singleton
    value string data="C:\Program Files\ModelMakerTools\Shared\Templates\Singleton.cs",Wizards

This key and it's values is non-essential for ModelMaker Code Explorer. Registering a new code template will auto create whatever is missing.

You do not need any keys or values in HKCU\Software\ModelMaker\MMXVS\2.0 or any of its sub keys. These keys are auto created and contain non-essential user settings

VS 2005 IDE Integration

The Code Explorer for VS2005 / VS 208 installer integrates the explorer with VS2005 only if that's installed already.

Technically VS 2005 IDE integration is done through an .addin file. This add-in file named MMXVS2005.Addin (or MMXVS2008.Addin) is located in a windows user data sub-directory:
C:\Documents and Settings\[USER]\Application Data\Microsoft\MSEnvShared\Addins
where [USER] is the currently logged in user. For example:
C:\Documents and Settings\Administrator\Application Data\Microsoft\MSEnvShared\Addins

Manually creating and verifying the .Addin file

If Code Explorer is not loaded by VS2005 - no menu item visible in the IDE View menu - , this is usually caused by a missing .Addin file. If you do not see a file named MMXVS2005.Addin (MMXVS2008.Addin) in the above mentioned directory, you can download a default copy here.

Do NOT run or open this file. Edit only using Notepad or any plain text editor. After downloading and saving this file in the above mentioned directory, open in Notepad and check that the xml node
<Assembly>
C:\Program Files\ModelMakerTools\MMX_VS2005\2.00\MMX_VS2005.dll
</Assembly>
corresponds to the actual MMX for VS2005 install directory + dll name. Similar for VS 2008

Manually (re-)registering the .ocx

The MMX_VS2005.dll as defined in the .Addin file <Assembly> node, uses the MMXVSHost.ocx , that is located in the same MMX VS2005 install directory. To manually (re-)register the types in this ocx:

  • open a command prompt window,
  • make the MMXVS2005 directory the active directory, and
  • run regsvr32.exe to register the MMXVSHost.ocx by typing:
    regsvr32.exe MMXVSHost.ocx

You should get a msg box that says that the ocx was registered OK. Restarting VS2005 should now load Code Explorer and have the MMX menu in the main VS 2005 toolbar.