Contributions
Re: Testing WPF Program Causes Crash
I've got the HTML log file. I sent it in but I haven't heard back yet. We sort of got it working if we set it in real time, turn off Map object names automatically under Name Mapping and then if we wait a few seconds before each action they will record and run, albeit it slowly. Note-I can't attach an HTML file here so I zipped it.1KViews0likes0CommentsRe: Testing WPF Program Causes Crash
I'm relatively certain .NET 4 is not the issue, but I installed AQtime and tried your steps. When I go to hit start it shows me the error I've attached. During the AQtime install I noticed it complained about no Microsoft Debugger so I went and installed that and it didn't seem to fix my problem. What do I need to do to fix that?1.8KViews0likes0CommentsRe: Testing WPF Program Causes Crash
I'm not entirely sure how to know if I have or had .NET Framework 4, but I'm running VS 2008 and it seems to be V 3.5. I went through all of those questions and the answers are: 1. I set the invoke timeout all the way up to 1 minute. Nothing. 2. I'm running 7.52 3. x64 4. I've tried it everyway. Running from the start menu, double clicking the exe, launching from TestComplete. Nothing. 5. Not run from any sort of network location. 6. Not sure, will check. 7. No 8. Pretty much the same as her.1.8KViews0likes0CommentsRe: Testing WPF Program Causes Crash
I set the Method Invoke timeout all the way up to 60000 and it still won't record any sort of movement or action inside of the application screen. There's no crash so I can't get a dump, no objects or movements are being recognized. What are my options?1.8KViews0likes0CommentsRe: Testing WPF Program Causes Crash
I haven't tried increasing the invoke, timeout I'll do that now. I've tried starting and restarting the application, TestComplete 7 in all manner of fashions and it's no help. The issue always occurs (either crash [which hasn't happened recently] or no objects are discovered or actions recorded). The crashes only happened when I moved my mouse in to the applications window, as far as not finding objects well yes, I suppose that happens right after start up. Edit - I tried to find the Timeout Option following your directions and it's not clear. I can't find an 'open applications' options group. Are you referring to Visual Studio options or TestComplete IDE options?2.1KViews0likes0CommentsRe: Testing WPF Program Causes Crash
It doesn't time out or crash. I can move around freely while recording a test, the program will respond to button clicks and move. But if I was recording the test, nothing shows up in the steps except for the program launch. On the record dialog that will show object types and names when the mouse moves over them or selects, nothing changes. This is what the object name is for the whole screen: ["Window"]("HwndWrapper[ConsoleUI.exe;;31f7e182-0c0d-4cde-8177-29ca597ba177]", "App", 1)2.1KViews0likes0CommentsRe: Testing WPF Program Causes Crash
Thanks for the detailed help David. Unfortunately when I tried to run it again, my Application wouldn't hang our crash this time. Some times it'd be a little slow to respond, but only a matter of seconds. It now seems my problem is with TestComplete finding items within the window. Once my mouse enters the applications window, it won't discover any of of the clicks, objects or mouse movements inside. What can you tell me about how TestComplete discovers objects, or why there would be problems from within a WPF application? Thanks.2.1KViews0likes0Comments