I am blog
These are the things I write about
The steps I took to successfully deploy to an Android device after receiving "The application could not be started" error.
XAML debugging tools are a welcome feature in Visual Studio but you may not want them to load by default.
By default the Diagnostic Tools window opens automatically when debugging. Whilst this is a handy tool I do not want to it load every time I debug.
You double click on your iOS storyboard, it opens, and then nothing. A blank screen or maybe an error if you're lucky. There are two steps to follow to make storyboards load.
Don't make me remember to run all my units tests, do it for me. Adding unit tests to the Kudu deploy script.
When I considered moving this blog to HTTPS all I thought about was getting an SSL certificate. Actually the certificate is only the first step, there is plenty more to do.
Let me guess, you're trying to set up an SSL certificate on Azure. I know, it happened to me.
Tools matter. And when there isn't a ready made tool for the job you have to make your own. Enter the ultimate desktop build.
This one had me banging my head against the wall for a long time, refreshing a list of items was causing the app to crash when it was repopulated.
There is nothing more frustrating than having to horizontal scroll a file on GitHub. It doesn't make for a happy user experience. Not for me anyway.