iLogic; Developing and debugging

[Anonymous]

Hi!

What would be the best practices to use while developing and/or debugging any iLogic rules? I guess there is no way we can use "break points" and/or have anything similar to the "watch" in VBA

Also, any real life "tricks" woul be greatly appreciated.

Thanks in advance.

Yves

[MjDeck · Accepted solution]

You can develop and debug code in Visual Studio or Visual Basic Express.  Compile it to create a dll that is loaded and run from an iLogic rule.  Put most of your code in the dll.  Then when you have it working, you can cut and paste it to the rule.  This is a lot of work, but it can be worth it if you need to put together a lot of code.

 One minor thing you can do in iLogic to help with debugging is to add something like a Print statement (using the function Trace.WriteLine)  that will show you a log of what the rule is doing.   For instance:

Trace.WriteLine(" d0 = " & d0)

To see the output, you can run DebugView from

http://technet.microsoft.com/en-us/sysinternals/bb896647

(In Inventor 2010, you have to add the line:

Imports System.Diagnostics

at the top of the rule.)

[Anonymous]

Thanks Mike, 

this will surely help.

Yves