For my Visual Studio integration work, I did not realize initially that I would run into issues related to the fact that Visual Studio is 32 bit app while j.dll may be 64 bit.... So what I am working right now is have ALL the j.dll integration via TCP/IP, the way you suggest it. Actually Python guys do the same, so I just need to port some Python code around... By they way, I never used Python before, I find it's extremely easy to come up to speeds with it. About 2 hours of reading and I am pretty much at home with most of Python....
On Tue, Apr 16, 2013 at 6:45 AM, Steven Taylor <[email protected]> wrote: > Hi Greg, > > MS is rumoured to be working on a C# native compiler (they hired in this > area towards the end of last year). The current J .dll approach is > probably the best approach. MS never promoted this much, but there are a > few different ways of exposing CLR methods as a .dll for the current CLR > versions (ie. native to managed, not over COM). I picked up on a few > robustness issues on this approach on various threads. So it may be > resource intensive to get it going well. The approach is a little like how > PostSharp does it (code injection). However, C#->native would be welcome + > make this step unnecessary. > > Probably interprocess comms based on TCP/IP/Http are your best bet. ie. > the LINUX single responsibility, less monolithic type stuff. > > best, > -Steven > > > On 15 April 2013 19:53, Greg Borota <[email protected]> wrote: > > > http://pythonnet.sourceforge.net/ > > http://pythonnet.sourceforge.net/readme.html > > > > These guys call .NET from the C based python interpreter. Without > > implementing Python on the .NET platform like IronPython does it. > > > > So maybe that same approach would work with J too. Just throwing this out > > there, maybe somebody would want to follow-on and share some more > details. > > ---------------------------------------------------------------------- > > For information about J forums see http://www.jsoftware.com/forums.htm > > > ---------------------------------------------------------------------- > For information about J forums see http://www.jsoftware.com/forums.htm > ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
