The control was recognized as a WinForms .NET 1.1 control

Ask general questions here.
Posts: 4
Joined: Mon Feb 27, 2017 8:55 am

The control was recognized as a WinForms .NET 1.1 control

Post by Baitosenshi » Tue Mar 21, 2017 9:24 am

Hi all,

We encountered this warning during the Ranorex script development.

"The control was recognized as a WinForms .NET 1.1 control. If this application targets the .NET Framework v1.1, then please ignore this message. Otherwise, the object recognition is not correct, most probably due to an installation issue. Please, uninstall and reinstall Ranorex and try again."

It's weird since we never encountered this issue before.

The situation is:
Before we didn't encounter this issue since we only open one win-application for automation testing.
But recently, we add a new function, before launch the target win-application will need to auto get its latest version before. In that case, in the automation process, we open another win-application for installing the new version of the target application and then launch the target application. But after the target application launched, this warning occurs. And then the Ranorex failed to recognize some components.

So any workaround for this situation?.
- I'm sure the 2 applications and Ranorex have same privilege during the test.
- The version of Ranorex is 6.2


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

Re: The control was recognized as a WinForms .NET 1.1 control

Post by Support Team » Wed Mar 22, 2017 9:31 pm

Please have your development team debug the application while running a test against it. There was an identical issue in support that we spent a lot of time troubleshooting, and the issue ended up being inside a method that was in the application under test (AUT) and not related to Ranorex software.

Please also be advised that you should investigate all the reasons for this error that are listed in the troubleshooting guide via the link in the warning just to make sure, but it sounds like you have already because of the information included in your post.

If after debugging the software your development team does not see any exceptions or issues, then please send an email to [email protected] (USA time-zones) or [email protected] (Europe and world) and we will be happy to take further steps in troubleshooting this issue with you.

M. Kendall McIntosh
Support Engineer