Forum Discussion

JonoW's avatar
JonoW
Occasional Contributor
14 years ago

tcClrHook.dll version X vs version Y/Z

Hello,



I'll start with some History:

We originally started out using the trial version of TC7. We discovered the name mapping issue that was fixed with a patched version of tcclrhook.dll (dated 25 Jan 2010 - v7.52.678.7).

On that basis we bought a couple of licences for TC8 Enterprise. This has the dll version (dated 22 July 2010 - v8.0.290.7). However when we try to access certain objects through the Object Browser our application crashes - we have two very similar (same sort of code base) applications on test, one of which always crashes with a stackoverflowexception error, the other just crashes with even less information - just a .NET 2.0 runtime error.



We have been given license for the enterprise version of TC7 and its version of the dll does not crash our application, but we still have the name mapping issue - objects showing up as:

Sys.Process("Application.UI").Window("WindowsForms10.Window.8.app.0.33c0d9d", "CompanyName", 1).Window("WindowsForms10.Window.8.app.0.33c0d9d", "", 2).Window("WindowsForms10.Window.8.app.0.33c0d9d", "", 3).Window("WindowsForms10.Window.8.app.0.33c0d9d", "", 7).Window("WindowsForms10.Window.8.app.0.33c0d9d", "Communication", 1)



For an Infragistics ultraButton control, for example.



If we patch to the later version of the dll, the one for TC7.52 (dated 16th April 2010 - v7.52.694.7) then our name mapping works as expected, but the application still crashes.



There's a sort of workaround, by which we let TC handle the name mapping automatically when we record keyword tests. We'll then have to change the mappings manually.



I was just wondering if there's anyone else out there who's experienced a similar issue, or if AQA/SmartBear are aware of this and working on a solution so that our application won't crash.



Thanks,

<J>

1 Reply

Sort By
  • AlexeyKolosov's avatar
    AlexeyKolosov
    Staff
    14 years ago

    Hi Jono,


    We are not aware of such problem with TestComplete 8. To help us investigate it, please follow the steps below to help us investigate the problem:


    1. Download a free trial version of AQtime 7, which is our profiling tool, from our web site. The trial can be requested on the following page of our web site:

    http://www.automatedqa.com/downloads/aqtime/


    2. Install the tool.


    3. Start AQtime with the -NotOpenApp command line argument. For example, you can use the following command line:

    "c:\Program Files\Automated QA\AQtime 7\Bin\AQtime.exe" -NotOpenApp


    4. Select the 'File | New Project From Module...' main menu item.


    5. In the Open File dialog, select the the tested application's executable file and click Open.


    6. Take a look at the AQtime toolbar - there is a combo box. Open it and select the "Tracing | Exception Trace Profiler" item.


    7. Select the "Options | Options..." main menu command - the Options dialog will appear.


    8. Set the "Profiling Time | Event View | General | Exceptions | Depth shown" setting to 100 and click OK.


    9. Start the tested application.


    10. Click the Run | Attach to Process... main menu item in AQtime.


    11. Select the tested application's process from the list by double-clicking it and click Run in the dialog that appears after that.


    12. Reproduce the problem.


    13. After the problem occurs, right-click somewhere within the Event View panel (it is opened by default at the bottom of AQtime's window) and select the 'Save All...' item.


    14. Save the panel's contents to an HTML file and send me the file via our Contact Support form:

    http://www.automatedqa.com/support/message/


    Thanks in advance.