While automating a large 3rd party application, I was running into a problem where TestComplete's Debug Info Agent would not be able to find debugging information for some MFC controls that the application uses. I placed the .pdb files for those MFC controls into the application directory and was still running into this problem for some time afterward. I've managed to trace the source of the problem to the fact that this application changes its working directory when files are opened inside of it. So basically if I open a file in the application by using the standard keyboard shortcut before I attempt to interact with the app via the mouse, the Debug Info Agent ends up looking in the recently changed working directory for the .pdb files instead of the directory where the application sits on disk and where the .pdb files exist.
My colleague is testing the same version of this application with the same version of TestComplete, and he is not seeing this same issue in his environment. His application directory does not include these MFC .pdb files, and it's always worked for him out of the box so to speak. This leads me to believe that the Debug Info Agent must be searching in more than just the application's working directory when it's looking for debug information. Does anybody know what directories the Debug Info Agent searches when it is looking for the debug information of an application during test playback? Knowing this information would allow me to put the .pdb files in another location that won't change with the state of the application being tested and eliminate a test step ordering issue that I frequently forget about while scripting the tests. Any help with this would be greatly appreciated!!!
Thank you all for your time and attention!
-Josh