Microsoft.ClearScript.Windows.Core VBScriptEngine - initializing.

[inavnapro]

Hi All,

How to initialize VBScriptEngine() in windows core? The constructor takes argument Isynclnvoker. How do I initialize the IsyncInvoker when creating vb script instance .NET core. For example:

/* Code example */
private VBScriptEngine vbsinstace;

public VBScriptEngine GetVBSCriptEngine()
{
if(vbsintance == null || vbsinstace.CheckAccess() == false)
{
vbsinstance = new VBScriptEngine(---NEED HELP WITH THIS PARAM---)
}
return vbsinstance;
}

Please advise. Thanks!

[ClearScriptLib]

Hi @inavnapro,

Like all Windows Script engines, VBScript has thread affinity, meaning that each instance can only be used on the thread that created it. Any attempt to use the script engine on the wrong thread results in an exception or possibly a crash.

ClearScript provides two managed wrappers for VBScript:

1. Microsoft.ClearScript.Windows.VBScriptEngine.
2. Microsoft.ClearScript.Windows.Core.VBScriptEngine.

The first class doesn't require an external implementation of ISyncInvoker. Instead, it provides its own implementation backed by an instance of Dispatcher. This version of VBScriptEngine is intended for desktop or console applications that have a main thread (or one or more UI threads). A multithreaded server could use it, of course, but it would probably have to manage a pool of dedicated script execution threads.

The other class allows the host to enforce thread affinity externally by implementing ISyncInvoker. This is mainly intended for multithreaded server use, but it could also be a good fit for simple single-threaded applications. If the host can ensure that the script engine is always invoked on the correct thread, it can use NullSyncInvoker.Instance to bypass thread affinity enforcement altogether.

Good luck!

[inavnapro]

Thanks!