I'm trying to execute this example code: https://stackoverflow.com/questions/32639893/call-dll-function-from-c-sharp-ironpython
I realize the posted question is a few years old at this point... has something changed in how python, compiled to a DLL via clr.CompileModule, is loaded? I'm getting this error when I run the code in the example at the above link: Unhandled Exception: System.TypeLoadException: Could not load type 'System.Runtime.CompilerServices.Closure' from assembly 'System.Core, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'. at DLRCachedCode.test$1(CodeContext $globalContext, FunctionCode $functionCode) at IronPython.Compiler.OnDiskScriptCode.Run() (full stack: https://gist.github.com/capoferro/5a730088582b8cd36591be510d6ca2fc) My ipy.exe, which did the compilation, is 2.7.8.0 and my embedded IronPython is 2.7.8.1, though I get the same error on 2.7.8.0. Am I missing something obvious or is there a better example to use? My end goal is to be able to take a python module defined in a file (foo.py) with some functions defined, compile it into a dll via CompileModule, then load it directly from the dll via ImportModule to skip the performance hit of interpreting the Python at runtime. Thanks! Josiah
_______________________________________________ Ironpython-users mailing list Ironpython-users@python.org https://mail.python.org/mailman/listinfo/ironpython-users
