Learning to write iLogic

[Anonymous]

Hello, 

I am just getting started after doing some extensive research on ilogic and after listening, watching and reading along with discussions I have had with others. I am curious if I can write code in iLogic using C# or if  Iwould have to stick to vb

[bretrick30]

To actually use the iLogic snippets and write code in the iLogic Rules Window, you have to use VB.net.  You can use C# to create an external program and use the Inventor API, or create a .dll written in C# and reference it through an iLogic rule.  

[Anonymous]

as Bret said, iLogic is Inventor's internal functionality that runs just on VBA. if you would like to use C# you will need to either create an Add-in or a standalone program that uses Inventor API to connect to the program.

the thing is if you are just trying to do a simple task, as forms and iLogic snippets are offered within inventor, maybe its better to use iLogic because while creating an add-in you will need to manage its appearance, UX, UI and more too, and based on your obsession its a bit time consuming.

[JamieVJohnson2]

To answer the question, the iLogic IDE was only designed to work within the Visual Basic realm.  The iLogic IDE actually understands VB.Net syntax (version 7) better then VBA syntax (version 6), but its object tree is a hybrid of both, such as being able to use ThisApplication to get Inventor.Application vs martialing.  If you attempt to so a simple c#.Net property it will not be understood within the iLogic IDE as it attempts to interpret your code as VB.Net.

Perhaps the real question is what do you want to do with your tools? 

I have written several tools for Inventor that remain in Visual Studio .Net environment as a standalone exe (all VB.Net for me, but C#.Net would work fine there).  I simply acquire the Active Inventor or create a new one.  Then I go to work on said application.  The advantage here, is my tools can 'screw up' without stopping Inventor, and that separation has come to help out many times.  I'm even able to parallel compute here ( w 2019 and carefully).

In fact the only thing I use iLogic for is a document embedded code that runs upon a limited set of iLogic event triggers such as before save.  I have written VS VB.Net code to create iLogic code in the iLogic IDE, and in general it is all of the same syntax as the VS VB.Net code.

If reacting to event triggers was your goal, you could use the Add-In method (a template for Visual Studio .Net that is installed with the Inventor API) to create an Inventor in process Add-In that can react to a much larger array of events to perform custom user interaction with your tool. 

As for 'forms' you can use Windows Presentation Foundation (WPF) or Windows Forms from the VisualStudio .Net framework, even doc it within an Inventor palette window.  iLogic forms are not the only method.

So if your already familiar with the .Net environment, then skip over the iLogic IDE and go straight to playing with us 'big boys and girls' in Visual Studio.  Either way, the Inventor API object tree is the same.  Only within iLogic there are some shortcuts that can be made such as getting a property value in one line.  iLogic IDE is growing each year, but the core tools in the .Net still have more control.