Announcements
Attention for Customers without Multi-Factor Authentication or Single Sign-On - OTP Verification rolls out April 2025. Read all about it here.

My addin is causing "Assembly Bonus Tools" to fail to load.

josh.nieman
Advocate

My addin is causing "Assembly Bonus Tools" to fail to load.

josh.nieman
Advocate
Advocate

This is a weird one.  I can't figure out what's going on here.  I can repeatedly cause this issue.

Has anyone run across an issue like this or know where to start looking?  This is very weird.


With Inventor open, I unload both addins and uncheck "automatic load" for both.  
Close Inventor.

Open Inventor.
Load Assembly Bonus Tools.  Set it to load automatically.
I do not load my addin.
All is well.

Close Inventor.  Launch again.
Assembly Bonus Tools is working fine.
Load my addin.
Everything is working fine.
Set my addin to load automatically.
Close Inventor.

Launch Inventor.
Assembly Bonus Tools does not load its commands.
At this point I can manually load Assembly Bonus Tools without error.
The commands show on the Ribbon but they do not execute.  It's like the click never sends.

0 Likes
Reply
297 Views
3 Replies
Replies (3)

JelteDeJong
Mentor
Mentor

I expect that your addin and the "Assembly Bonus Tools" use the same GUID. Your GUID is the large string you find in your addin file between <ClassId>....</ClassId>. You will also find the GUID in your "ApplicationAddInServer". ther you will find something like:

<GuidAttribute(".....-...-............"), ComVisible(True)>

just change them in bot locations. You need to use the same but something different from the "Assembly Bonus Tools"

Jelte de Jong
Did you find this post helpful? Feel free to Like this post.
Did your question get successfully answered? Then click on the ACCEPT SOLUTION button.

EESignature


Blog: hjalte.nl - github.com

0 Likes

josh.nieman
Advocate
Advocate

1) Changing the GUID of the .dll means everyone also has to replace their .addin file.  Right now our updates are pretty invisible because all I have to do is update the .dll and they have the most up-to-date next time they load Inventor.

2) This is a new problem for a .dll I've had deployed for over 2 years, and nothing has changed for either the Inventor installations or my .dll in regards to IDs since we updated to Inventor 2022 very shortly after the initial release.  I believe if it were a GUID conflict it would've cropped up before now, and I wouldn't be able to make either work at all when both were loaded.  I'm not sure about the latter, but I am pretty sure about the former.

Bonus: The odds are just very, very, very tiny.  From stackOverflow: https://stackoverflow.com/questions/39771/is-a-guid-unique-100-of-the-time
I use https://guidgenerator.com/ to generate GUIDs for each application and if they can be believed:

128-bits is big enough and the generation algorithm is unique enough that if 1,000,000,000 GUIDs per second were generated for 1 year the probability of a duplicate would be only 50%. Or if every human on Earth generated 600,000,000 GUIDs there would only be a 50% probability of a duplicate.

 
However, I will test a different GUID on my machine and report back.

0 Likes

josh.nieman
Advocate
Advocate

Well.

When I rebuilt with a new GUID, everything worked :grinning_face_with_smiling_eyes:

But now it's to see whether or not it's related to the GUID or some other ghost in the code that a GUID-change just 'fixed'


0 Likes