"Unable to activate Windows Store app [GUID]. The [EXE Name] process started, but the activation request failed with error 'The app didn't start'." - Make sure your project is on C!
A debugger is attached to App4.UWP.exe but not configured to debug this unhandled exception. To debug this exception, detach the current debugger.
Unable to activate Windows Store app 'f736c883-f105-4d30-a719-4bf328872f5e_nh7s0b45jarrj!App'. The App4.UWP.exe process started, but the activation request failed with error 'The app didn't start'.
I did a bunch of repairs, re-installs, etc., thinking it was a Xamarin.Forms issue.
Then I did what all dev's should do when troubleshooting, started eliminating variables. "What happens with a standard, non-Xamarin UWP app?"
Same error! Well now we know it isn't Xamarin!
What can be the problem here? This only happens on universal apps. Classic Desktop projects opens without problems.
Tried renewing my developer license. It doesn't work for Windows 10 Universal Apps and is only for Windows 8 Apps.
Tried uninstalling Visual Studio 2015 completely and re-installing. Still nothing.
NEW: Tried doing a full fresh reformat of Windows 10 still didn't work.
Scrolling down... no the "answer" can't be it! It can't be THAT simple!
"...I even went as far as to do a fresh install of Windows 10 but when the problem still persists, I was about to give up. But I found out another solution that I haven't tried: move the project folder to the C: drive.
OMG, all my projects were on my D drive too! It CAN'T be that, can it?
Move the original Xamarin project from D to C and guess what?
Are you a Windows Live Writer user with a Blogger blog?
Windows Live Writer (WLW) used an old authentication API AND old Blogger API. Google has been wanting to deactivate both for a while now, but kept them available for Windows Live Writer users.
With last week’s release of Open Live Writer (OLW), the open source fork of Windows Live Writer, Google killed both.
Then… Showing the power of open source, dev’s stepped up and added initial Blogger support to OLW. If you download the latest version (which is SO nice and fast to install now), v0.5.1.2, you get Blogger support. Woot!
If you are seeing Display driver stopped responding issues and have an Intel card, try turning off your 3D settings, reboot and see if that helps.
Since upgrading to Windows 10 I've been getting "Display driver stopped responding and has recovered" every so often. SnagIt would trigger it, but other apps too.
Yet sometimes it would go away, and stop happening.... grrr. I thought it was my Intel 4600 HD driver versions, that updating would fix it and that the issue would come back in later versions.
Problem: Intel Video Driver, Windows 10 "Display driver stopped responding and has recovered" when using SnagIt and other apps.
For the second time this week I was in the Channel 9 Studio recording a show, this time hosting This Week on Channel 9. The best part was that I suckered (um... errr... um... invited... yeah that) co-VS ALM MVP Brian Randell to be my co-host.
You are listening to RadioTFS, right?
You all are listening to the RadioTFS podcast right? You know, the one that I host with Martin Woodward and Paul Hacker? The one where every two weeks we talk all things TFS, VSO and ALM? And we interview many of the TFS/ALM influencers, MVP's and Microsoft team members?
And guess what? Episode #98, "Pocket Dialing Paul" is just out! Woot!
Well, if you're not... it's not to late!