Justin Regele wrote:
This brings up another question I've encountered. My understanding was that IPy had problems with 3.5, and so I have been targeting 2.0. But when I try to reference the IronPython and Microsoft.Scripting assemblies, Visual Studio says I need 3.5
I've created many projects in Visual Studio referencing IronPython assemblies and targeting .NET 2.0. Which means I don't know what is wrong, but it *should* work fine... :-)
Michael Foord
On Wed, Jun 17, 2009 at 6:05 PM, Curt Hagenlocher <c...@hagenlocher.org <mailto:c...@hagenlocher.org>> wrote:Good point! On Wed, Jun 17, 2009 at 5:12 PM, Michael Foord <fuzzy...@voidspace.org.uk <mailto:fuzzy...@voidspace.org.uk>> wrote: Curt Hagenlocher wrote: ...except through the hosting API *and through the new C# dynamic functionality in .NET 4.0*. And how do you get to the classes to use them with the new dynamic functionality if it isn't through the hosting API? What you do with them once you get them is your own business of course... Michael On Wed, Jun 17, 2009 at 5:06 PM, Michael Foord <fuzzy...@voidspace.org.uk <mailto:fuzzy...@voidspace.org.uk> <mailto:fuzzy...@voidspace.org.uk <mailto:fuzzy...@voidspace.org.uk>>> wrote: Justin Regele wrote: What is the status of referencing IPy libraries compiled to dlls by other CLR languages? Google turned up that as of 1.1 you had to use the embedding/hosting api's, since the dlls were not compatible with say C# assemblies. There were allusions made to this being changed. You can't access Python classes except through the hosting API. There are no (public) plans for this to change anytime soon. Michael------------------------------------------------------------------------_______________________________________________ Users mailing list Users@lists.ironpython.com <mailto:Users@lists.ironpython.com> <mailto:Users@lists.ironpython.com <mailto:Users@lists.ironpython.com>>http://lists.ironpython.com/listinfo.cgi/users-ironpython.com-- http://www.ironpythoninaction.com/ http://www.voidspace.org.uk/blog _______________________________________________ Users mailing list Users@lists.ironpython.com <mailto:Users@lists.ironpython.com> <mailto:Users@lists.ironpython.com <mailto:Users@lists.ironpython.com>>http://lists.ironpython.com/listinfo.cgi/users-ironpython.com------------------------------------------------------------------------ _______________________________________________ Users mailing list Users@lists.ironpython.com <mailto:Users@lists.ironpython.com> http://lists.ironpython.com/listinfo.cgi/users-ironpython.com-- http://www.ironpythoninaction.com/http://www.voidspace.org.uk/blog _______________________________________________ Users mailing list Users@lists.ironpython.com <mailto:Users@lists.ironpython.com> http://lists.ironpython.com/listinfo.cgi/users-ironpython.com _______________________________________________ Users mailing list Users@lists.ironpython.com <mailto:Users@lists.ironpython.com> http://lists.ironpython.com/listinfo.cgi/users-ironpython.com ------------------------------------------------------------------------ _______________________________________________ Users mailing list Users@lists.ironpython.com http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
-- http://www.ironpythoninaction.com/ http://www.voidspace.org.uk/blog _______________________________________________ Users mailing list Users@lists.ironpython.com http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
