Author Topic: CAMduct does not honor the "Always Load" for an add-in that cannot be verified  (Read 731 times)

0 Members and 1 Guest are viewing this topic.

Offline srivesTopic starter

  • Active Member
  • **
  • Posts: 3
  • Country: us
  • Gender: Male
I wrote a CAMduct add-in that is not signed. I have had difficulties getting it signed because Fabrication API.DLL is not strongly named. But that's not my question.

Given that my add-in is not signed, I would still think that CAMduct would always load (after the user clicks "Always Load"), and stop telling them that the add-in is unverified on subsequent loads.  I have attached a screen shot of the "Always Load" option that comes up. Alas, the next time CAMduct starts up, it asks the question all over again. That is, "Always Load" seems to be unrelated to always.

My addin gets installed under the "c:\Program Files\" directory (which I read in one place was needful for this to work).

FYI: I am running with admin rights and full authority on my own machine (and I see the problem). I launch CAMduct with admin rights to make sure that's not an issue. Also, I did try adding my addin by key to the codesign section in the windows registry, here: HKEY_CURRENT_USER\Software\Autodesk\Fabrication 2020\CodeSigning -- I found this solution on a help page, but it has does not help with the issue at hand.

Thanks for any help!

Steve

Online Admin

  • Administrator
  • Premier Member
  • *****
  • Posts: 1432
  • Country: gb
  • Gender: Male
I do NOT offer support to forum postings via email, IRC or any form of instant messaging network. If you want help, ask here!

Offline jaysomlam

  • Senior Member
  • ****
  • Posts: 486
  • Country: us
  • Gender: Male
We get the same problem in where I work ever since 01/21/2020.  That "Always Load" option worked fine before that.  The problem might have occurred a week earlier than 01/21/2020; but I only noticed this on 01/21/2020.

Not sure when your problem started -- or if yours ever worked before.  My network administrator said that he didn't change any Group Policy at that time.  May be Windows or Autodesk changed something and triggered the problem?  No idea.

So far, I just ask shop users to click the button and move on.  No one seems to care about this.  But I surely hope there is an easy solution to this problem.

Jaysom

Offline jaysomlam

  • Senior Member
  • ****
  • Posts: 486
  • Country: us
  • Gender: Male
I don't have this problem right after I have upgraded to CAMduct 2024.

I had this problem when I was using CAMduct 2019.

Not sure from which version of CAMduct that this problem fixed.

Jaysom