Addon wont load (gets in dependentdlls), but no errors with verbose logging

[TendenZ]

We have a user in which an add-on of ours (Act! Salutation Tool ) is blocked by Act!. This addon dll is called 'Aanheftool' (see log below).

As usual, we've raised the Act! loglevel to '4' (verbose), removed the entry from dependentdlls.xml, and started Act!.

It's immediately added again to dependentdlls.xml, but no errors are logged. 

We did find some strange info messages, as shown below.

Any ideas? Corrupted Act! install or profile?

<Message Timestamp="10:22:59.878" Type="Message" Category="UI" Severity="Info">
      <Message><![CDATA[Setting enable for: act-ui://com.act/application/menu/Tools/AanhefTool_showConfigScherm to: Falseat Act.UI.Core.CommandBars.GetBarControl() in :line 0]]></Message>
    </Message>

    <Message Timestamp="10:22:59.881" Type="Message" Category="UI" Severity="Info">
      <Message><![CDATA[Command not found. Can not set enable for: act-ui://com.act/application/menu/Tools/AanhefTool_showConfigScherm to: Trueat Act.UI.Core.CommandBars.GetBarControl() in :line 0]]></Message>
    </Message>

[jimdurkin]

If you wrap your code which is failing in a TRY what message do you receive?

-- Jim 

[TendenZ]

Like in .. put the whole giant add-on in a try/catch blcoK?

We don't know from which point it's being blocked.

[jimdurkin]

I always try/catch the entry point of the addon

  Private Sub OnLoad(ByVal ActApplication As Global.Act.UI.ActApplication) Implements Act.UI.IPlugin.OnLoad
       
        Try
           '------------------------------------------
           ' Delete the last log file
           '------------------------------------------
           Durkin.Common.Utilities.LogError.DeleteLogFile()


          ' your code here

        Catch ex As Exception
            LogError.Write(ex, "OnLoad:ImpactAct")
        End Try
   

    End Sub

If you do not pick up the Catch in your code then Act is not loading your addon.

Inside the ACTLOG.XML file. It will document the reason why Act did not load your plugin.

Follow these step to retrieve the Act Error Log

1) Change the error logging to 4 in the Act!.exe.config file
    By default its set to 1 but at 1 sometimes Act does not log the reason it bypassed the addon. Setting it to 4 usually forces act to log the reason.
2) Delete the DependentDlls.xml file.

    Once the addon has been blacklisted into this file, Act will ALWAYS bypass it. Once you have been blacklisted you need to delete this file to force Act to releaod all the DLL files in the plugins folder.

3) Delete the ACTLOG.XML file.

4) Start Act

  After starting Act wait till the entire UI loads then close Act. Its on the close event Act updates the ActLog file.

Hope this helps

-- Jim 

[Si4lvester]

When you attempt to load such a DLL and one of the dependent DLLs doesn't exist you get a nasty Windows dialog tellpopeyes.