Hello!
I use JavaScript engines in most modules of my open-source library - Bundle Transformer. JavaScript engines are used not directly, but through the wrapper – JavaScriptEngineSwitcher. Currently, I have a problem with using the Noesis Javascript .NET library under 64-bit version of IIS 8.X, and I see as a replacement the ClearScript.V8 library.
But there are following problems:
In addition, it would be good if the
I use JavaScript engines in most modules of my open-source library - Bundle Transformer. JavaScript engines are used not directly, but through the wrapper – JavaScriptEngineSwitcher. Currently, I have a problem with using the Noesis Javascript .NET library under 64-bit version of IIS 8.X, and I see as a replacement the ClearScript.V8 library.
But there are following problems:
- Bundle Transformer is used in some CMS, which register all used assemblies in GAC.
-
Bundle Transformer is used in the web projects of various types, including ASP.NET Web Pages sites. In ASP.NET Web Pages sites cannot store assemblies for different processor architectures in the root of
bin
directory, therefore it should be placed in subdirectories. For such cases in static constructor of the V8JsEngine class I determine and add search paths of the ClearScript.V8 assemblies. In order to be use JavaScriptEngineSwitcher.V8 in different projects types I wrote a special NuGet package.
V8Proxy.GetDirPaths
method.In addition, it would be good if the
ClearScript
assembly will be divided into 3 assemblies:ClearScript.Common
- common types and utilitiesClearScript.Windows
- windows script enginesClearScript.V8
- V8 script engine proxy