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

I agree with @R.Mabery.  I wasn't a career software programmer and didn't have a degree in programming (other than CNC machine programming), but now have years of experience writing a lot of both iLogic rules and VBA macros (not so much in Add-ins, due to corporate restrictions).  Although the VBA editor has a far more developed and useful user interface, and a nice built-in Object Browser that the iLogic rule editor dialog doesn't have, I still very much prefer creating my solutions using iLogic.  Inventor's iLogic is an Inventor Add-in that uses VB.NET as its basis, and has provided a TON of Inventor specific Interfaces, Types, and objects with lots of very useful methods, properties, and events to use to help us automate stuff in Inventor.  To me, using VBA is just a little older and clunkier feeling and the code is less condensed, often requiring more code to do the same thing.

One thing I do continue to use VBA macros for though is to be able to put buttons into my ribbons, so I can execute code with a single click.  I would gladly give up the VBA aspect of that equation though if Inventor would allow/expose a way to place buttons for iLogic rules directly in the ribbons (instead of 'macro' buttons) without having to have a macro run my rule, to set it up that way.

That's just my opinion though.

Wesley Crihfield

EESignature

(Not an Autodesk Employee)