Crash on Launch, Win7 x64

[ReanimationXP]

References Notification creation I think. This happens with damn near every version, even ones which have worked. I suspect a restart would fix, but keeps happening.

Also Github wouldn't let me upload the zip you're generating. Even after trying a handful of evasion bullshit. Uploaded it here:

https://mega.nz/#!sNQjHbhS!5UIV1uG2dDuuD7CwB5NSIvYgtSyMd0wrZ0K9Vy0wnn4

[FireEmerald]

Do you remember which kind of Notification (None,Windows,Sound,Toast,Custom) you had configured to show up if you changed your devices?

The error occurred because you are using Windows 7 and configured:
"NotificationSettings": 3 - which is Toast and Toast isn't available under Windows 7.

The easiest way to fix your problem is to delete the configuration file:
%AppData%\Roaming\SoundSwitch\SoundSwitchConfiguration.json

Edit:
Nevertheless @Belphemur there could be a small issue introduced in 0bc54a4.
I changed the order of the Notification DropDown menu items to be more sorted.

0bc54a4#diff-e5c0d47cc4eb7013b7b5cb73a9c1f456R18

I didn't noticed that these settings are serialized as integer values.

[Belphemur]

@FireEmerald it surely that yes.

We need to either put them in the order they were or add a backward compatible setting in the configuration.

The easiest is to rechange the order in the enumerated.

I missed that change when reviewing the pull request.

[Belphemur]

@ReanimationXP is I'm sorry but for now you'll have to remove the %appdata%/SoundSwitch directory to start with a fresh configuration.

[Belphemur]

In that case I'll add a fallback for the notification setting. Since each notification has an IsAvailable method. This way we'll avoid this type of crash. It would be nice to know how this setting has been set in the first time. ⁣Sent from BlueMail ​

…

On Mar 5, 2017, 08:25, at 08:25, FireEmerald ***@***.***> wrote: Well, but `"NotificationSettings": 3` wasn't changed - so the source of this crash shouldn't be the localization commit. -- You are receiving this because you were mentioned. Reply to this email directly or view it on GitHub: #161 (comment)

[FireEmerald]

It would be better to assign each Enum a value which is used in the configuration instead of the code order. Then we could change the order without any problems.

[FireEmerald]

The only file changes which lead to this crash is located here: NotificationTypeEnum.cs.