Releases: eswann/ClearScript.Manager
Defaulting Byte Restrictions to 0 now as this was causing crashes
Defaulting Byte Restrictions to 0 now as this was causing crashes (default was too small)
Per @rushfrisby:
Actually maybe it does have something to do with ClearScript Manager... in the RuntimeManager constructor a V8Runtime is being constructed with V8RuntimeConstraints. I just read that because of changes in V8 that it is recommended to use the empty constructor for V8Runtime.
Release 1.3.4 - Added access to Engine
Added access to V8Engine directly:
-
RuntimeManager now has a GetEngine() method to return the current engine. Note, that the engine will be disposed when the runtime manager is disposed.
-
Execute functions now return a reference to the engine so that it can be used to retrieve script objects after execution, as in engine.Script.{dynamic object name here}
-
Made pooling logic slightly more efficient. If runtime is available, won't add a new runtime to the pool
Better Support for Require and improved documentation
Better Support for Require and improved documentation
See the Readme for details.
Added V8 Debug support in settings
Added support to Enable V8 Debug and set the V8 debug port in settings. See the readme for more info.
Fix for not disposing cancellation token
Fix for not disposing cancellation token when script with timeout completes
ClearScript.Manager.Http
- Split out ClearScript.Manager.Http to encapsulate Http functionality so that System.Net.Http ref is not needed for people that don't need this functionality.
- Added abililty to "require" other scripts or resources within a script using the Nodesque "require" syntax. More documentation to follow on this. This can be used for both .Net objects and types as well as scripts if they are placed in the new RequiredPackage class.
Bug Fixes - ScriptEngine had a lifecycle issue where it was disposed before some allowing users to retrieve script elements.
- ScriptEngine is now not automatically disposed unless RuntimeManager.Cleanup is run or until the ManagerScope is ended.
- Added RuntimeManager.Cleanup to support above.
Added ability to run multiple main scripts.
- Added ability to run multiple main scripts. RuntimeManager.ExecuteAsync now takes an IEnumerable of IncludeScripts. These can be code, file, or Uri references. They are compiled and run in order.
Added ability to run external scripts.
Added ability to load and run external scripts before running the main script.
Added ExecutionOptions and obsoleted/removed some existing calls for executing scripts.
Added System.Net.Http to load scripts.
Small updates for better inline documentation and fix for obsoleted property.
Small updates for better inline documentation and fix for obsoleted property.
Release to support ClearScript 5.4
Release to support ClearScript 5.4
Now depends on ClearScript.Installer for ClearScript references.
(https://www.nuget.org/packages/ClearScript.Installer/)