Text entry answers for For critical errors that leave the app in an undefined state sorted by frequency of occurrance.
| (2) | CListCtrl |
| (2) | crash |
| (1) | crash and burn |
| (1) | Create a log of the event |
| (1) | Depends on the app & environment. Sometimes handle it, force app restart. Other times throw exceptions. |
| (1) | Don't Leave App in undefined state! |
| (1) | Let if crash and burn |
| (1) | Log Crititcal |
| (1) | Log the exception, report it to the user and try to gracefully recover without crashing the app |
| (1) | Log the failure to bug traking system and fail |
| (1) | Messagebox with Explanation |
| (1) | MessageBox.Show( "An error occured in Windows. Please call Microsoft support for assistance." ); |
| (1) | Notify the user of the error, give an option to report the error, and notify themthat the app needs to be restarted |
| (1) | report error then uwnind app until it hits a good state, even if that is all the way back to just started |
| (1) | Set a global error flag || Set a global error flag || Return an encoded error value (eg HRESULT) || Throw an exception || Cover up the mess and don't say anything |
| (1) | Throw an exception and open an "send a report" dialog. Then give the user the option of continuing or quiting the app. |
| (1) | Try to write any unsaved data and restart! |
| (1) | uhh.. terminate? |
| (1) | xna framework is not needed on the market |
| (1) | 777-777-1911form@value777.com |
| (1) | autosend a details email |
| (1) | Blame Microsoft, then hunt for other running apps to crash |
| (1) | blame someone else |
| (1) | Catch, log, and send error notifications via Nagios |
Submit an article or tip