7sharp9/edge-fs

F# compiler for edge.js

edge-fs's Issues

Could not load file or assembly 'FSharp.Core, Version=4.0.0.0, ...'

The following exception is thrown on Windows 8.1 with Visual Studio 2013 installed:

...\node_modules\edge\lib\edge.js:143
    return edge.initializeClrFunc(options);
                ^
System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.IO.FileNotFoundException: Could not load file or assembly 'FSharp.Core, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot
find the file specified.
   at EdgeCompiler.CompileFunc(IDictionary`2 parameters)
   --- End of inner exception stack trace ---
   at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)
   at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments)
   at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
   at ClrFunc.Initialize(Handle<v8::Value>* , Arguments* args)

Is it possible to supply an assembly binding redirection to edge-fs with an app.config file?

Investigate if sigdata and optdata from Fsharp.Core.dll are really needed

Publish on NPM

In your blog post you mentioned plans to publish edge-fs to npm once things settled down. I would recommend publishing what you have so far (maybe with a disclaimer). This makes it much easier for people to discover, use, and contribute to your module in the node ecosystem.

Project enhancements proposal to support current version of Edge.Js

Hi,
I maintain an up-to-date version of Edge.Js https://github.com/agracio/edge-js that supports modern versions of Node.Js, .Net Core, incorporates unmerged PRs from original Edge.Js repo and receives constant updates via new PRs and code improvements.

Currently I am looking at migrating various language integrations like edge-fs and others to support .NET core. Since I do not own the original NPM repositories or have maintainer access to them had to resort to forking the projects then renaming newer packages to something similar for example edge-py is published as edge-iron-py which also changes language specification in Edge.Js functions from py to iron-py.
Following that example edge-fs would be published as edge-fs-core for .NET Core project while edge-fs would remain as a package for .NET 4.5.

Was wondering if you would be open to the idea of transferring the project to me so I could maintain both .NET Framework and Core versions in one package while adding any necessary improvements.

One way of doing it would be adding me (agracio) as maintainer for edge-fs NPM package and I could publish to it using my forks.
If it is done this way then GitHub link would point to my page instead of yours but it would include full credit at the top of the project description, I do not want to take any credit for peoples hard work since I just maintain the existing repo.
Currently GitHub link for NPM edge-fs package points to https://github.com/tjanczuk/edge.
This has a benefit of offloading any potential issues coming back to this repo as I am sure you have long moved on from this project.
Alternatively if you want to resurrect this repo here you could add me as maintainer both on GitHub as well as NPM and publishing would continue from here.

Let me know your thoughts.