Hello,
currently we are testing on both variants, rx 2.3.9 and 3.0.1 and we have some cases where Ranorex 3.0.1 is not able to cast an element to control. May its a special problem of an UltraExplorerBar InfracisticsControl, we actually don't know...
We made two images:
[UltraExplorerBar_Rx_2.3.9.JPG]
The first one is taken from our ms studio and debugged with ranorex 2.3.9. As you can see value and type are named as "Ranorex.Core.Element" and the cast was successfull (control is not null and reachable through ranorex).
[UltraExplorerBar_Rx_3.0.1.JPG]
The second one is debugged while ranorex 3.0.1 was running. The type of our element is still Ranorex.Core.Element but the value is "Unknown:UltraExplorerBar". The cast in this case is not successfull, control is null.
In Ranorex 3.0.1 we've already changed the "Filtering compatibility level" in Spy from V3X to V2X with no effect.
Any ideas?
Best Regards! JayDee
Rx 3.0.1: Element will not be recognized as Control
Rx 3.0.1: Element will not be recognized as Control
You do not have the required permissions to view the files attached to this post.
- Support Team
- Site Admin
- Posts: 12145
- Joined: Fri Jul 07, 2006 4:30 pm
- Location: Houston, Texas, USA
- Contact:
Re: Rx 3.0.1: Element will not be recognized as Control
Do you have a Ranorex 2.X and Ranorex 3.X installed on that machine?
Do you have the .NET Framework 4.0 installed on the machine?
If so, this is a known problem that will be fixed with Ranorex 3.0.2. Please, try to uninstall Ranorex 2.X from the machine and try again, thanks!
(It should be safe to install Ranorex 2.X afterwards again without problems. The problem only exists if you install Ranorex 3.X after 2.X, have .NET 4.0 installed and try to automate Windows Forms 2.0 controls.)
Regards,
Alex
Ranorex Team
Do you have the .NET Framework 4.0 installed on the machine?
If so, this is a known problem that will be fixed with Ranorex 3.0.2. Please, try to uninstall Ranorex 2.X from the machine and try again, thanks!
(It should be safe to install Ranorex 2.X afterwards again without problems. The problem only exists if you install Ranorex 3.X after 2.X, have .NET 4.0 installed and try to automate Windows Forms 2.0 controls.)
Regards,
Alex
Ranorex Team