Keybinding activation on Windows machine fails.

[haberdashPI]

See #49

Seems to be a problem activating keybindings on Windows. (This is probably some issue with how paths are handled).

[haberdashPI]

See updates in #49 for how I reproduced the problem and a workaround.

It's quite hard to reproduce this problem after getting the extension working. I tried to uninstall VSCode and all the %AppData% and still couldn't reproduce the problem. Need to look into what other places VSCode is storing data (it does seem that not everything was lost, because I still had extensions installed after re-installing VSCode).

[haberdashPI]

New learnings:

Extension host version error

In the console there is a message about the extension host being the wrong version which shows up while install mastser key on windows. This seems to be the cause of the problem. Restarting VSCode resolves the issue. Removing all app data and user profile data for VSCode and reinstalling the extension reproduced the problem. I cannot find anything online explaining the reason for this error message.

My best guess is that the extension host version recently changed (this would explain why the error hasn't been addressed in a question online), and if I update Master Key in the extension store it should resolve the issue.

Unsigned extension

One of the extensions (it is hard to tell which) installed by Larkin causes the second I error I saw in #49. If I can I should improve the error message and I should at least watch the order of extension installation carefully and verify by selecting only that extension to verify which one is causing a problem. Hopefully we can just eliminate it by adding its features to selection-utilities

[haberdashPI]

Experimenting with the release in #52 indicates that the same problem remains. My hypothesis that this is due to some recent change in the extension host version was incorrect.

[haberdashPI]

TODO: re-run the extension on a windows machine and post the exact error from the console here in this issue.