Problem when I run the application using cntrl+F5. Wintech OPC DLL
-
Hi, I have an MFC application for which I have integrated OPC function using Wintech OPC DLL. This application is an OPC Client which connects to a OPC Server and gets values from it using OPC communication. I call the OPC functions in my application. I used WPF(dll created by C#) in this application for some graphics and turned on the project setting "Common Language Runtime Support (/clr)" When I run my application in VS2008 using F5, it runs without any issues it shows correct values. But when I run the same application using Cntrl+F5 or directly run the EXE, it runs but it shows junk values. Notes Suppose i change project setting from "Common Language Runtime Support (/clr)" to "No Common Language Runtime support" it is not supported WPF dll. Please help me to find the solution for this problem
-
Hi, I have an MFC application for which I have integrated OPC function using Wintech OPC DLL. This application is an OPC Client which connects to a OPC Server and gets values from it using OPC communication. I call the OPC functions in my application. I used WPF(dll created by C#) in this application for some graphics and turned on the project setting "Common Language Runtime Support (/clr)" When I run my application in VS2008 using F5, it runs without any issues it shows correct values. But when I run the same application using Cntrl+F5 or directly run the EXE, it runs but it shows junk values. Notes Suppose i change project setting from "Common Language Runtime Support (/clr)" to "No Common Language Runtime support" it is not supported WPF dll. Please help me to find the solution for this problem
So, you cannot use debugger to find an error, since the program runs correctly under debugger. You need to use another debugging technique, for example, tracing. Add TRACE/OutputDebugString messages to different parts of the program. Print results of different function calls, values of a variables etc., whatever you need to check the program. Run the program without debugger with DebugView: https://docs.microsoft.com/en-us/sysinternals/downloads/debugview Use the TRACE output to find what is wrong. By the way, during development process, always run your program without debugging. Use debugger only if you really want to debug. This allows to prevent such situations in the future.
-
So, you cannot use debugger to find an error, since the program runs correctly under debugger. You need to use another debugging technique, for example, tracing. Add TRACE/OutputDebugString messages to different parts of the program. Print results of different function calls, values of a variables etc., whatever you need to check the program. Run the program without debugger with DebugView: https://docs.microsoft.com/en-us/sysinternals/downloads/debugview Use the TRACE output to find what is wrong. By the way, during development process, always run your program without debugging. Use debugger only if you really want to debug. This allows to prevent such situations in the future.
Hi Thanks for replay. I downloaded debugview application it is also not display issue. Still i couldn't identify the issue. Please help me
-
Hi Thanks for replay. I downloaded debugview application it is also not display issue. Still i couldn't identify the issue. Please help me
Try to log: at first step log the main steps of the running application, then implement smaller logging steps and so on...