-
Notifications
You must be signed in to change notification settings - Fork 930
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
"Unable to load one or more of the requested types" server error after JavaScriptEngineSwitcher upgrade to 2.4.0 #417
Comments
Hello, Roman! Already there was a similar error - “Updating JavascriptEngineSwitcher.V8 breaks React.Net”. Also I recommend you to read the “Misconceptions about the JavaScript Engine Switcher version 2.X” discussion. |
It's also very similar to the fact, that you did not install packages with native assemblies. |
@Taritsyn, thanks for the quick response! I've noticed that setting For now, I still cannot influence the way ReactJS.NET seeking for required assemblies by registering JS engine factories manually. Do I still need to install native assemblies for V8 and ChakraCore engines even if I not register factories for them? |
Read about this problem in Daniel's comment. If you want to solve this problem, then vote for my pull request - “Added a ability to select the default JavaScript engine”.
Not necessary. |
Resolved in 3.1.0 release |
Error message:
Unable to load one or more of the requested types. Retrieve the LoaderExceptions property for more information.
Stack trace:
React.Core 3.0.1 and React.Web 3.0.1 installed from NuGet.
Upgraded packages:
JavaScriptEngineSwitcher.Core 2.4.0
JavaScriptEngineSwitcher.Jint 2.4.0
JavaScriptEngineSwitcher.Msie 2.4.0
JavaScriptEngineSwitcher.Jurassic 2.4.2
JavaScriptEngineSwitcher.V8 2.4.2
JavaScriptEngineSwitcher.ChakraCore 2.4.6
MsieJavaScriptEngine 2.2.1
All upgraded assemblies copied into website
bin
folder.Only Jurassic and Jint registered, both worked fine before JavaScriptSwitcher upgrade:
The text was updated successfully, but these errors were encountered: