Hi guys,
probably I'm not the first to hit this issue, but I haven't found anything on the forum....
I'm planning to invoke a sequence in the PreExpr of my step definitions (to add GUI messaging). As an example, I refer to this this.
It works invoking sequences without parameters. As soon as parameters for the sequence to be called are introduced, I get errors.
![tserror.png tserror.png]()
The PreExpr used is
RunState.Engine.NewExecution(SeqFileReference, "SeqName", Nothing, False, 0, Step) where Step is the container to be passed.
During debugging, I found out, that using this PreExpr with a standard step (in this case a Statement) placed in the sequence, everything works as expected.
So I removed the PreExpr from my Typedef and retried inserting the PreExpr into the step manually. No luck...
![tserror2.png tserror2.png]()
So... is there a context-wise difference between the PreExpr used in the (user) TypeDef of the step and the NI Typedef?
Cheers
Oli
BTW.... still on TS2013 / Win7