- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report
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.