Calling Node.js from C# .NET

问题

Is it possible to call Node.js functions from a C# ASP.NET server? I found the Edge.js library, but as I understood, it allows Node.js to call into C#. I need the directly reverse solution.

回答1:

Microsoft.AspNetCore.NodeServices

• This provides a fast and robust way for .NET code to run JavaScript on the server inside a Node.js environment. You can use this to consume arbitrary functionality from NPM packages at runtime in your ASP.NET Core app.

• Most applications developers don't need to use this directly, but you can do so if you want to implement your own functionality that involves calling Node.js code from .NET at runtime.

Source: https://github.com/aspnet/JavaScriptServices

回答2:

Edge.js has not been updated since mid 2017 and Microsoft.AspNetCore.NodeServices has been obsoleted.

My organization maintains a library, Jering.Javascript.NodeJS, that does everything Microsoft.AspNetCore.NodeServices did and more:

Jering.Javascript.NodeJS enables you to invoke javascript in NodeJS, from C#. With this ability, you can use javascript libraries and scripts from your C# projects.

Example usage

string javascriptModule = @"
module.exports = (callback, x, y) => {  // Module must export a function that takes a callback as its first parameter
    var result = x + y; // Your javascript logic
    callback(null /* If an error occurred, provide an error object or message */, result); // Call the callback when you're done.
}";

// Invoke javascript in Node.js
int result = await StaticNodeJSService.InvokeFromStringAsync<int>(javascriptModule, args: new object[] { 3, 5 });

// result == 8
Assert.Equal(8, result);

Highlights

• Cross-platform support

  • Targets .NET Standard 2.0 and .NET Framework 4.6.1.
  • Tested on Windows, macOS and Linux.

• Performance features

  • Does not start a new Node.js process for each invocation. Instead, sends invocations to long-lived processes via inter-process communication.
  • Optionally, runs invocations concurrently in a cluster of Node.js processes. Handles load balancing for the cluster.
  • Caches compiled javascript where possible.

• Long-running application support

  • Restarts Node.js processes if they terminate unexpectedly.
  • Optionally, restarts Node.js processes on file change.
  • Kills Node.js processes when their parent .Net process dies.

• Flexible API

  • Exposes both a static API and a dependency injection based API.
  • Supports invoking javascript in string form, Stream form, or from a file on disk.

来源：https://stackoverflow.com/questions/42108188/calling-node-js-from-c-sharp-net