I wrote a first script (RunScript.py) calling a DLL that runs in IPython to be Rhino compliant. To test it I used ipy.exe and it worked well (it enters and read the DLL). Same when running the script with Rhino 64-bit.
When adapting and testing my script to another DLL, it didn’t work with ipy.exe nor with Rhino 64-bit, but it worked with ipy64.exe (indeed the library was compiled in 64.
Does it means that the command RunPythonScript launched in Rhino 64-bit is not using ipy64.exe but ipy.exe?
Rhino does not use either of the .exe’s, but uses the implemenation of IronPython that in turn those programs use. If you are more specific regarding the error, maybe we could assist further.
Hi again @Nathan_Clero. The reasons why it could not add references can be multiple.
One, which is the simplest one, would be that the path to the assembly is unknown. Try using AddReferenceToFileAndPath() or another of the alternatives to see if the problem persists.
Also, ipy.exe is not a product of Robert McNeel & Associates.
IronPython runs embedded in the Rhino process so if you are running Rhino 32 bit, then IronPython will be executing as 32 bit. If you are running the 64 bit version of Rhino, then IronPython will be executing as 64 bit.
)