Closed kjami closed 1 month ago
@kjami Im Having the same issue, have you found any solution to this issue? @tjanczuk Have you had this issue ?
thanks guys!
Hi Cristian,
No, I didn't find any solution for this. I avoided using edge and developed local meteor package that does the same thing as .Net library that I was supposed to use. In my case, I only need few methods of the library and it took me less than a week to replicate all of them. It is optimum for our company because we avoid other issues like installing mono on linux to deploy the application and the main advantage is even if there are bugs in the new code at a later date, we can solve them unlike issues like the current one, which anyone in our company doesn't have any idea about.
Nevertheless, I like Edge when used with Node.
Regards, Kishor Jami.
On Thu, Mar 5, 2015 at 1:56 AM, Cristian Leyes notifications@github.com wrote:
@kjami https://github.com/kjami Im Having the same issue, have you found any solution to this issue?
— Reply to this email directly or view it on GitHub https://github.com/tjanczuk/edge/issues/231#issuecomment-77209723.
Kishor Jami
Hi,
Thanks for the good work. I have been using edge module to call c# methods in a dll. I have successfully been able to call c# methods using edge in node js application. Since our company is using MeteorJS, and it only supports Npm modules inside Meteor packages, I have created a local meteor package and used Meteor's Npm.depends and Npm.require to get the edge npm module. But when I run the project I get the following stack trace and the meteor application is restarting. I have no idea what the stack trace is all about. Can you please look into this stack trace and let me know if I can do anything to avoid this issue.
I have tested other npm modules just to make sure that it is not the problem of accessing npm modules itself.
Stack Trace:
Please let me know if you want more information. Thanks.