Implicit reference in all iLogic rules

Implicit reference in all iLogic rules

mat_hijs
Collaborator Collaborator
188 Views
2 Replies
Message 1 of 3

Implicit reference in all iLogic rules

mat_hijs
Collaborator
Collaborator

I have created a dll that includes some subs and functions that I want to be able to use in iLogic rules. I can do this by writing the following statement in the header of the rule.

AddReference "MSInventorTools.dll" 

 This works perfectly, but I'm wondering if there's a way to create an implicit reference to this dll so that I don't need to explicitly reference it in every rule I write. Does anyone have any idea if this is possible?

189 Views
2 Replies
Replies (2)
Message 2 of 3

bradeneuropeArthur
Mentor
Mentor

You have created your dll with vb.net or equal. Why are you not directly creating an add in. I only see benefits of this approach, and using ilogic for design configuration and testing only.....

Regards,

Arthur Knoors

Autodesk Affiliations & Links:
blue LinkedIn LogoSquare Youtube Logo Isolated on White Background


Autodesk Software:Inventor Professional 2025 | Vault Professional 2024 | Autocad Mechanical 2024
Programming Skills:Vba | Vb.net (Add ins Vault / Inventor, Applications) | I-logic
Programming Examples:
Drawing List!|
Toggle Drawing Sheet!|
Workplane Resize!|
Drawing View Locker!|
Multi Sheet to Mono Sheet!|
Drawing Weld Symbols!|
Drawing View Label Align!|
Open From Balloon!|
Model State Lock!
Posts and Ideas:
My Ideas|
Dimension Component!|
Partlist Export!|
Derive I-properties!|
Vault Prompts Via API!|
Vault Handbook/Manual!|
Drawing Toggle Sheets!|
Vault Defer Update!

! For administrative reasons, please mark a "Solution as solved" when the issue is solved !


 


EESignature

0 Likes
Message 3 of 3

mat_hijs
Collaborator
Collaborator

The biggest reason for this is that it's a lot easier to quickly create or modify a rule that does something and throw it away when I'm done with it than it is to incorporate it into an add-in. For static things, definitely the add-in would be better.

The second reason for this could be when using custom classes to represent custom objects. I don't want to copy the whole code of the classes to every rule, and I'd also like to avoid having to add a reference manually every time I write a new rule. This mostly comes in when building configurators for me.

Another example for me is when using Excel, when I do it in iLogic I don't seem to have any issues, but when using the same code in an add-in, for some reason Excel often keeps running in the background after the code was ran. I've been searching how to solve this and came across some things about releasing objects, but this still doesn't seem to fix all my issues.

0 Likes