-
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
ASP.NET Core 3.1 w/ClearScript Azure Web App #166
Comments
Hi @upsilondynamics, What is your web application's host operating system? ClearScript requires Windows, but at the moment Azure appears to support .NET Core 3.1 only on Linux (see here). Thanks! |
Running Windows on the app resource. If you look closely at the links you sent they had it globally launched Dec 13th I believe. And the second link in the answer states others are able to confirm 3.1LTS working on windows containers. So if clearscript requires windows I don’t think this is the issue. |
@ClearScriptLib Is there a way to add something like this, I remember having to add this for .NET Framework 4.7: I also remember I had to move the assemblies out from the root of the directory to bin\ClearScript.V8: Also, why is it working locally, but not on Azure?
|
Full stack trace when I try and move the files out of the root (x64)
|
And.. when I leave it in, why is it saying it's an incorrect format when it's clearly marked x64?
|
Hi @upsilondynamics, Thanks for reporting this issue. We've identified the cause. Despite the unfortunate error message, the problem is a missing 64-bit Visual C++ component named VCRUNTIME140_1.DLL. It was added in a recent update but apparently has yet to make its way to Azure's ASP.NET host configuration. You can read about the component and its related compiler feature here. We'll disable this feature in our next release, temporarily eliminating ClearScript's dependence on VCRUNTIME140_1.DLL. We'll then re-enable it when Azure's ASP.NET PaaS has been updated. In the meantime you have several options:
Please let us know if any of these options work for you, and thanks again for reporting this! |
Let me start by saying YOU GUYS ROCK. Your proposed solution worked, for the time being I will simply package that DLL into my build pipeline and should be good.. Thanks for working so hard on getting a solution this quickly. |
Would there be any major disadvantage to link to the VC runtime statically instead of depending on the DLL? We are using ClearScript extensively, and it does cause hard-to-debug issues sometimes that the correct version of the redistributable needs to be installed. |
Hi @erik-kallen, Unfortunately static linking can't be combined with CLR support for C++:
Sorry! |
That's a shame :( |
…Hub Issue #160); fixed 64-bit V8 initialization on Azure App Service (GitHub Issue #166); enabled DirectAccess for ComVisible .NET objects (GitHub Issue #161); added ScriptEngine.ExposeHostObjectStaticMembers (GitHub Issue #152); added ScriptEngine.UndefinedImportValue and made Undefined.Value public (GitHub Issue #154); enhanced ExtendedHostFunctions.typeLibEnums to pull in external enumerations; added thread affinity enforcement in WindowsScriptEngine.Dispose; eliminated KeyNotFoundException when checking for system documents (GitHub Issue #169); enabled the use of the application's root folder as a backup for its local data folder (GitHub Issue #171); reduced minimum CPU profile and heap size sampling intervals to 125 ms; updated deployment and API documentation, resolving GitHub Issues #158 and #159. Tested with V8 8.1.307.28.
Fixed in Version 6.0.1. |
Having issues when I deploy my .NET Core 3.1 app to Azure (ASP.NET CORE).
Runs locally without issue, what causes this? All the projects are set to build as x64 if that makes ay difference. Files that exist in the site/wwwroot:
D:\home\site\wwwroot>ls ClearScript*.dll
ClearScript.dll
ClearScriptV8-32.dll
ClearScriptV8-64.dll
D:\home\site\wwwroot>ls v8*.dll
v8-base-ia32.dll
v8-base-x64.dll
v8-ia32.dll
v8-libcpp-ia32.dll
v8-libcpp-x64.dll
v8-x64.dll
Works locally without issue, why is it not working when deployed as an Azure Web App?
The text was updated successfully, but these errors were encountered: