Share via

Debugging and Troubleshooting Tips

  • Article

This section includes some debugging and troubleshooting tips.

Debugging Add-Ins

You can debug an add-in by attaching a debugger to the GROOVE.exe process. When you attach the GROOVE.EXE process, you should specify "Managed mode", not the default, which is "Native mode".

You must ensure that the .dll libraries built by the project are identical to the .dlls in the installation folder on the system.

Troubleshooting Add-In Loading

This section contains some troubleshooting tips to help you develop and install an add-in.

  • If the new tool does not appear in the Workspace->Add tool menu, check the following:

    • The registry file was not executed or contains an error. No code is loaded until the tool is installed in a workspace; consequently, this problem can only be caused by a registry error.

    • The registry file defined the keys in the wrong hive in the registry. For example, if you are running on a Windows 32-bit on Windows 64-bit operating system, SharePoint Workspace looks in the HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Office\Groove\AddIns node instead of the usual HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\Groove\AddIns node. To define the keys in the correct location, you should execute the registry file by importing it with the SysWOW64 version of the registry editor. If you have installed the operating system in the c:\Windows folder, you can run the SysWOW64 version of regedit, by entering the following:

      c:\Windows\SysWOW64\regedit

    • The workspace version is 2007. You can only use add-ins in workspaces with a 2010 version.

  • If a tool load error message is displayed when the tool is opened, there is typically an error loading an assembly.