Re: Stopping error pop box
try/catch?
Thats just hiding the problem though.
Re: Stopping error pop box
Would happily hide the problem if it meant the pop-up box would not appear!
We have corrected for the issue we found (try- catch didn't actually catch the issue), but this is more to do with stopping the error pop-up message in the future if something else unexpected happens (Pop-up doesn't happen in the Visual Studio 6 version).
Really just wondering if anyone else had something similar and if there are any complie time options in VS2008 we could use.
Re: Stopping error pop box
No there's no compiler/linker switch available for this.
If try/catch doesn't solve your issue you have a non C++ expection. Check out SEH http://msdn.microsoft.com/en-us/libr...57(VS.85).aspx
Re: Stopping error pop box
Your best best is to debug and fix the code issue. VC6 wasn't very compliant and VC2008 is more strict and is exposing a coding error.
Re: Stopping error pop box
Quote:
Originally Posted by
NCIRL
We found the error and corrected it no problem, however, the error does not cause the pop-up when run from the Visual Studio 6 build
First you say you fixed the error, then you say that "the error does not...". I thought you fixed the error?
Quote:
and I was wondering if there is a compile time option on Visual Studio 2008 that we could use to prevent the the pop-up message.
Why not fix the error now? The time it could take you to look for band-aid solutions could have been spent in diagnosing the cause of the problem.
Quote:
The dll & 3rd party application are run in a batch mode and the pop-up window causes everything to hang until someone actions the pop-up, which is not possible in batch operation.
A lot of people would not put trust in a program that has an error, regardless of when it happens. If the DLL was coded in C++, runtime errors could be the sign of other things internally wrong with the program that you have yet to identify.
Also, what if you could cover up this dialog box? What if the error is a very serious one? You would never know, and whoever is running this batch file is risking something very serious going wrong.
Fix the error. Or at the very least, identify what the error is, note it, and then see if it can be "left for later".
Regards,
Paul McKenzie