Attaching the Debugger to the Process

This topic shows how to attach and detach the Visual Studio debugger to the Microsoft Identity Lifecycle ManagerĀ 2007, Feature PackĀ 1 service process in order to debug your extension.

ms694624.wedge(en-us,VS.85).gifTo attach the Visual Studio 2005 debugger to the Microsoft Identity Integration Server (MIIS) service process, perform the following steps.

  1. Ensure the current version of the extension class library is copied to the Extensions folder under the ILM 2007 FP1 installation folder.

  2. Open the extension project in Visual Studio 2005.

  3. Insert any required breakpoints.

  4. Select Debug, and then Attach to Process from the Visual Studio 2005 menu. The Attach to Process window is displayed.

  5. In the Available Processes window, make the following settings:

    • Set Transport: to Default.
    • Set Qualifier: to the MIIS server computer name.
    • Select the Show processes in all sessions check box.
  6. In the Available Processes list, select a process and press the Select button to select the code type to attach to. The Select Code Type dialog box is displayed.

    • For rules extensions, select miiserver.exe. The extension must be configured to run in-process.
    • For connected data source extensions, select miiserver.exe if running in-process or dllhost.exe if running out-of-process.
  7. In the Select Code Type dialog, select the Debug these code types option. Check the Managed check box and clear all other check boxes. This step is important because it affects what happens when the debugger is stopped or detached. If Native is selected, the MIIS process will have to be terminated to stop debugging.

  8. Press Attach in the Attach to Process dialog box to attach the debugger to the selected process.

  9. The debugger is now attached to the miiserver.exe process.

Detaching the Debugger

When debugging is complete, the debugger is detached from the process by selecting Debug - Stop Debugging in the Visual Studio 2005 menu.

Send comments about this topic to Microsoft

Build date: 2/16/2009