Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Normally when you have a application configuration file in your application and your application is expected to read from it.
Is it good to check initially at start up if this file exists and raise an error and not to proceed at all ? (Worse case senarios)
Or leave it to the unhandled exception manager to handle it and shut down the application? (WPF/Winforms etc)
Please advice?
A better approach would be to have sane defaults configured, and run in the absence of the file. Really, what happens if the file is present, but some critical setting has been deleted by the user?
Especially if the user can change config points using an in app UI, crashing out in the absence of the file leads to an unrecoverable situation.