You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am randomly getting this error on a Hello World example-code on a "clean" asp.net project.
The error happens very randomly, with no apparent pattern.
I am using this nuget package: <package id="Noesis.Javascript" version="0.7.1.0" targetFramework="net471" />
This is the code:
App pool settings:
C++ installations:
If the site starts up without the error, it is able to run like that for a long time. Therefore i created a Powershell script to better provoke the error:
The script will continuously do an issreset and then call the page. The result is about 50/50 chance of getting a 200 statuscode back and getting the error back.
The text was updated successfully, but these errors were encountered:
With some further testing i have found that this only happens when i use the x64 version of Noesis.Javascript.dll.
When i switch to x86 and set "Enable 32-bit Applications" to True in the App pool, i do not get the error.
This is not a fix for me, as i need to be able to run x64.
While I don't have a build/nuget package available yet, I have upgraded to a recent version of V8 and build using VS 2017, so it might be worth retesting this. (Building JavaScript.Net is now easy because we get V8 from nuget.)
Uh oh!
There was an error while loading. Please reload this page.
Hi
I am randomly getting this error on a Hello World example-code on a "clean" asp.net project.
The error happens very randomly, with no apparent pattern.
I am using this nuget package:
<package id="Noesis.Javascript" version="0.7.1.0" targetFramework="net471" />
This is the code:
App pool settings:
C++ installations:
If the site starts up without the error, it is able to run like that for a long time. Therefore i created a Powershell script to better provoke the error:
The script will continuously do an issreset and then call the page. The result is about 50/50 chance of getting a 200 statuscode back and getting the error back.
The text was updated successfully, but these errors were encountered: