-
Notifications
You must be signed in to change notification settings - Fork 150
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How do I deploy a 64-bit ClearScriptV8 assemblies globally (at the machine level)? #117
Comments
Hi Andrey, Unfortunately ClearScript currently doesn't support global deployment. In theory the official ClearScript* assemblies are GAC-able, but the v8* assemblies are native and loaded manually via an algorithm that assumes application-level deployment. We'll look into adding support for machine-level deployment in the future. Thanks! |
Thanks for information! As I understand it, we cannot deploy native assemblies globally due to this logic. |
…y, GitHub Issue #114); added initial support for CommonJS modules (V8 and JScript); added ScriptEngine.ExecuteDocument and ScriptEngine.EvaluateDocument; added V8ScriptEngine.CompileDocument and V8Runtime.CompileDocument; added support for machine-level deployment (GitHub Issue #117); added Extensions and JavaScriptExtensions to facilitate specific scenarios; added implicit conversion of host method arguments via user-defined operators (GitHub Issue #115); patched a V8 issue that causes occasional script execution failure in 32-bit processes (GitHub Issue #111); fixed accessibility of public methods overriden by internal classes (GitHub Issue #112); updated deployment and API documentation. Tested with V8 7.6.303.28.
ClearScript 5.6 supports machine-level deployment. It doesn't provide an installer, so you'll have to use |
Thank you! |
Hello!
Is it possible to globally deploy the following assemblies:
ClearScript.dll
,ClearScriptV8-64.dll
,v8-base-x64.dll
andv8-x64.dll
? I.e. I need to understand what assemblies should be registered in the GAC, and which copied to to theC:\Windows\System32
directory.The text was updated successfully, but these errors were encountered: