iLogic rule debugging an variable monitor

[Anonymous]

It would be great if a decent debugging/variable watch could be added to the iLogic environment.

While creating rules it is very difficult to do troubleshooting due to the lack of debugging/variable-watch availability. I have to use msgboxes or write a log.txt to check where the code fails or in the more complicated cases first make a vba macro and translate those back to ilogic where i sometimes run into conversion errors again...

I know iLogic is based on VB.net so why does it not have debugging capabilities?

[khoskins]

I constantly still start writing iLogic code within VBA because of the Locals dialog and line by line step-through functionality.  The lack of debugging is a huge missing feature of the iLogic IDE.  Intli-Sense was a huge step forward for iLogic but is still quite a bit behind VBA from a debugging perspective.

[miechh]

Indeed. Having to constantly switch between Visual Studio, (re)attach to process, starting the iLogic code, not being able to modify the running code in Visual Studio, writing down possible solutions for the generated errors, stopping the debug, returning to the iLogic Editor, typing new code and repeating this process costs a lot of time.

I would plead for not only adding a 'watch window',but for step-by-step debugging and being able to modify the running code in the iLogic Editor as well!