-
Notifications
You must be signed in to change notification settings - Fork 926
ReactEngineNotFoundException on Azure #400
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
Comments
I'm running into the same issue. My .NET Core 1.1 web application works locally, but throws an exception when published:
Since it seems to be an issue with the JavaScript engine, I thought adding I think we may need to do something along the lines of this article, but the last few steps are outdated: http://www.samulihaverinen.com/web-development/dotnet/2016/01/19/how-to-run-clearscript-v8-javascript-engine-in-azure/ |
I was able to get the application working when published to Azure using a combination of these guides: From the first guide, I installed dependencies separately: From the second guide, I installed a package to enable JavaScriptEngineSwitcher configuration in .NET Core 1.X: In Startup.cs ConfigureServices(): |
@jyee117 This package is not needed. I recommend you to read the documentation. |
@andpoulsen @jyee117 I recommend to read the “Misconceptions about the JavaScript Engine Switcher version 2.X” post. |
This save me, thanks. |
@andrewwang1tw I recommend you to read the “ChakraCore” section of “Misconceptions about the JavaScript Engine Switcher version 2.X” discussion. |
Closing issues older than a year, please re-open if you think this is still relevant. |
I'm building an asp.net mvc core application with server side rendering and I get ReactEngineNotFoundException, when I deploy to Azure.
You might see the entire callstack yourself here: http://dotnetopeniddemo.azurewebsites.net
I have created an Azure web app, and I'm deploying to it from Visual Studio. It works locally in IIS Express, but not on Azure.
The text was updated successfully, but these errors were encountered: