Crashes form old iLogic code

[mporterC7FHA]

After Loading Inventor 2025, it crashes a couple of times a day doing simple things.  Other people on my team that are not running the iLogic code do not experience the crashes.  How can you find the parts of the code that are causing the problems?

[A.Acheson]

Hi @mporterC7FHA 

You will need to identify what rules are running and at what time before the crash. If you can isolate the rule then you can work to see what operation was being performed at the time. If you can then post the rule with information on the operation that led to the crash then we might be able to point out a solution or error catching methods to avoid failures like that.

[bradeneuropeArthur]

I always use message boxes to find where the rule stops or crashes.

Do you use external vb.net forms or dll files. Inventor 2025 has changed to net8! This may also lead into issues with I logic than!

[mporterC7FHA]

Thank you for the feedback. Now that I know what to look for, I can figure out what code is running when it crashes. Once I know what crashes it, I will post that so we can take the next step.

[mporterC7FHA]

There are no calls to vb,net or dll files, although there are calls to excel files.

[JelteDeJong]

Just some other points:

Inventor API is based on .Net core 8 (it used to be based on .Net framework 4.8.) It is a big upgrade but not very important if you are just creating simple iLogic rules. However, if your iLogic rules depend on other dll's (and they are based on .Net framework 4.8) then it might be possible to keep using them but that is not guaranteed. This is something you need to check. (Trial and error.)

A second thing that came up on the beta testing forums.

---

This is a case in which iLogic code that worked in Inventor 2024 and earlier will fail to compile on Inventor 2025. Here is a sample rule:

nameToFind = "Test"
Dim partDoc As PartDocument = ThisDoc.Document

For Each paramX As Inventor.Parameter In partDoc.ComponentDefinition.Parameters
    If paramX.Name.Contains(nameToFind) Then
       Logger.Info("Found {0}", paramX.Name)
    End If
Next


This will produce a compile error: "Late-bound extension methods are not supported."

There are several ways to fix it. The most general way is to change the line to:

If paramX.Name.Contains(nameToFind.ToString()) Then


The error happens because the "nameToFind" variable is an Object, and not a String. So the compiler is looking for an extension method named Contains (on the String class) which takes an argument of type Object instead of String.
In earlier versions of Inventor (running .NET Framework) it would automatically convert the argument to a String and find the Contains method.

---