While Inventor software’s VBA and iLogic provide a convenient and easy way to add custom functionality to Inventor, there are limitations to what you can do with VBA macros and iLogic rules. This class will introduce you to VB.NET and Inventor add-ins and the pros and cons of add-ins compared to VBA and iLogic. In this class, you'll learn the technical differences between VBA, iLogic, add-ins, and external EXEs, and some of the reasons you would choose one over the other. The class will also cover how to create an add-in using an easier-to-use custom VB.NET template. We'll also look at the differences between VBA code and VB add-in code and how to convert your existing VBA macros and iLogic rules into add-in commands. We'll also cover how to debug your add-in. Finally, we'll look at how to package and distribute your add-in to make it easy for others to use. This is an intermediate level class and you should have a basic understanding of the Inventor API.
- Discover when an add-in is the best option
- Learn how to convert existing VBA and iLogic code into an add-in command
- Learn how to debug an add-in
- Learn how to package and distribute your add-in
CAD has been a passion of mine ever since I saw a demonstration of an Applicon system while on a field trip in high school in 1977. My experience in the industry since then has been varied, but always customer focused. I started out developing courses and teaching customers how to use Intergraph’s mechanical CAD software. I then transitioned into an Application Engineering role where I provided technical support to the sales organization by conducting tests (benchmarks) of Intergraph’s CAD software for potential customers based on their designs and requirements. Benchmarks involved working with customer to understand their needs and then modeling parts, creating assemblies, performing analyses, producing detailed drawings, and machining parts. I specialized in complex modeling and customization of the software. When Intergraph began developing Solid Edge, they asked me to design the programming interface (API). I had been a user of API’s but API design was a completely new role. They asked me because they wanted someone to do it that had a user’s perspective. I designed the API for the Solid Edge and then moved to Autodesk where I designed the API for Inventor and most recently, I’ve been designing the API for Fusion 360. As part of those roles, I’ve written the documentation and many of the sample program, taught classes, and supported everyone using the API’s. Now I run my own consulting/contracting business where I help Inventor and Fusion 360 users turn the software into a tool specific to their needs. Contact me if you need help with your use of the software.