Hi Rob,
We'll be happy to check with Devs! Can you please share the case number where this patch was created and delivered to you?
I have no idea what the case number would be. I see the properties on the dll say its file version is 10.30.1370.11, I would assume that could be tracked down. Product version is exactly the same.
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?
Hello Alexander,
No we are still unable to pass this additional parameter to the tested application.
That being said, how do I go about getting another patch created for 12, and I assume for each new release we take?
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?
