JavaScriptEngineSwitcher | JavaScript Engine Switcher determines unified interface | Runtime Evironment library
kandi X-RAY | JavaScriptEngineSwitcher Summary
kandi X-RAY | JavaScriptEngineSwitcher Summary
JavaScript Engine Switcher
Support
Quality
Security
License
Reuse
Top functions reviewed by kandi - BETA
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of JavaScriptEngineSwitcher
JavaScriptEngineSwitcher Key Features
JavaScriptEngineSwitcher Examples and Code Snippets
Community Discussions
Trending Discussions on JavaScriptEngineSwitcher
QUESTION
The project is an ASP.NET MVC Web App targeting the .NET Framework 4.6.1.
All of a sudden (some NuGet packages were upgraded) I started to get the following error during runtime:
CS0012: The type 'System.Object' is defined in an assembly that is not referenced. You must add a reference to assembly 'netstandard, Version=2.0.0.0, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51'.
In my main view Index.cshtml
, in a line where I make use of @Html.ActionLink
I do have .NET Core SDK 2.0 and .NET Framework 4.7.1 installed in my machine but I don't want to include a reference to it. This is a .NET Framework web app only, it's hosted on Windows IIS where the installed framework is 4.6.1, there's no NET Core installed in the server.
So why is it asking to add a reference to netstandard
? How can I fix it without referencing netstandard
but the full Windows .NET Framework 4.6.1?
I've checked out a previous commit which worked fine and I'm still getting this error. So it's not related to NuGet packages being upgraded. Seems to be something on my local dev machine.
If a publish the app to a directory and run it with IIS it works.
packages.config
...ANSWER
Answered 2018-Apr-24 at 20:14Might have todo with one of these:
- Install a newer SDK.
- In .csproj check for Reference Include="netstandard"
- Check the assembly versions in the compilation tags in the Views\Web.config and Web.config.
QUESTION
we are making a ASP.NET Core 3.0 application that has one part implemented in React. For that reason we Reactjs.Net library (the latest version) with WebPack bundler and server-side rendering. It works perfectly on my development machine but when deployed to Azure App Service I get the error:
ReactJS.NET has not been initialised correctly. Please ensure you have called services.AddReact() and app.UseReact() in your Startup.cs file
I have tried properly registering the JavaScript engines by using these tutorials from here:
- Publish to azure, asp.net core React app
- https://github.com/Taritsyn/JavaScriptEngineSwitcher/wiki/Registration-of-JS-engines
We are using the Chakra-Core engine JS engine and the ChackraCore.dll is being properly deployed to the Azure AppService in the x64 folder.
But this doesn't help. Don't know what to check. Any ideas?
...ANSWER
Answered 2019-Dec-12 at 15:01I had a similar issue with Reactjs.net library. The issue was that by default Reactjs.net uses the 64-bit version of Chakra-Core engine. Make sure that your Azure AppService is running in 64bit so that it can load the JavaScript engine dll. You can change it from Application Settings
QUESTION
I have an app which uses the Babel to transpile some dynamic JS into es5 compatible JS for use in IE browsers.
This setup works perfectly locally however once deployed to Azure I keep getting the following exception when trying to call
...ANSWER
Answered 2019-May-24 at 09:11Ok so thanks to some desperate trial and error it was simply a case of adding support for other platforms regarding the JavaScriptEngineSwitcher.ChakraCore.Native package, I originally had just the win-x64 but installing the win-x86 as well sorted it and got it working in Azure.
This was the end result for the packages I had installed to get my app successfully working in Azure:
QUESTION
I have a ASP.NET Core 2.1 web application with React.aspnet. It runs perfectly when running in IIS. But when I run it in Docker, the application can still run successfully but the view page with React failed with following error:
...ANSWER
Answered 2019-Apr-16 at 21:38I manage to fix the issue by installing different OS-specific versions of JavaScriptEngineSwitcher.ChakraCore.
QUESTION
Trying to build ReactJS.NET in Visual Studio 2015
...ANSWER
Answered 2019-Jan-15 at 08:19The docs show that you need to install this NuGet package, which contains the AddJsEngineSwitcher
extension method that's missing:
JavaScriptEngineSwitcher.Extensions.MsDependencyInjection
Once installed, you'll also need to add the following using
to include the namespace:
QUESTION
I am used to the "normal" React setup, but now I need to make one of my pages in my ASP.NET MVC admin system into a simple react app.
I have installed https://reactjs.net/ for MVC 4/5, and followed the tutorial on how to setup.
My question is: How do you refer components in other files?
What I have done:
I have a super simple setup with an app called App.jsx
. If I don't refer any pages, I get the output from the tutorial above.
However, if I - in the same folder - make a new file, InvoiceBuilder.jsx
, and I make the following (or any code, this is never reached it seems):
ANSWER
Answered 2018-Apr-01 at 16:06You need to add a export to the component.
Try
QUESTION
I want to use BundleTransformer. I've followed all the steps stated in the docs, but still don't work.
I've installed:
- BundleTransformer.SassAndScss
- BundleTransformer.Autoprefixer
- LisSassHost
- LibSassHost.Native.win-x64
- JavaScriptEngineSwitcher.V8
Here is my config:
...ANSWER
Answered 2017-May-03 at 22:18Well, after trying a little, I just installed LibSassHost.Native.win-x86, and it worked.
Now I have the two packages x64 and x86, everything is working fine.
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install JavaScriptEngineSwitcher
Support
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page