Inventor iLogic, Macros, AddIns & Apprentice Forum. Share your knowledge, ask questions, and explore popular Inventor topics related to programming, creating add-ins, macros, working with the API or creating iLogic tools.
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Show only
|
Search instead for
Did you mean:
This page has been translated for your convenience with an automatic translation service. This is not an official translation and may contain errors and inaccurate translations. Autodesk does not warrant, either expressly or implied, the accuracy, reliability or completeness of the information translated by the machine translation service and will not be liable for damages or losses caused by the trust placed in the translation service.Translate
I'm starting a new project that will be used with Inventor 2008 on a mix of 32bit and 64bit machines. Mostly 64bit. Since this a brand new project with no code written yet which would you use? VBA or a .NET Addin?
VBA will be easier to deploy/update. An addin seems like it would be less problems with interoperablity with later version of Inventor on 64bit machines. What are other things I should be watching out for.
I cannot advice you on the 32 vs 64 bit issues. But .Net is so much easier as a programming tool in comparison to VBA, that I would recommend .Net for any project unless it is a tiny project. Deploying and updating through an AddIn is not much harder. Just compile a new setup file and send it around...
