Ranorex occasionally freezes with TFS project

[odklizec]

OK, I can reproduce this behavior also with newly created project. The freeze after checkin (either finished or canceled) is not so long with new project, but it's definitely there. I guess it has something to do with project size/number of files in project. I also think it has something to do with icon overlaying! I've sent you the sample project, my actual RanorexStudioProperties.xml and some additional comments to support email. Hope this helps?

[Support Team]

Hi,

We are currently via email in contact with odklizec and we will update the forum thread when we found what is causing the issue.

Regards,
Markus

[odklizec]

OK folks, here is an update to this issue.

We exchanged number of emails and the main reason of the problem appears to be MSSCCI provider. MSSCCI enables integration and use of TFS in apps without native TFS plugin (basically any non-MS app). It seems this MSSCCI provider provides somewhat limited control over the TFS integration, which could make the TFS operations significantly slower. Part of the problem could be also slower access to TFS server, typically if the server is not in the same building/country

There is unfortunately nothing Ranorex can do about MSSCCI. We discussed several options, but none of them appeared to be comfortable enough to be done at a daily basis. Luckily, I was able to find a quite reasonable workaround.

At first, it's required to convert the workspace (in which is placed the Ranorex solution) to a "local" mode...
https://msdn.microsoft.com/en-us/library/bb892960.aspx
This removes the read-only lock from all solution files. This is required for second step, in which we kill Ranorex TFS integration

The second step is kind of hack. You will have to edit *.csproj file and remove this line from it:

Code: Select all

<RxSccProvider>Microsoft Team Foundation Server MSSCCI Provider</RxSccProvider>

Basically, this will remove your solution from Ranorex TFS integration, which means you will no longer be able to perform check-in (or other TFS- related operations) from Ranorex Studio. You will just have to use TeamExplorer or something else outside the Ranorex Studio.

I think this is only a minor downside considering the major performance boost you will get after removing solution from Ranorex TFS integration. And you can believe me, it's now damn fast! Absolutely no waiting after loading solution or adding/renaming modules. And because the solution is in "local" mode, we can freely edit it without the need to use "Checkout for edit" to remove read-only lock. Hope this helps?

PS: I was pointed out that the same effect (as removing line from csproj file) could be achieved be using "Remove Source Control Binding" context menu action. I somehow missed that menu item

TFS_remove.png

[krstcs]

I'm starting to think that Ranorex should just remove ALL versioning system integration, it's too much of a problem on their side to try to integrate and slows things down on ours.

But, I use GitHub where there's no integration anyway, so...

[mtaylor]

I'm having the same issues with my project freezing and I'm getting these Debug lines in my Logfile...the same thing for me:

2015-03-20 09:45:01.4914|DEBUG|Ranorex.Core.DualModeNetFactory|Will create dual mode TCP client.
2015-03-20 09:46:01.4984|DEBUG|Ranorex.Core.DualModeNetFactory|Will create dual mode TCP client.
2015-03-20 09:47:01.5243|DEBUG|Ranorex.Core.DualModeNetFactory|Will create dual mode TCP client.
2015-03-20 09:48:01.5331|DEBUG|Ranorex.Core.DualModeNetFactory|Will create dual mode TCP client.
2015-03-20 09:49:01.5419|DEBUG|Ranorex.Core.DualModeNetFactory|Will create dual mode TCP client.
2015-03-20 09:50:01.5607|DEBUG|Ranorex.Core.DualModeNetFactory|Will create dual mode TCP client.
2015-03-20 09:51:01.5699|DEBUG|Ranorex.Core.DualModeNetFactory|Will create dual mode TCP client.

I have to manually intervene and abort the test in order for it to proceed.

I have attached my logs below...My test froze for over 8 hours.

[odklizec]

I would really suggest you to stop using TFS integration and start using Team Explorer instead. This move will save you a lot of time and pulled hair Sadly, as long as the Ranorex TFS integration will relly on MSSCCI provider, the TFS experience will never be smooth, especially with larger projects. And because MSSCCI provider is currently the only way for 3rd parties (companies outside MS) to integrate TFS into their apps, Ranorex cannot do anything about it.