Hello!
Based on your earlier question in another thread, we'll assume that you're considering using ClearScript with JScript/VBScript rather than V8.
If that's correct, then yes, ClearScript uses the same JScript and VBScript engines as the Windows Script Control. However, as you pointed out, it also uses .NET facilities such as COM Interop and Reflection, and brings together components that were designed for fundamentally different environments.
To answer your specific questions:
Yes, ClearScript can be used in a 64-bit ASP.NET app. However, JScript and VBScript instances have thread affinity and therefore require careful handling in server applications. Also, ClearScript doesn't support certain server-friendly features, such as cloning. Finally, we've observed some JScript and VBScript bugs that are specific to the 64-bit versions of these components.
We're not currently aware of any memory leaks related to the use of COM Interop and Reflection, but of course there may always be bugs in any layer. We try to investigate issues as they're reported, but please keep in mind that this an open-source project with no official support.
Thanks for your questions, and good luck!
Based on your earlier question in another thread, we'll assume that you're considering using ClearScript with JScript/VBScript rather than V8.
If that's correct, then yes, ClearScript uses the same JScript and VBScript engines as the Windows Script Control. However, as you pointed out, it also uses .NET facilities such as COM Interop and Reflection, and brings together components that were designed for fundamentally different environments.
To answer your specific questions:
Yes, ClearScript can be used in a 64-bit ASP.NET app. However, JScript and VBScript instances have thread affinity and therefore require careful handling in server applications. Also, ClearScript doesn't support certain server-friendly features, such as cloning. Finally, we've observed some JScript and VBScript bugs that are specific to the 64-bit versions of these components.
We're not currently aware of any memory leaks related to the use of COM Interop and Reflection, but of course there may always be bugs in any layer. We try to investigate issues as they're reported, but please keep in mind that this an open-source project with no official support.
Thanks for your questions, and good luck!
