AlexanderM
StaffJoined 12 years ago
User Profile
Staff
User Widgets
Contributions
Re: Add "/tr_prefer_wmpaint_hooking" to TestComplete 12 invoked by DCOM
Hi, Since you start TestComplete as a COM server, I suggest that you consider changing the server registration records in the Registry to include the needed option to the server command line. For example, for a 32-bit version of TestComplete 12 on a 64-bit system, the Registry branch would be this: HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{990BBECC-B5F4-478C-9E90-1758B3CE814C}\LocalServer32 You need to change the (Default) key in that branch to include "/tr_prefer_wmpaint_hooking" to the command line: "C:\Program Files (x86)\SmartBear\TestComplete 12\Bin\TestComplete.exe" /tr_prefer_wmpaint_hooking See the attached screenshot. There is a tricky thing though with this approach - TestComplete restores the COM server registration on start to the default state. So once it starts, it removes the parameter. So, in your logic that starts TC via COM, you'll need to implement an extra preparation step that modifies the Registry record before instatiating a new TC instance. Would this work?922Views1like0CommentsRe: I have a seperate 10.3 patch version of tcMSAAAppHook.dll. Do I still need it?
Hi Rob, Understood. I recommend that you go this route: submit a support case through the web site, and specify that you would like to get a TC 12 patch like the one provided in case 00062495. To help the engineers route this request to Devs properly, give a link to this Community thread in the case description - it will give more context and will avoid confusion (there were several patches in that case). Then the case will be escalated to Devs and we'll see what they suggest. Makes sense?2KViews1like2CommentsRe: Registry key is not getting added for auto Login using C# script.
Mojo They are talking about accessing the 64-bit registry from a 32-bit application on a 64-bit system. By default, a 32-bit application will be auto-directed into the Wow6432Node folder even when it does not include that part in the registry key name. That's why you did not see the value added to the path you used, but instead it appeared under Wow6432Node - TestComplete is a 32-bit application. When writing "Just add a 64 to main key", they are talking about this help file of AutoIt: https://www.autoitscript.com/autoit3/docs/functions/RegRead.htm To access the 64-bit registry from a TestComplete script, you can use the Storages.Registry object, like this: function Test_FWC_UTL_Registry_Write_Registry_Key_Value() { var strKey strKey = "SOFTWARE\\Microsoft\\Windows NT\\CurrentVersion\\Winlogon" FWC_UTL_Registry_Write_Registry_Key_Value (HKEY_LOCAL_MACHINE, strKey, "DefaultUsername", "XXXXXXXX") } function FWC_UTL_Registry_Write_Registry_Key_Value(regRoot, strRegistryKey, strRegName, strRegKeyValue) { var key = Storages.Registry(strRegistryKey, regRoot, AQRT_64_BIT); key.SetOption(strRegName, strRegKeyValue); return 1; } Does this help? Also, if you can make things work manually, you will certainly be able to automate the process. That's why I suggested figuring out how to do it manually first, and then trying to turn this into code, as opposed to writing the code right away.4.1KViews3likes2CommentsRe: Registry key is not getting added for auto Login using C# script.
Mojo Makes sense. Looks like RebootAndContinue uses a different registry path: HKEY_USERS\{USER_SID}\Software\Microsoft\Windows\CurrentVersion\RunOnce Did you try using this path (need to figure out the current user ID)? I would actually try to force auto-login manually first, by changing the registry in Regedit. Once this works, I would then automate this in a script.4.1KViews0likes4CommentsRe: Registry key is not getting added for auto Login using C# script.
Mojo I can't recall what I did exactly, but this worked for me in the past (a few years ago). I think I followed the technique the RebootAndContinue function uses: https://support.smartbear.com/viewarticle/80655/ Read that topic, it may give you a clue. Also, why don't you just use RebootAndContinue?4.1KViews0likes6CommentsRe: I have a seperate 10.3 patch version of tcMSAAAppHook.dll. Do I still need it?
Hi Rob, It's not that easy, but I have managed to find that case where the module was provided. It was sent on 11/6/2014 in case 00062495 (just for your records). This was a very special version of the module, and the changes were not included in future releases of TestComplete. To be specific, this module had the "tcUseAltMSAAFree" mode enabled by default without the need to pass that command line parameter to the tested application when starting it. Since you could not change your tests to use this additional parameter, Devs agreed to create that custom patch for you. That is, the patch did not fix anything, it just enabled that mode by default. However, this was a custom change and this mode cannot be used by default for all tested applications. Now, when using TestComplete 12, can you pass this additional command line parameter (/tcUseAltMSAAFree) to the tested application when starting it from your tests?2KViews1like4Comments