-
-
Notifications
You must be signed in to change notification settings - Fork 103
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
Nuget package 11.15.0: Could not load file or assembly 'EdgeJs, Version=9.3.0.0 #130
Comments
I have the same problem, but the exception is at runtime. While building I got just MSB3270 warning: "There was a mismatch between the processor architecture of the project being built "MSIL" and the processor architecture of the reference "EdgeJs, Version=9.3.0.0, Culture=neutral, processorArchitecture=AMD64", "AMD64". After changing project's Platform Target from Any CPU to x64 the exception gone, but now at first I have a message box with: "The procedure entry point Other time I have in VS's output window an error: "internal/modules/cjs/loader.js:857 return process.dlopen(module, path.toNamespacedPath(filename)); Error: The specified procedure could not be found.".
|
Any solution for this issue? @fortnum @smilovich @agracio |
Any update? I got this issue with the latest NuGet package v11.15.0. |
The latest version of EdgeJS 11.15.0 from nuget doesn't work. It just shows error while building:
System.BadImageFormatException: 'Could not load file or assembly 'EdgeJs, Version=9.3.0.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. An attempt was made to load a program with an incorrect format.'
Tested with .Net Framework 4.7.2, 4.8, 5.0
Previous nuget package EdgeJS 9.3.4 works well with the same code from examples.
Also it would be great to be able download EdgeJS release with at latest stable NodeJS 10.xx version for .net 5.0 framework. I tried to do create own build, created node.dll 10.24.0, built EdgeJS C# project, but in a result when I invoke Edge.Func it just throw the following error:
JFY NodeJS 12.xx and 14.xx still have issues with creating node.dll shared library nodejs/node#36516
The text was updated successfully, but these errors were encountered: