This is probably something that you’ve seen if you’ve been working with Windows Store apps for a while but it just happened to me so I thought I’d share.
I find that when I’m writing code that’s using the Share Contract ( more details here ) if I’m working in the debugger and trying to debug Share or if I happen to have code that behaves badly during development and throws a bunch of exceptions then I can get the system into a slightly broken state.
Here’s a screenshot of where I seem to have ‘broken’ Share;
and my code isn’t firing and I can’t continue to debug.
The way I resolve this one is to restart Explorer.exe – if you give that a quick cycle you should find that you’re back in business.
Thu, Oct 18 2012 6:18 PM