Location of Working Directories When Using LabWindows/CVI To Debug an External Process Primary Software: LabWindows/CVI Development Systems>>Full Development SystemPrimary Software Version: 8.5 Primary Software Fixed Version: N/A Secondary Software: N/A
Problem: I have a TestStand sequence that calls a LabWindows/CVI DLL that I have created. I am attaching LabWindows/CVI to the TestStand Sequence Editor process by using the Run » Specify External Process command. When debugging my DLL, some of the files that my DLL are looking for cannot be found. Our DLL references these dependent files using the This may or may not be important, but both TestStand and LabWindows/CVI are installed onto the When using LabWindows/CVI as the debugger, LabWindows/CVI uses its own directory as the working directory rather than the directory of the application. So in this case when you use the To workaround this behavior, simply add
Report Date: 10/26/2007 Last Updated: 11/20/2007 Document ID: 4EP92A6S |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
