Hi @lkirit2000. The primary programming language used within iLogic rules is VB.NET. In Inventor 2024 and earlier, they were using VB.NET Framework 4.8.1 version, but then in Inventor 2025 they bumped it up to VB.NET 8 (on the 'Core' side), and now in Inventor 2027 they are encouraging everyone to start using VB.NET 10, and convert all of their Inventor application add-ins to that version also. But Inventor add-ins and external standalong exe's are a whole other subject than iLogic rules, because we can use various other coding languages in add-ins and standalone exe's. The term 'iLogic' is the name of an add-in within Inventor which has its own API (Application Programming Interface)...the iLogic Rule Editor dialog. That interface if pretty simplistic (or basic) looking compared to some other external code editors. The iLogic system contains a lot of 'helpers' to help make automating common tasks within Inventor as simple & easy as possible. So, if you do not have any (or much) previous coding experience, iLogic can be a pretty good gateway into it, opening a door to a whole world of automation possibilities, which can potentially reach far beyond the boundaries of the Inventor application.
As far as learning resources, there are lots of avenues available, but likely no single resource will provide everything there is to know on the subject. There have been multiple similar inquiries here within this Inventor Programming Forum, one of which I participated in not that long ago (Link Below).
https://forums.autodesk.com/t5/inventor-programming-forum/ilogic-syntax-language/td-p/14151920
The first resource I would recommend reviewing is Inventor's own help documentation in the areas of Inventor's API, the iLogic API, and related iLogic UI resources documentation.
If you are not familiar with reading or writing code using the vb.net coding language, then there is a TON of documentation and tutorials about that online which can be very helpful also. The following Link can be considered the 'front gate' to Microsoft's online documentation for that system. You will see the term .NET commonly used, because it covers multiple variations, which vb.net is the 'Visual Basic' language variation of. The other popular main branch is C# (C-Sharp).
https://learn.microsoft.com/en-us/dotnet/api/
I also get a lot of good vb.net coding information & examples from the StackOverflow website, because they have been around for decades and have TONS of question/answer topics to browse through that have been voted on, and commented on over the years by other coding peers, which sometimes provides even more insights.
Conducting searches within this forum for topics or tasks that you may be interested in trying to automate within Inventor, reading through the conversations, and trying out some posted codes that are marked as 'accepted solutions' can be a good learning path as well. Of course not all discussions or code examples found in forums will provide detailed explanations of everything involved, or well commented code examples that explain what each line of code is supposed to be doing, so sometimes you may end up with 'working' code that you do not understand how it works, then the learning how it works part may come later.
There is are also a lot of useful resources available within Autodesk University, if you do a search for 'iLogic' in there.
Several of the other folks who frequent this forum regularly to help others out also have their own 'blog' type sites, and of course Autodesk has their own Blog site too. There are several 'iLogic' related blog posts in the Autodesk sector too. I can post a few Links to them below, for convenience.
https://forums.autodesk.com/t5/community-blog-d-m-english/making-inventor-ilogic-work-for-you/ba-p/1...
https://forums.autodesk.com/t5/community-blog-d-m-english/how-to-identify-processes-ready-for-ilogic...
And below is a Link to the Autodesk Learn site, where the term 'Inventor iLogic' has been searched. It has Links to several topics you may find helpful.
https://www.autodesk.com/learn/catalog/Inventor%20iLogic
Wesley Crihfield

(Not an Autodesk Employee)