SilverlightApp_0 to SilverlightApp

[Kristine]

I have an existing project created using the Q1 version. All project elements were added to a Silverlight instance named "SilverlightApp".
I then updated my version of the tool using the 2010.2.727 Q2 release. After this install, all new project elements were added to a new Silverlight instance named "SilverlightApp_0". I am still testing the same Silverlight application, but then I thought  this change was inevitable because of the new tool version so I Iet it go as it is, it works anyway.
However, after several days of using the new release, something weird happened. The tool switched the SilverlightApp instances: SilverlightApp -> SilverlightApp_0; SilverlightApp_0 -> SilverlightApp. I have a lot of existing coded steps using the original instance, also have created a lot of coded steps using the new instance, resulting to hundreds (or thousand) compile error messages. What I did was edit the "Friendly Name" property of both elements in the Property box, and then saved. This worked. However, whenever I reopen the same project, they switch back again. Is there a way how to make this automatic renaming not happen?

[Cody]

Hi QA,

There are multiple issues going on here actually. The correct way to fix this would be to change the Find Expression of the old SilverlightApp node to match that of the new SilverlightApp_0 node.

Unfortuantely I just discovered you can't do that due to a bug in the tool. We've set a high priority to fix this bug and will send you an internal build containing the fix. Should have it in just a couple of days.

FYI, the reason the nodes sometimes switch between SilverlightApp -> SilverlightApp is that that node name (the friendly name) is dynamically generated as we're loading the tests. Thus whatever order we happen to find the files in is how the nodes will be generated and named. True you can't set/save the node name due to a different bug. I'm trying to get an answer if the bug is that it can't be saved or if that friendly name field should be read-only.

Are you having any difficulty getting your original tests recorded with Q1 tool to run with the Q2 tool (other than the name swap causing compiler errors)?

Kind regards,
Cody
the Telerik team

[Kristine]

I had to update some tests because an element or two can no longer be found. But they're working ok now.
In my opinion the tool is better now that it's able to recognize the extended components of the Telerik controls.

[Cody]

Hi QA,

I have good news! We have posted a new internal build that addresses this problem. Here are the steps to fix this once and for all in your test project using this new build:

1. Right click on the new SilverlightApp_0 node in Element Explorer that was created when you upgraded to the Q2 release and started recording
2. Select Edit Element
3. Make note (write down or screenshot, etc.) of the find expression. It will probably look like the one in the attached screenshot.
4. Cancel out of this one.
5. Right click on the original SilverlghtApp node that is for your Q1 tests.
6. Select Edit Element
7. Make this find expression match exactly the one for the SilverlightApp_0 node.
8. Click OK to save it.
9. You will notice that all of a sudden all the elements will merge into one SilverlightApp node.
10. Now you'll need to do a global find and replace in your code behind files. Change SilverlightApp_0 to SilverlightApp.

That's it. You will no longer have to deal with multiple SilverlightApp nodes in your project or the compile errors you were getting.

Regards,
Cody
the Telerik team

[Kristine]

Hi Cody,

I installed the latest internal build 2010.2.806.0, and then followed the steps provided. I encountered this error:

Microsoft .NET Framework
Unhandled exception has occurred in a component in your application. If you click Continue, the application will ignore this error and attempt to continue.
Object reference not set to an instance of an object.

Have you encountered this?

Regards,
Qa

[Konstantin Petkov]

Hi QA,

Can you please submit a private support ticket and zip/attach the problematic project there? We will investigate the error and get back to you with resolution, thank you!

Regards,
Konstantin Petkov
the Telerik team