Contributions
Re: All Objects properties are changed after upgrade application version to .net framework 4.6.1 & TC12
I'm not sure where I can find the CC-6531 patch, but we downloaded the latest installer available for TestComplete 11.31 and tested it with .Net 4.6.1 and we see that it works fine. Following are the combinations we tried: TC11.20 +.Net 4.6.1 = Works fine TC11.31 +.Net 4.61 =Works fine TC12 + .Net 4.6.1 =Cant see the CLR properties such as Caption, ObjectIdentifier, etc TC12 + .Net 4.5.1 = Cant see the CLR properties such as Caption, ObjectIdentifier, etc TC12 + .Net 4.0 =Cant see the CLR properties such as Caption, ObjectIdentifier, etc We would appreciate if you can provide some help as early as possible as we have a huge inventory of tests that needs this and are blocked from upgrading to TC12.1.7KViews0likes0CommentsRe: CPUUsage Property specific to 64-bit/32-bit?
Hi Helen, Thanks for the reply. I have opened a request as mentioned,request ID:M0100908. I tried the function using stop instead of split but unfortunately it still didn't work. var elapsetime = StopWatchObj.Stop(); It still returns double the time, eg. 3.2 hrs in place of 1.6 hrs. Hence, I have added the same in the request too. Thanks, Eyme735Views0likes0CommentsCPUUsage Property specific to 64-bit/32-bit?
Hi, I have a doubt regarding the CPUUsage property. I am using it for calculating the CPU Usage of a process, ie, Sys.Process(...).CPUUsage; I see that the value crosses 100%, eg. 106%,135%,etc. Could this be due to a 64-bit operating system and if so is there a necessity to divide it by 2? This doubt came up as I see that the elapsetime obtained using stopwatch function also returns exactly double the time due to which we are dividing it by two: var StopWatchObj = HISUtils.StopWatch; StopWatchObj.Start(); StopWatchObj.Stop(); ..... .... .... var elapsetime = StopWatchObj.Split(); Please guide me if I am wrong. Hope to see a response soon. Thanks, Eyme18KViews0likes4Comments