Question 1

How do I debug C# code in Edge.js with Visual Studio?

Accepted Answer

On Windows, set the EDGE_CS_DEBUG environment variable to 1 and attach a managed debugger to node.exe; you can use System.Diagnostics.Debugger.Break() in C# code or set breakpoints in embedded sources, but this doesn't work well on non-Windows platforms.

Question 2

Edge.js vs using child processes for Node.js and .NET communication

Accepted Answer

Edge.js offers lower latency and overhead by running in-process, but it's more complex to set up and debug. Child processes are simpler and more isolated but involve serialization and IPC costs.

Question 3

Can I use .NET Core with Edge.js on Linux?

Accepted Answer

Yes, Edge.js supports .NET Core on Linux, but you must set the EDGE_USE_CORECLR environment variable and ensure proper runtime installation, as detailed in the Linux setup and Docker sections.

Question 4

How to handle exceptions between Node.js and .NET in Edge.js?

Accepted Answer

Exceptions are marshalled automatically: .NET exceptions appear as error objects in Node.js callbacks, and JavaScript errors thrown in Node.js code cause CLR exceptions, with stack traces preserved across boundaries.

Question 5

What's the performance impact of using Edge.js?

Accepted Answer

Edge.js minimizes overhead with in-process execution, but there's still marshalling cost; the README includes latency benchmarks showing it's efficient for interop but may add complexity compared to pure solutions.

Question 6

Is Edge.js still actively maintained?

Accepted Answer

The original repository is archived, with active development moved to agracio/edge-js; check the new repo for updates, but this fragmentation might affect long-term support and issue resolution.

Edge.js

What is Edge.js?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions