ContributionsMost RecentMost LikesSolutionsRe: Trojan found in TE Beta 2 installerGood to know, thanks! Our IT guy is super strict on this kind of thing so just taking precautions. Thanks again :)Trojan found in TE Beta 2 installerOur Virus Software found a Win32/Heur Trojan in the Beta 2 installer for TestExecute 8. Any news on this would be helpful... thank you.Re: .Net 4 and TestComplete 7.52No problem! At least my intern self is good for something!Re: .Net 4 and TestComplete 7.52 http://downloads.automatedqa.com/support/d24b39bf-0029-4a40-be8c-8a4528393170 This has the .dll file that fixes the issue, at least it seems to be working for us. Just overwrite the one in the TestComplete 7\Bin\Extensions folder and you should be good to go. Re: convert recorded test to an exe?We use .bat files to launch a test via TestExecute. Let me know if you need samples.Re: .Net 4 and TestComplete 7.52Sounds like the same scenario. We are seeing if our TestComplete 8 beta machine w/ .NET 4 finds anything beyond the base object..Net 4 and TestComplete 7.52We are having issues with v7.52 after we updated to Visual Studio 2010, which runs on the new .Net 4 framework. Does 7.52 support this or will there be a patch soon to fix the issue? Or do we have to wait for TestComplete 8 to run any of our tests?.Net 4 and TestComplete 7.52This topic has been moved Question from Ashish Garg was moved to a new thread, since it is not related to the topic of the current thread. Re: TC7 slowness when populating text fields We haven't been able to reproduce it on a regular basis. It just seems to happen randomly. As a software company, when a customer approaches us with a technical issue, we drop all production and do everything possible to reproduce and fix the error/issue, not make our customers figure it out. A Better Way to Find Objects I'm working on ways for TestComplete to find objects by looping until they actually exist, since the WaitWinFormsObject and WaitMSAAObject and so forth, don't seem to work very well and I don't want to have timed waits. And infinite waits are useless when Testcomplete can't find the object 25% of the time (this leads to TC looping for hours until I stop the tests). A few ideas I've tried: 1. A looping refresh until the item .exists (This works but posts an error to the log (.exists is possibly the most useless property of any object as it will error because the object does not exist... duh!) ***If anyone knows of a way to suppress this error, please let met know :) *** 2. Looping until the childcount of the parent object is >= number (this essentially will wait for the object tree to be created, if only I could get it to work) I'm lost on further ideas...