IronPython Support on coming version 2.0

Class library usage, coding and language questions.
Posts: 1
Joined: Thu Jan 29, 2009 12:00 am

IronPython Support on coming version 2.0

Post by grey » Fri Jan 30, 2009 6:43 pm

Hi, I received a comment from support team about a new support on v2.0 for Python and this will be IronPython, my concern now is about where I could get information about it, because I used the trial of v2.0 but it generate code in C# or C++, now in 1.5 for Python integration we use two Dlls but I'm not sure how is gonna be this change to IronPython....

Will this be a limitation about just work with .Net applications? or Will you keep the support for MFC as well ?


User avatar
Support Team
Site Admin
Site Admin
Posts: 12173
Joined: Fri Jul 07, 2006 4:30 pm
Location: Houston, Texas, USA

Post by Support Team » Wed Feb 04, 2009 9:36 am

The new Ranorex 2.0 core is based on the .NET Framework, so you need at least .NET 2.0 installed to get Ranorex 2.0 running. You can still automate MFC and pure Win32 applications, however, your automation code/program must be able to reference .NET assemblies (DLLs).

That's why we suggest IronPython for all the users that want to write their automation code in the Python language. IronPython is an implementation of the Python language for .NET, meaning: You write Python code and this code can be interpreted by the IronPython runtime, like with the old CPython (that is commonly known as "Python"). Unlike CPython, the IronPython runtime executes your code using the .NET Framework and you can compile your Python code to .NET assemblies (DLLs), too.

If you don't want to switch to IronPython and want to continue using CPython (like with Ranorex 1.5) instead, you can use "Python for .NET" to access the new Ranorex 2.0 core (see this blog for more information on "Python for .NET").

Whatever option you choose (IronPython or Python for .NET), you will always have to install the Ranorex 2.0 package that includes all the DLLs needed.

Ranorex Support Team