Hi niconico49,
Thanks for providing so many details.
We're sorry to hear that this issue is still blocking you, but we still can't reproduce it. On a machine running 32-bit Windows 7 and Visual Studio 2012, we created a Visual Basic ASP.NET project, added a reference to ClearScript.dll, added the other DLLs as content files at the root, and added some code that invokes the V8-based script engine and displays the result in the home page. Everything just works.
Can you think of anything else about your project that might be different or non-standard in any way?
If you can't share your project, one thing we could do is give you a slightly modified version of ClearScript that collects error information returned by the
Thanks!
Thanks for providing so many details.
We're sorry to hear that this issue is still blocking you, but we still can't reproduce it. On a machine running 32-bit Windows 7 and Visual Studio 2012, we created a Visual Basic ASP.NET project, added a reference to ClearScript.dll, added the other DLLs as content files at the root, and added some code that invokes the V8-based script engine and displays the result in the home page. Everything just works.
Can you think of anything else about your project that might be different or non-standard in any way?
If you can't share your project, one thing we could do is give you a slightly modified version of ClearScript that collects error information returned by the
LoadLibraryW function. Are you interested in trying that? It might provide a clue.Thanks!