Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

If Rubberduck.config cannot be read, use default configuration. #131

Closed
rubberduck203 opened this issue Dec 23, 2014 · 0 comments
Closed
Assignees
Labels
bug Identifies work items for known bugs

Comments

@rubberduck203
Copy link
Member

If the *.config file is missing, Rubberduck uses a default configuration that is more or less hardcoded into the system and then later creates a new *.config file.

If *.config is simply corrupted, then Rubberduck blows up and the add-in doesn't load. Catch the exception and give the user the option to repair the *.config file with a warning that any customization will be lost.

@rubberduck203 rubberduck203 self-assigned this Dec 23, 2014
@rubberduck203 rubberduck203 added this to the Settings/Options Dialog milestone Dec 23, 2014
@rubberduck203 rubberduck203 added the bug Identifies work items for known bugs label Dec 23, 2014
Hosch250 pushed a commit that referenced this issue Jun 27, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Identifies work items for known bugs
Projects
None yet
Development

No branches or pull requests

1 participant