Table of Contents

Debugging a connector

When you have finished configuring all necessary settings, you can start debugging.

  1. In the DIS menu, go to DMA > Connect, and select the DataMiner Agent to which you want DIS to connect.

  2. Import the protocol. In the DIS menu, select DMA > Import Protocol, select a protocol and a version, and click Import.

  3. In the XML editor, go to the QAction that you want to debug, and click the Edit C# button in front of it to open the QAction in a C# editor.

  4. In the C# editor, set the necessary breakpoints.

  5. In the DIS menu, select Tool Windows > DIS Inject to open the DIS Inject window.

  6. Select the Protocol tab.

  7. Open the large selection box at the top of the window, and select an element that uses the exact same protocol as the one you are currently editing.

  8. In the QAction list:

    1. Go to the row of which the QAction ID matches that of the QAction you have opened.
    2. If necessary, in the Project column, select another temporary QAction project.
    3. Click the green plus to replace (i.e. inject) the element's QAction.dll file (compiled in Release mode) with its counterpart found in the temporary QAction project (compiled in Debug mode).

  9. Click the Attach button to build all temporary QAction projects and attach the Microsoft Visual Studio Debugger to the DataMiner SLScripting process.

  10. In the DIS Inject window, click the yellow lightning bolt to manually trigger the QAction by simulating a change of the parameter selected in the Trigger ID box (in case of a dynamic table parameter, use the Trigger Key box to specify the table row).

    Note
    • Instead of clicking the yellow lightning bolt, you can also open DataMiner Cube, connect to the DataMiner Agent to which DIS is connected, and perform an action in the user interface that triggers the QAction you are debugging.
    • When a QAction refers to another QAction in a DllImport attribute, then that referenced QAction will now also automatically be injected when you debug a protocol in DIS.
Tip

Debugging is often not possible for third-party libraries. dotPeek can serve as a handy tool to overcome this.

Propose changes