khalidabuhakmeh, 14 days ago Only a few years ago, there was a considerable effort in #dotnet to make interoperability with #nodejs a thing... now it seems like all those projects are gone or woefully behind. Bummer :(
Only a few years ago, there was a considerable effort in #dotnet to make interoperability with #nodejs a thing... now it seems like all those projects are gone or woefully behind. Bummer :(
shortdev, 13 days ago @khalidabuhakmeh What about https://github.com/microsoft/node-api-dotnet?
@khalidabuhakmeh What about https://github.com/microsoft/node-api-dotnet?
khalidabuhakmeh, 13 days ago @shortdev it’s still a WIP and not a NuGet package. I found it, but it’s not accessible yet without downloading and building it yourself.
@shortdev it’s still a WIP and not a NuGet package. I found it, but it’s not accessible yet without downloading and building it yourself.
filipw, 14 days ago @khalidabuhakmeh the real question is, was there ever a proper use case?
@khalidabuhakmeh the real question is, was there ever a proper use case?
khalidabuhakmeh, 14 days ago @filipw Considering the collapse of OSS solutions in the .NET space, leaning on ecosystems like Node would be beneficial in supplementing the void. I had a use case today to introduce a static search index to #aspnetcore apps, but the tooling is a node module. Alas... not meant to be.
@filipw Considering the collapse of OSS solutions in the .NET space, leaning on ecosystems like Node would be beneficial in supplementing the void.
I had a use case today to introduce a static search index to #aspnetcore apps, but the tooling is a node module.
Alas... not meant to be.
Add comment