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
{{ message }}
This repository was archived by the owner on Apr 8, 2020. It is now read-only.
Repository navigation
This repository was archived by the owner on Apr 8, 2020. It is now read-only.
Is it possible to pass arbitrary .NET types including delegates? #701
With Edge.js it's possible to pass arbitrary .NET types, including delegates, and then have the JavaScript code invoke the delegates. Then, from the .NET delegates, you return back to JavaScript, and so on.
Would it be possible to do something similar with this tool?
That's not something currently supported natively in NodeServices. At some point, we might be able to enable Edge.js as an alternative transport layer that you can use with NodeServices (similar to how you can currently choose between HTTP and Socket transports), but that wasn't possible last time I checked because Edge.js didn't support hosting Node within a .NET Core process.
So right now, all types you pass have to be serializable by Json.NET.
Activity
SteveSandersonMS commentedon Feb 22, 2017
That's not something currently supported natively in
NodeServices. At some point, we might be able to enable Edge.js as an alternative transport layer that you can use withNodeServices(similar to how you can currently choose between HTTP and Socket transports), but that wasn't possible last time I checked because Edge.js didn't support hosting Node within a .NET Core process.So right now, all types you pass have to be serializable by Json.NET.
moodmosaic commentedon Mar 20, 2018
Is there some fundamental difference between desktop and CoreCLR that prevents hosting Node within a .NET Core process?
SteveSandersonMS commentedon Mar 22, 2018
Nothing fundamental that I know of. AFAIK, it's just not implemented in Edge.js.