Ranorex Technology Limitation popup message from Spy

[Ciege]

When I spy on a certain part of a dialog within my AUT I receive the attached error message (see screenshot).

Ranorex Tech Limitation.jpg (11.91 KiB) Viewed 1476 times

It has only appeared (that I've noticed) when I try to spy on the Element 'CostItemReportControl' or the Element's children within Panel2 of my Report Dialog in my AUT. I've attached a snapshot of the dialog.

Code: Select all

/form[@controlname='ReportLaunchDialog']/container/container[@controlname='panel2']/element[@controlname='CostItemReportControl']

This (of course) did not happen with 2.x of Ranorex but is happening now with 3.0.1.

[Ciege]

Just an update...
If I have Spy version 2.3.8 running at the same time as Spy version 3.0.1 and Spy on that form I get no technology limitation popup message. However, if I close both versions of Spy then start just the 3.x version the popup message returns.

[Support Team]

I checked that "CostItemReportControl" and it seems to come from a dynamically loaded assembly, i.e. an assembly loaded from a byte array. That's why Ranorex cannot load the assembly defining that control (since there is none or none that Ranorex could load). So the warning message is correct, however, it looks a little weird since no path is displayed.

And it is pretty useless, too, because you cannot do anything against it, that's why we decided to no show that message if the path for the assembly is empty. Consequently, you won't get that warning again with the next version

Regards,
Alex
Ranorex Team

[Ciege]

It appears that I can still do all the automation I want to do within that dialog/form regardless of the warning message. Should I be worried at all about the automatability of that form?

[Support Team]

Should I be worried at all about the automatability of that form?

It seems like it's only that one control coming from a dynamic assembly. As long as it's only that single control, I would not worry about it. And you cannot do much about it unless you change how plugin assemblies are loaded in your application, I guess...

Regards,
Alex
Ranorex Team