To avoid relying on resetting a single engine upon script invocation, you could instead cache scripts as objects, and assign each their own engine (doubtful on any significant performance hits).
You could then interact directly with a script object instead. A basic advantage of this would be the ability to limit CLR access based on script type.
To avoid relying on resetting a single engine upon script invocation, you could instead cache scripts as objects, and assign each their own engine (doubtful on any significant performance hits).
You could then interact directly with a script object instead. A basic advantage of this would be the ability to limit CLR access based on script type.