I'm trying to do some fuzzy matching in a script, and want to use the SimMetrics.NET library for this, and I mocked it up in Visual Studio where it worked fine, then I added the assembly to the scripting references and tried my script in HS and it fails with the totally not helpful message:
Running script C:\Program Files (x86)\HomeSeer HS3\scripts\Sage.vb :Exception has been thrown by the target of an invocation.->Does entry point StartShow exist in script? at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor) at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Obj ect obj, Object[] parameters, Object[] arguments) at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture) at Scheduler.clsRunVBNetScript.ExecuteScript()
If I comment out the line where I instantiate the object, the error goes away, and I've even boiled it down to a script that does nothing but create a new Levenstein [sic] object in that library. If I just declare the variable, there are no complaints about the type definition (which would have a different, more useful error), but as soon as I "New" it, the script blows up.
Any thoughts?
Running script C:\Program Files (x86)\HomeSeer HS3\scripts\Sage.vb :Exception has been thrown by the target of an invocation.->Does entry point StartShow exist in script? at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor) at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Obj ect obj, Object[] parameters, Object[] arguments) at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture) at Scheduler.clsRunVBNetScript.ExecuteScript()
If I comment out the line where I instantiate the object, the error goes away, and I've even boiled it down to a script that does nothing but create a new Levenstein [sic] object in that library. If I just declare the variable, there are no complaints about the type definition (which would have a different, more useful error), but as soon as I "New" it, the script blows up.
Any thoughts?
Comment