You have started to automate repetitive workflows by writing iLogic rules that utilize Inventor API methods, and you’re possibly creating big iLogic “forms,” and now you’re wondering if you should abandon iLogic and jump to an add-in instead. In this class, we will examine the pros and cons of using an add-in versus using iLogic rules (internal and external), and also consider the use of a .NET class library. It turns out that all of these options are compatible with each other, so we’ll also learn how they can work together, and how and where to “draw the line” between these different tools. To get the most out of this class, you should be comfortable writing iLogic rules and forms. You don’t have to be a programmer, but you shouldn’t be scared of looking at code.
- Learn how to identify key indications for when to use rules versus add-ins versus class libraries
- Understand the pros and cons of each technology versus the others
- Understand the basic components and software “plumbing” required for an add-in
- Discover how easy it is to use a custom class library from iLogic rules