I also tried to build on a 64bit Windows 7 machine and was not able to make it work consistently. I was told that the issue was with the version of VS that I used to build PythonNet. I am not knowledgeable in this area however, and could not figure out how to get it to work consistently. I was trying to use it with a distribution of CPython 2.6 (which caused me the most trouble) and CPython 2.7. I stopped working on it as I could only get 2.7 to see the PythonNet module. I'm curious what answers you come up with as I would still love to get this to work on my machine. Thomas On Tue, Oct 30, 2012 at 7:19 AM, John Burkhart <jfburkhart.reg@gmail.com>wrote:
Hello,
I'm new to .NET and just trying to make available a few .NET dll files for an application I would *like* to build in CPython. I'm trying to use pythonnet for the task as I would prefer not to use IronPython. I have Python 2.7 installed on a 64bit Windows 7 PC.
I have managed to get the latest svn version, confirmed required changes according to: http://blog.bidiuk.com/2011/01/python-net-and-vs2010-net-4/
were made. Though, it seemed most were no longer necessary in the latest SVN version.
I also changed the Conditional Compilation symbols to: PYTHON27,UCS2 under the Python.Runtime, Properties->Build tab.
I rebuilt the entire solution, and all compiled with no errors.
However, I get the following when I try to run Python.exe:
PS G:\svn\Python\pythonnet\trunk\pythonnet\src\console\bin\Debug> .\python.exe ImportError: No module named site PS G:\svn\Python\pythonnet\trunk\pythonnet\src\console\bin\Debug>
Does anyone have experience building pythonnet for Python 2.7 and .NET 4?
Thank you in advance, john
_________________________________________________ Python.NET mailing list - PythonDotNet@python.org http://mail.python.org/mailman/listinfo/pythondotnet